Closed planeth44 closed 4 years ago
Can you create an example of this issue on something like glitch.com? However, it sounds like this is a bug with Safari, and not with this library.
please help ...
That looks like an old version of the library, and I'd need more than a screenshot to help debug it.
I'm closing this issue since there's no minimal reproduction.
Hi, it's impossible to debug something like this with just screenshots. However, if this is a firebase issue, please raise it with them.
Sorry @jakearchibald I didn't find the time to build a glitch app. I discussed the matter with Maximiliano Firtman and he said it was probably a Safari iOS bug. I filed an issue in the bugtracker. No news since then.
My app works as a PWA but is not “installed” as one (no manifest). However I don't think it's relevant to this particular problem. This is how it goes : the user access the page, the indexedDB is created. User uses the app. Then the user decides to no longer authorize ccokies. (Go to settings and disable cookie) Now the app is no longer working, so said user goes back to allow cookies again.
This is when the problem arise: openDB is stuck in ‘blocked‘ state forever. You can close all the windows you want. Close Safari. Nothing will do unless the user goes to setting and ask for ‘delete the site data’. Which means the DB is deleted.
Tested with Safari iOS 13. Is there a way to get unstuck without resorting to drastic erase of the DB ? Thanks for any insight
BTW, thanks for this awesome library :)