-
Notifications
You must be signed in to change notification settings - Fork 894
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
IINTERNAL ASSERTION FAILED: AsyncQueue is already failed: FirebaseError: The current tab is not in the required state to perform this operation. It might be necessary to refresh the browser tab. #2555
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Sorry to hear about your issues, @burtonator. I haven't encountered this error yet. Based from the error message, it's more likely related to (#1436) multi-tab synchronization support, and was addressed in v5.7.2.
|
Thanks @rommelpe ... appreciate your help as this might be a huge bug for us.
I'm not but I am running synchronizeTabs.
Electron doesn't really have 'tabs' but it does have windows. I've tried to duplicate this and I can't ... I might try to disable synchronizeTabs. What would be the downside of using enablePersistence () without synchronizeTabs? I assume this means the second 'tab' or window wouldn't have persistence? |
Without |
Hey @burtonator. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
We've also been seeing this error on and off for several months. We are not on electron, just your typical web app. We are using I've only now just discovered The error pretty consistently happens when both a) you have multiple tabs of the same app open, and b) Here is a timeline I constructed from some of the error logging:
That last error starts spamming thousands of instances once I open the lid back up in the morning. Failed to obtain primary lease for action 'maybeGarbageCollectMultiClientState'. is notable, as that's the initial error. |
@cmditch "experimentalTabSynchronization" and "synchronizeTabs" are equivalent. It looks like there is indeed an issue with |
This ignores the error if the primary lease is somehow lost between updateClientMetadataAndTryBecomePrimary() and maybeGarbageCollectMultiClientState(). There is no special recovery logic needed as the next primary will run the periodic GC. Fixes #2555
Excellent, thanks! |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
We're getting this exception constantly in the wild, but I can't actually duplicate it locally.
We have about 5k uses and receive this error about 9200 times per month.
Relevant Code:
I don't have a reduction unfortunately. Is there a better way to reproduce this?
The text was updated successfully, but these errors were encountered: