v7.4.4 updated today? Suddenly nothing works.
-
I've been a pretty happy Cookie user for many versions. I'm not sure how long, but v3? 2? Anyway...
Cookie has full disk access. It still has full disk access. Suddenly (I imagine when macOS updated Cookie from the App Store?), every browser is disabled, and Cookie asks to allow access to all of the usual first time 'allow access' folders (not that it does any good).
Even when I do allow access - either from the 'allow access' button, or the macOS file/directory selection dialog, nothing changes. (The 'allow access' button doesn't change color, there's no form of acknowledgement - nothing.)
I've tried the obvious 'remove sandbox permissions' button, restarted cookie, and then re-allowing access. (as well as toggling the 'full disk access' permission). Nothing changed.
This was before updating to macOS 15.1. I'm also running on an M1 MacBook Pro, for what it's worth.
I obviously can export my settings, run one of the apps to completely remove all of the settings, delete Cookie, and re-install - but I'd like to do something less scorched earth (or give you a chance to see if there's a bug you want to fix first).
-
oh sorry, I see you already tried that....
feel free to email me at support@sweetpproductions.com -
@Pariah_Zero have you also tried a computer restart as well as remove the sandbox permissions
-
I've restarted (a few times), as well as removed sandbox permissions (again, a few times).
In fact, I've tried a few iterations of removing sandbox permissions, uninstalled cookie, reinstalling it, and then granting full disk access (as I primarily use Safari).
As well as exporting my cookie settings (with the intent to re-import them again - however, there doesn't seem to be a lot of point if I can't even get Cookie to accept it has permissions to do its job).
It behaves as described above. Clicking on "Give global access" doesn't do anything, even after granting full disk access (and restarting, of course).
-
@Pariah_Zero can you download and run this debug build:
https://send.tresorit.com/a#Kz_YMG0y-qGoRJA61I1-PgIt will still fail to enable the paths, but may give me some clues as to what is happening.
- If you unzip the file,
- then open the Cookie app contained inside
- it will ask for access to the desktop - allow this
- than try to Allow access to some browser paths. any paths, it doesn't matter which
- A file wil be saved to your desktop: CookieLog.txt
can you send me this file
support@sweetpproductions.com -
heres a new debug build link
https://send.tresorit.com/a#GCdYe6VrJgsp75mc1dw6FQ -
hares an updated debug build:
https://send.tresorit.com/a#mUqeFBW9hjmQiV5UlhOIgQ -
I'm having this exact issue as described by Pariah_Zero. It started after updating to Sonoma from Ventura this afternoon. Cookie v7.4.4. Trying all of the prescribed recommendations listed above has not resolved the issue. Please help. I've been using Cookie and a host of other SweetP products since 2013. Thanks!!
-
@mwculbreath can you try this debug build and send me the CookieLog.txt file:
https://send.tresorit.com/a#6HlMfQO4CAvey6NJgZbCPw- Download and unzip the file,
- then open the Cookie app contained inside
- it will ask for access to the desktop - allow this
- than try to Allow access to some browser paths. any paths, it doesn't matter which
- A file wil be saved to your desktop: CookieLog.txt
