Open baltpeter opened 1 year ago
The debug info isn't exactly helpful, unfortunately.
Searching for "Uncaught UnknownError: Internal error." only brings up IndexedDB problems, albeit with longer error messages. That would make this @zner0L's problem.
Maybe the code location is more helpful.
Maybe the code location is more helpful.
Not at all, I'm afraid. commons.bundle.gen.js
:18:18078 is our rethrow
function*.
* Which we should probably re-evaluate at some point. I feel like a lot of our usages of that stem from us not properly understanding promises early on…
Doesn't seem to be related to the browser either. Remarkably enough, I've managed to match it exactly (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
) but still wasn't able to reproduce the problem.
I think I'm out of ideas.
Have you tried private mode? This might actually be related to IndexedDB as you suggested: https://stackoverflow.com/questions/74207049/internal-error-opening-backing-store-for-indexeddb-open
Yes, I am pretty sure I can narrow it down to PrivacyAsyncStorage
, since this is the only place where we use rethrow
without any additional error message (oops, should've caught that earlier). I'll investigate.
It might be due to a broken browser profile, which seems plausible to me (https://jasonsavard.com/forum/discussion/4233/unknownerror-internal-error-opening-backing-store-for-indexeddb-open), but I don't really know how to mitigate that. I think in this case I do want to throw an error, but the problem is not on our side.
Sounds plausible. Do you want to reply to the user?
Yes, I'll do that.
@zner0L Any news?
Neither me, nor the reporter were able to reproduce this, but it seems to be related to errors in the browser (configuration), so in #1166 I introduced changes to ignore this error and just fall back to localStorage
.
We've received the below error report.