-
Notifications
You must be signed in to change notification settings - Fork 893
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
request.auth
is null for what should be a valid request with self-made custom token [Firestore emulation]
#4795
Comments
@akauppi Something similar happened to me yesterday. I have downgraded to |
@ANDREYDEN Thanks for the extra info. In my case, I’m (happily) stuck with the 9.x beta (different API) so no downgrade possibility, but I trust Firebase to look into this, and suggest a fix. |
@akauppi what version of the Firebase CLI are you using? |
@samtstern I'm using the latest, 9.10.0 so it's not that. |
Was this closed because it was fixed? I'm running 9.10.2 and I have the same issue. |
@Davste93 I received the fix with some update. Are you on |
Hi! This bug is happen to a lot of people but is very difficult find the reason and this forum. again, thanks a lot to all! { |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
The context is emulation (development). In production everything is nice.
In my security rules,
request.auth
isnull
though it should not.I've authenticated in web client like this:
I can see in the browser console that the sign-in is successful.
firestore-debug.log
shows this warning:Can I do something about that?
But the real problem is that I cannot subscribe to changes of the connection guarded by a rule that uses
request.auth.uid
. I've established thatrequest.auth
is null, by playing with the rule.Steps to reproduce:
Open http://localhost:3000/?user=dev and observe the contents of the
firestore-debug.log
Expected:
Actual:
As above, without the project entry.
This looks like a bug or two, to me. Things used to work long ago. The current code is based on 9.0.0-beta.1 and I'm no longer able to try with 8.x APIs. Not sure which change has started this problem.
Thanks for any help!
The text was updated successfully, but these errors were encountered: