You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment: Windows (with Chrome and maybe other browsers), when RTDB emulator is set to listen on "host": "0.0.0.0" in firebase.json.
Root cause: firebase/firebase-tools#2870
Workaround: firebase/firebase-tools#2870 (comment)
tl;dr: Run localStorage.removeItem('firebase:previous_websocket_failure') in Developer Console on Firebase Emulator UI web page (NOT hosting emulator or anywhere in your app)
We should either bake the workaround into Emulator UI or fix the underlying issue in RTDB (cleaner but may take longer). The workaround above can be used to get it working for now.
The text was updated successfully, but these errors were encountered:
Is there any updates on this issue? It is becoming more frequent and more annoying to delete the localStorage key. Sometimes it is confusing when it is doesn't update because I think my code is broken when it is the emulator lost the websocket connection and falling back to the http one and failing to connect.
I am having this issue as well, but I tried the workaround and it did not work. The issue is occurring when I launch the Sign in with Google pop-up and it tries to connect to the Auth emulator. I ran the provided command in the emulator UI developer tools console and then re-launched the sign in pop up, but it still failed to connect. I also tried completely clearing the localStorage and cache and restarting the emulator, and still it could not connect.
Symptoms: #464 (comment)
Environment: Windows (with Chrome and maybe other browsers), when RTDB emulator is set to listen on
"host": "0.0.0.0"
infirebase.json
.Root cause: firebase/firebase-tools#2870
Workaround: firebase/firebase-tools#2870 (comment)
tl;dr: Run
localStorage.removeItem('firebase:previous_websocket_failure')
in Developer Console on Firebase Emulator UI web page (NOT hosting emulator or anywhere in your app)We should either bake the workaround into Emulator UI or fix the underlying issue in RTDB (cleaner but may take longer). The workaround above can be used to get it working for now.
The text was updated successfully, but these errors were encountered: