-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate "Uncaught UnknownError: Internal error." #1014
Comments
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. |
Not at all, I'm afraid. * 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 ( 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 |
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. |
In #1014, we found that proper error messages were missing from PrivacyAsyncStorage, which made it harder to debug. I added those now.
In #1014, we found that proper error messages were missing from PrivacyAsyncStorage, which made it harder to debug. I added those now.
In #1014, we found that proper error messages were missing from PrivacyAsyncStorage, which made it harder to debug. I added those now.
In #1014, we found that proper error messages were missing from PrivacyAsyncStorage, which made it harder to debug. This commit adds them.
@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 |
We've received the below error report.
The text was updated successfully, but these errors were encountered: