-
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
Upgrading to sdk version 8.3.2 causes auth errors against firestore emulator #4721
Comments
I created a small app demonstrating the issue: https://github.com/zwily/firebase-8.3.2-test Somehow, auth information isn't making it into the firestore emulator. The same problem does not happen against production. This may be an emulator bug, but it does not happen with the current emulators and 8.3.1. |
I found this issue as I have been having issues with permissions. My previously-working Firestore rules are now failing with a "Null value error" saying I cannot create a document where I could before. Downgrading to 8.3.1 fixes the issue. |
This should be fixed in Firebase CLI v9.9.0. |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
I upgraded from 8.2.5 to 8.3.2, and after upgrading, found that any calls to my firestore emulator were failing with auth failures. Authentication (Google auth against the auth emulator) does appear to succeed.
I found the following blob in
firestore-debug.log
that does not appear when using 8.3.1. (Token is just against emulator, not sensitive.)I bisected all the intermediate firebase-sdk upgrades, and it was the move from 8.3.1 -> 8.3.2 that started doing this. I am also using the latest
firebase-tools
(9.8.0).I scanned through the diff of 8.3.1 -> 8.3.2 but the refactoring looked fairly extensive.
Relevant Code:
Any authenticated firestore read against emulator. I'm trying to put together a bare app demonstrating the problem and will update the ticket if I manage to get that.
The text was updated successfully, but these errors were encountered: