Sonoma: Permission for QS to access data in other apps is not persistent

[Bob West]

Hiya…

Just "upgraded" (don't get me started) my MacBook Pro M1 Max to Sonoma, and I'm seeing a gripe from macOS every time QuickSilver starts up.

Apparently, sandboxing is tighter now, so explicit permission from the user is required to allow QS to access data in other apps.

Unfortunately, I'm seeing this on every startup; the permission is not being saved.

Interestingly, I didn't see this issue on my Mac Studio M1 Ultra... But I did have to re-set every trigger's key combination every time I restarted. Which is one of the several reasons why I had to erase that machine and reinstall Ventura. :/

Would like to avoid having to do the same with the MBP for now...

Any way to grant this permission persistently?

TAI…

[Rob McBroom]

On 6 Oct 2023, at 18:05, Bob West wrote:

> Just "upgraded" (don't get me started) my MacBook Pro M1 Max to Sonoma, and
> I'm seeing a gripe from macOS every time QuickSilver starts up.
>
> Apparently, sandboxing is tighter now, so explicit permission from the user
> is required to allow QS to access data in other apps.
>
> Unfortunately, I'm seeing this on every startup; the permission is not
> being saved.

There could be several things you need to allow (files, contacts, calendar events) depending on which plug-ins you use. Which one won’t stick?

The first thing I would check is that you’re using an official build from qsapp.com since those will be signed and notarized.

--
Rob McBroom