Bug 199937

Summary: REGRESSION (iOS 13): Error: IndexedDB Server Was Lost Please refresh the page
Product: WebKit Reporter: Sanjay Kumar <hypertree>
Component: Service WorkersAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Blocker CC: beidson, cdumez, sihui_liu, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: iPhone / iPad   
OS: Unspecified   

Sanjay Kumar
Reported 2019-07-19 03:55:38 PDT
if you kill a PWA or any webworker enabled app with a IDB transaction happening in a webworker, restarting the APp seems to lose IDB with above error message. This is similar to or perhaps a duplicate of: https://bugs.webkit.org/show_bug.cgi?id=197050 This is critical because if IndexedDB is lost - the entire app stops working. Please ensure that killing and restarting a page/PWA with IndexedDB in webworker - does not kill IndexedDB server for good.
Attachments
Radar WebKit Bug Importer
Comment 1 2019-07-19 12:57:16 PDT
Sihui Liu
Comment 2 2019-07-19 14:57:14 PDT
(In reply to Sanjay Kumar from comment #0) > if you kill a PWA or any webworker enabled app with a IDB transaction > happening in a webworker, restarting the APp seems to lose IDB with above > error message. > > This is similar to or perhaps a duplicate of: > https://bugs.webkit.org/show_bug.cgi?id=197050 > > This is critical because if IndexedDB is lost - the entire app stops working. > > Please ensure that killing and restarting a page/PWA with IndexedDB in > webworker - does not kill IndexedDB server for good. Hi Sanjay, Thank you for the report. Do you have the test app or web page that we can use to reproduce the issue? https://bugs.webkit.org/show_bug.cgi?id=197050 is about process getting killed while backgrounded. Your case seems like you are killing the process manually.
Sanjay Kumar
Comment 3 2019-08-03 09:28:36 PDT
Hi Sihui, I re-architected my App and I have not seen this error message of late. I don't know now what exactly was causing the error or if it will return. So I am marking this bug as works for me.
Note You need to log in before you can comment on or make changes to this bug.