"No connected database" when trying to send rageshakes when IDB is not available

[jryans]

Hm, well I don't get the Something went wrong! message on refresh anymore, but submitting logs does result in an "No connected database" still.

And that doesn't go away even after logging in and out... so going to assume something else is causing that. Is there any other way I can get debug logs to you guys ooi?

Originally posted by @anoadragon453 in #13287 (comment)

[jryans]

@anoadragon453, are you using a private window in Firefox? Do you see this immediately after login without any further actions?

[anoadragon453]

@jryans Correct. Reproducible with a new account, on https://riot.im/develop

Possibly useful log lines:

Just prints "Sending bug report" when clicking "Send logs":

Edit: and even after closing all private tabs and reopening another one to test again with a new account.

[t3chguy]

Well the logs are stored in IDB which is not available in Firefox InPrivate so it makes sense

[anoadragon453]

oh, well then

[jryans]

It would be nice to have some fallback path for recording and reporting rageshake data when IDB is not available, but it does appear like that could be complex to pull off, since the implementation is heavily IDB based right now.

[jryans]

@anoadragon453 As a workaround for now, you could use Firefox's containers feature to login with test accounts instead of private windows so that you'll have regular IDB access as expected.

[anoadragon453]

@anoadragon453 As a workaround for now, you could use Firefox's containers feature to login with test accounts instead of private windows so that you'll have regular IDB access as expected.

Have been doing so and it works great, thanks!

[t3chguy]

Firefox fixed this https://www.mozilla.org/en-US/firefox/115.0/releasenotes/