Thom Lawrence

So if you have a look at the [Java code](https://github.com/getsentry/sentry-java/blob/92483883017b53aaa4bcac8a43548ca0aec255a3/sentry/src/main/java/io/sentry/protocol/Contexts.java#L16) or the [Sentry docs](https://develop.sentry.dev/sdk/event-payloads/contexts/), you can see that there's basically some special cases with meaningful key value pairs underneath them....

Yeah, purely for debouncing I often have code like this: ``` (reg-event-fx :app/store-debounced-event (fn [{db :db} [_ event timestamp]] {:db (assoc-in db [:app/debounce (first event)] {:timestamp timestamp :event event})})) (reg-event-fx...

This is caused by sandboxing: > Sandbox: ExternalQuickLoo(32569) deny(1) user-preference-read org.n8gray.QLColorCode > rejecting read of { org.n8gray.QLColorCode, thom, kCFPreferencesAnyHost, /Users/thom/Library/Preferences/org.n8gray.QLColorCode.plist, managed: 0 } from process 32569 (ExternalQuickLookSatellite-x86_) because accessing preferences...

It appears to be enough to grant full disk access to the following executables: 1. `~Library/QuickLook/QLColorCode.qlgenerator/Contents/MacOS/QLColorCode` 2. `~Library/QuickLook/QLColorCode.qlgenerator/Contents/Resources/highlight`