[Webkit-unassigned] [Bug 170358] IndexedDB keys are gone or nonworking after upgrade to iOS 10.3

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 4 07:32:16 PDT 2017


Andrew <andrew at asmiller.com> changed:

           What    |Removed                     |Added
                 CC|                            |andrew at asmiller.com

--- Comment #3 from Andrew <andrew at asmiller.com> ---
Created attachment 306173

  --> https://bugs.webkit.org/attachment.cgi?id=306173&action=review

Test case using db.js indexeddb adapter

This same issue has happened to me, using the db.js adapter. Based on the test case (attached), it looks like all of the table data is wiped if the table is set to NOT autoincrement ids. The other tables DO keep their data across the udpate. I have not found a way to retrieve the lost data after the update.

In earlier versions of Safari, the autoincrement functionality was buggy, so many app developers worked around it by using their own IDs.

The next step would be to test a non-autoincrement table using vanilla js.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170404/bcf9bab4/attachment.html>

More information about the webkit-unassigned mailing list