+1. My users are reporting this too - toggling off and on the extension in Safari settings seems to fix it. C'mon Apple.

We are still not sure if that’s a bug on our side or Apple’s. Maybe there’s a new permission that we need to request? It's a bug on Apple's side. Something to do with Safari 18 shipping with a different database schema version to WebKit and because of this, when converting storage (not sure why it does that) - it nukes all local storage. Brilliant if you ask me. Now I have thousands of users that have to setup my extension again. It has apparently been fixed in this PR but I'm not sure when that will be released. See my PR comment. I know there is an 18.1 beta, maybe 18.1.1??? I don't know. Too late anyway. https://github.com/WebKit/WebKit/pull/33778#issuecomment-2362289012