Cookie keeps asking for folder permissions
I note that I ran into this loop, adding Containers along with Library, in versions 6.3.5 and 6.3.6. Thankfully, I found this post.
But the solution was more than simply 'Remove all Sandbox permissions'. I also had to:
- Enable Global permissions. This covered all my browsers.
- Click "Enable" for EACH browser down my list.
- Approve of the resulting (all too familiar) requests for permissions: Library and Containers. Just once!
Cookie is now sane again.
I am using Cookie 6.3.6. Cookie endless asks for path permissions. I cannot even get out of the loop to try to change the preferences. Finally killed it via activity monitor since it does not otherwise show up in the force quit window. So finally deleted it off my iMac so I can do some work. If it gets fixed, I may choose to use Cookie again, but very frustrating.
If you can’t access Preferences, then you need to do a full reset of Cookie.
Quit Cookie first.
You can restore your settings,
by first making a copy of all the files in this folder:
Then delete this folder:
On macOS Catalina and earlier, the folder path is:
Quickly skip through the setup.
And replace the files you copied earlier.
Then you should be able to restart Cookie with all your browser settings and favorites.
You still need to go into Preferences and update any settings you had customised (start at login, hide dock icon etc…)
@SweetP I feel that the information above should be updated. I have been encountering the issue for some time, and I continue to encounter it from time to time. I am currently on Monterey. There is no ~/Library/Containers/com.sweetpproductions.CookieApp/Data/Library/Application Support/CookieApp folder in my Library. There is definitely a ~/Library/Containers/Cookie folder, but there seems to be in that folder various items unrelated (?) to Cookie that I am not sure I should delete (more than 9 Mo total size).
What I delete is the small (sub)folder: ~/Library/Containers/Cookie/Data/Library/ApplicationSupport/CookieApp (it contains Favorites.plist, Settings.plist and TrackingCookies.plist). It seems to do the job.
Any comment or advice?
@SweetP FYI I'm having this issue in Big Sur right now. I returned to my Mac (running Cookie 6.8.6) after a couple of hours which was left on and there was a pop-up window asking for permission. I clicked permission maybe 100 times, then went into Activity Monitor to quit it. I saw 6.8.7 was out so I updated it, launched and got the same constant folder requests.
I tried to give permission to folders higher-up to 'bless' all the folders below but that didn't work. I also tried Removing Sandbox Permissions but that didn't seem to do anything - the permission requests kept coming.... hundreds in a row, nonstop
FYI I trashed com.sweetpproductions.CookieApp, then set up app from scratch. (Re-entered serial #)
I'm not getting constant requests for folder permissions, but in setup if I give Global permissions per-browser then click back on a browser I'd given permissions the 'Global' button is no longer greyed-out, and I click again and go through a 3-folder permssion-granting again.
When I open Cookie right now, for example, I see my 4 browsers (Safari, Firefox, Brave, Vivaldi). If I click on Brave it shows 3 folder/paths (Application Support/Brave, Library/Caches, /Library/Preferences) that need permission, the 1st two have checks under 'Required' and all of them have clickable 'Allow' buttons (which SHOULD be greyed out) and Global Access is ALSO clickable. I don't know why, because I've given acess over and over. They should all be greyed-out by now, right?
@SweetP So my system ended up then having some sort of issue, I don't know what it was related to. My dock grew three active 1Password icons, two Firefox browsers, and I couldn't shut down via menu, had to button-press my iMac into shutdown.
I relaunched and some weird housekeeping needed to be done (I had to re-permit full disk access to Backblaze, for example) but after relaunching Cookie and setting it up again like new it seems to be working.
So it probably wasn't an issue with the app...