Error opening an IndexDb database on w10 Mobile running an HWA

Fixed, not yet flighted Issue #7578452

Details

Author
Joao A.
Created
May 16, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
13.10586
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Different behavior between Edge and HWA on Mobile only. Not sure it is related to chakra, or IndexDb implementation.

The issue is happening using IndexDB on w10 mobile. The indexdb is being used through a DexieJS (IndexDB JS implementation). It works flawlessly on Desktop (Edge), even as a HWA. However if I run it on the device, I’ve got an error opening the indexdb.

Some detailed info:

          Lumia 1520
          OS Build: 10.0.14332.1001

Repro: https://github.com/joalmeid/IndexDBHWAmobile

Also created an issue in DexieJS, to follow up from their side: https://github.com/dfahlander/Dexie.js/issues/249

Uncaught Promise: OpenFailedError: UnknownError UnknownError occurred when opening database FriendDatabase. OpenFailedError: UnknownError UnknownError occurred when opening database FriendDatabase
at Anonymous function (http://192.168.1.100/phc2/Dexie.js:2459:45)
at doResolve (http://192.168.1.100/phc2/Dexie.js:741:13)
at Promise (http://192.168.1.100/phc2/Dexie.js:585:13)
at Anonymous function (http://192.168.1.100/phc2/Dexie.js:2457:25)
at Promise.newPSD (http://192.168.1.100/phc2/Dexie.js:862:13)
at _promise (http://192.168.1.100/phc2/Dexie.js:2453:17)
at transactionPromiseFactory (http://192.168.1.100/phc2/Dexie.js:1327:17)
at resume (http://192.168.1.100/phc2/Dexie.js:1315:29)
at Anonymous function (http://192.168.1.100/phc2/Dexie.js:1280:17)
at Array.prototype.forEach (native code)
Dexie.js (892,9)

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nishant N.”

      Changed Status to “Fixed, not yet flighted”

    • Thanks for providing us with this feedback on MS Edge. we are showing this as fixed based on our testing of builds 

      10.0.
      14342.1001 and higher. Looking forward to more feedback from you in the future.

      We had an internal item of feedback that we duped this to, since technically this was a known issue that we were already aware of.

      All the best,

      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in