-
Notifications
You must be signed in to change notification settings - Fork 875
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
FIRESTORE (10.12.0) INTERNAL ASSERTION FAILED: Unexpected state #8250
Comments
Looking into the Firebase logs, the error seems to occur after Our app uses I wonder if there would be any legs in not having a tab manager if that will result in no calls to This is also similar to what is described by another GitHub user here I don't know a lot about the internals of the tab management so might be completely wrong here. Sample Log
@wu-hui I would be Happy to share the full log with you privately if you could let me know the best way to do that. |
@vojto Perhaps that's a different issue, this has always been limited to just iOS for us. |
I think the multitab log might be unrelated, this seems to stem from a underlying webchannal message. |
Fair enough, not an area I've dug too deep into. @wu-hui what steps can I take to help try and move this forward? |
Still seeing this issue on the latest version. I have logs I can share if that would be useful? |
@luke-rogers I would like to review the logs. You can share the logs through a private GitHub repo (shared with me), through a Cloud support ticket, or through a Firebase support ticket. If creating a ticket with either Google support channel, please reference this GitHub issue so the support staff knows to route the ticket to my team. Thanks! |
Operating System
iOS 17.4.1
Browser Version
Mobile Safari UI/WKWebView (AppleWebKit/605.1.15)
Firebase SDK Version
10.12.0
Firebase SDK Product:
Firestore
Describe your project's tooling
Angular web app running on iOS via Capacitor
Firestore offline persistence enabled with unlimited cache size
Describe the problem
For a long time now we have been plagued by this iOS-only issue and have received many reports from users that it's causing the app to stop working and forcing them to restart.
We have captured some Firebase debug logs of this error which I am happy to share privately.
This seems similar to the following issues:
Example Errors
Example Stack Trace
Steps and code to reproduce issue
Steps currently unknown but possibly related to the app going between the background and the foreground over time.
The text was updated successfully, but these errors were encountered: