-
Notifications
You must be signed in to change notification settings - Fork 885
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
getToken succeeds or fails randomly #5081
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
I am also seeing this issue, although it occurs every time in our environment. Receiving the following error, and nothing has changed in our application in regards to firebase integration:
|
We are getting this error too. {
"error": {
"code": 401,
"message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
"status": "UNAUTHENTICATED"
}
} |
@schummar have you found a solution? |
No solution, only a not-so-great workaround. |
In our case it always fails. |
Getting this error message since yesterday. It was working perfectly in both extension and react app. |
It was working correctly yesterday, but it's not working now on my react app. |
We are also seeing this error a lot, first occurrence was at June 29, 2021 4:44:25 AM UTC. We have also made no changes in this timeframe. In my testing, the error occurs probably 95% of the time. Eventually a call will succeed. |
We are also facing same issue since yesterday evening (Aroud 5PM IST). There is no problem for existing active subscribers, but this is affecting our new users and old users We have a feeling that they replaced fcm token registration authentication code with login authentication for google signin. |
Started implementing push notifications 2 days ago for our app and spent way too much debugging this thinking that it's an issue on our side (give me 8 hours of my life back pls 😅) Our calls usually fail 80% of the time. I've checked the requests going to |
This also happens to me :( |
I'm getting a 401 on the call to registrations as well. Just noticed it yesterday. It's happening in production and no code has changed there. |
Same. Getting 401. It appeared to work until I unregistered the service worker during testing. Now it continuously throws the same error. No code or api changes on my side |
I am getting this issue since beginning , never given successful token, I tried with new vapidKey as well |
We are currently looking into this issue internally. We'll keep this thread posted for any updates. |
It seems by now all of our requests fail all the time. Yesterday it felt like 50/50. So is it possible some update/cert/whatever has been rolled out to the servers gradually in the last days? |
copying from: #2364 (comment) I ran into this issue this morning. (1st Jul)
here is how it happened
Firebase JS Version: 8.6.8 scripts imported like so:
|
We have identified and believe we have resolved the issue. |
Confirmed the resolution in multiple devices |
Today morning I Could see token. |
Finally ... a sigh of relief ... thank you team firebase .. :) |
I can confirm, that so far it looks good. I could not observe any more failures this morning. |
@schummar Did you change anything on your end? |
No changes, it just works now. |
Thank you for informing |
Any idea in which releases will it land? I am particularly interested in v9.0.0-beta... |
By the looks of it, the issue was backend related. |
Per checking, the issue is now resolved. This is a backend issue and we didn't change anything in the current JS SDK. |
finally works |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
getToken seems to randomly fail without plausible explanation. I run it with the exact same config on the same device multiple times in a row (call deleteToken in between).
Some requests are successful, some fail, seemingly at random. I cannot make out any significant difference between failing and successful requests. Same config, request headers contain same values for
x-goog-api-key
andx-goog-firebase-installations-auth
Request payloads have the same shape and same value for
applicationPubKey
.The returned error is:
Steps to reproduce:
Relevant Code:
Example reponse overview
To test it I'm running a loop of
And the result is:
The text was updated successfully, but these errors were encountered: