App fails to load and throws indexed_db_went_bad error

Technical Support
1

This is from a fresh login on an incognito tab

Screenshot from 2022-06-22 19-03-38
Screenshot from 2022-06-22 19-03-38562×1046 68.6 KB

2

If I’m not mistaken, IndexDB does not work in incognito mode

3

Thanks for reporting, @Fred . Is this happening consistently?
We know that large attachments can cause this: Database errors on some devices when forms have large attachments · Issue #6699 · medic/cht-core · GitHub
This also appears sporadically in feedback docs: Feedback docs: "500: indexed_db_went_bad" · Issue #7149 · medic/cht-core · GitHub

IndexedDb is is used by PouchDb for storage, we don’t use it directly or have any direct control over transactions.

4

@derick that might be the case, this appears to only happen when i try access the app in incognito mode. @diana I was trying to access a user account in an incognito browser window and noticed this, if i do it via a normal browser window it runs OK

5

IndexedDb should work in incognito, the main difference is a limitation is maximum storage space.

6

How many docs does your user have? Do you see the error early in replication or late?
Can you check the amount of storage the app uses when the error is thrown to see if it’s consistent?

7

It happens as soon as authentication succeeds. When i check the indexed_db on the dev tools it has no docs every time

8

And if you load this user outside of incognito, does it work?

this appears to only happen when i try access the app in incognito mode.

I just realized you replied to this, just needed confirmation that:
a) you get this error in incognito every time with this user
b) you never get this error when not in incognito with this user

9

Yes that is correct, works outside incognito

10

I just realized this is Firefox, not Chrome.
@derick was probably correct. I can find plenty of references about this on the web.
Can you try testing this user in Chrome incognito?

11

Tested on chromium incognito, loaded just fine.