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
I get the following error when trying to access a firestore document while the user is not authenticated.
It happens for both streaming and just getting the document.
Handling error gRPC Error (code: 13, codeName: INTERNAL, message: Error making call: SignedOutException: Attempted to call a protected resource while signed out, details: null, rawResponse: null, trailers: null) using FirestoreGateway._handleError
It looks like you are just blocking all unauthenticated requests, which is not always wanted.
If a dev doesn't want to allow access without authentication, they can set that up in the Firestore rules. I think rather than blocking all unauthenticated requests, it would be better to just leave that to the firestore rules.
The text was updated successfully, but these errors were encountered:
Hi! I did actually see if I could fix it initially but ended up just going for a workaround yesterday.
I wanted to stream the app version number before the user logs in so I can force them to update if necessary (that's what I was doing with flutterfire). I now host a Json file instead, and periodically make an http request to read it.
I just had another look inside the firedart library but couldn't really wrap my head around where this error came from. When you do figure it out, I'll be very curious to understand the fix!
We got the same issue, Please help us with the quick fix.
My workaround was actually not to use firestore. I only needed to stream one value before authentication, so I've put that value in a json file on the web and im reading it in a loop via Http requests.
Firstly huge thanks for this library.
I get the following error when trying to access a firestore document while the user is not authenticated.
It happens for both streaming and just getting the document.
But here is the relevant firestore rule:
Here is the full stacktrace
It looks like you are just blocking all unauthenticated requests, which is not always wanted.
If a dev doesn't want to allow access without authentication, they can set that up in the Firestore rules. I think rather than blocking all unauthenticated requests, it would be better to just leave that to the firestore rules.
The text was updated successfully, but these errors were encountered: