Cookie 6 and Safari 16
-
@SweetP Unfortunately, I had problems to allow permissions in the enable browsers dialogs after I removed all sandbox permissions with 6.7.4.1 Beta. I got a spinning wheel of death (beachball). I worked around it by force quitting 6.7.4.1 Beta and did it in 6.7.4.
-
- I installed 6.8.
- Visited https://logbuch-netzpolitik.de
- I pressed the big play-button on the podcast controller on this page.
- I quit Safari.
1 cookie gets deleted but 2 localstorage.sqlite3 entries for that site remains undeleted. They even cannot be deleted by pressing any delete button inside Cookies.
Is that reproducible?
-
I’ve released v6.8.1 which fixes the issue. You do need to quit Safari the first time you open Cookie so it can process the databases. This only needs to be done just the first time.
The App Store Version should be available within the hour, as it has just been approved
-
@SweetP Thanks a lot Russell.
I am somehow puzzled. Quitting my browser (Safari?) before opening Safari? I tried several combinations of quitting and starting orders of Cookie and Safari but the database entries are still there with 6.8.1. -
@Brownie If you close Safari, then open Cookie. Cookie will remove all the junk databases which are causing Cookie to beachball. This will only occur if Safari is closed otherwise it can cause issues.
You only need to do this just the once, and the cleanup will take a moment. You then you should be able to go about using both Safari and Cookie as normal
-
@SweetP It does not work for me as described. Cookie doesn't beachball.
I took a look into Console if that helps. For Cookie (CoreServicesInternal) it writes an error 10 times at the moment when pressing "Delete" inside Cookie for the unremovable entries:
"Scoped bookmarks can only be created for existing files or directories".