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:

{
  "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"
  }
}

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.
I just retry until it works in 30s intervals. But that means it can take quite some time until the subscription becomes active.

In our case it always fails.

Yes, we got this same error too, since last 4-5 hours. it was working correctly before.

Getting this error message since yesterday. It was working perfectly in both extension and react app.
An error occurred while retrieving token. FirebaseError: Messaging: A problem occurred while subscribing the user to FCM: 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. (messaging/token-subscribe-failed). at http://localhost:3000/static/js/vendors~main.chunk.js:4303:33 at step (http://localhost:3000/static/js/vendors~main.chunk.js:61747:17) at Object.next (http://localhost:3000/static/js/vendors~main.chunk.js:61678:14) at fulfilled (http://localhost:3000/static/js/vendors~main.chunk.js:61633:24)

It was working correctly yesterday, but it's not working now on my react app.
I tried to delete the app from firebase and create it again but still fails.
@schummar Have you found a solution?

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
1]. Old users, whose token has expired
2]. New users, whose new token is to be registered.
We checked some of our partners implementing server side token registration ... it looks like its working fine for them. firebase team should atleast inform us if there is any update in this regard. Since yesterday no new subscribers for our website.

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.
The workaround on our side was to retry messaging.getToken 5 times at 3 seconds intervals. If that fails, we notify the user to try again later.

I've checked the requests going to https://fcmregistrations.googleapis.com/v1/projects/{PROJECT_ID}/registrations and the payload is identical between succeeding and failing requests. The same goes for x-client-data and x-goog-firebase-installations-auth, they are identical.

This also happens to me :(
Yesterday it was normal and today I'm getting this error too.
Does anyone have any updates or where can we try to get a status?
I just created a new account for test and entered the new credentials but the error remains.

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

No report in the status page neither

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.

I have the same issue since yesterday

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?

Another thing to add:

After many failures, I've managed to get some registrations.

• Sending notifications, didn't fail, but also didn't reach the destination.
• If I try to generate a new token, I first get an FAIL to delete the current registration.
• Than, I get the same stuck problem, fails 90% of trying to get new tokens.

The fail to delete the current registration:

PS.: I've never called delete before.
If I get a new token again, and try to delete, same problem.

copying from: #2364 (comment)

I ran into this issue this morning. (1st Jul)

POST https://fcmregistrations.googleapis.com/v1/projects/my-project-id/registrations 401 (Unauthorized)
<call-stack>
index.html:630 Unable to get permission. FirebaseError: Messaging: A problem occurred while subscribing the user to FCM: 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. (messaging/token-subscribe-failed).
    at api.ts:67
    at tslib.es6.js:102
    at Object.next (tslib.es6.js:83)
    at r (tslib.es6.js:73)

here is how it happened

• created client-1, got notifications working.
• for some reason I happened to delete the client-1 from firebase console.
• created client-2
• copied the new firebaseConfig from console.
• got the error now.
• Noticed, the Web API Key is the same for both the clients. there are not restrictions on the web api key.
• I have followed everything I could (unregister service worker)

Firebase JS Version: 8.6.8

scripts imported like so:

<script src="https://www.gstatic.com/firebasejs/8.6.8/firebase-app.js"></script>
<script src="https://www.gstatic.com/firebasejs/8.6.8/firebase-messaging.js"></script>
var firebaseConfig = {
  // CONFIG COPIED FROM FIREBASE CONSOLE.
};

firebase.initializeApp(firebaseConfig);

const messaging = firebase.messaging();


  messaging
    .getToken({ vapidKey: "MY_PUB_KEY" })
    .then((currentToken) => {
      console.log(currentToken)
    })
    .catch(function (err) {
      // handle error
    });

We have identified and believe we have resolved the issue.

Confirmed the resolution in multiple devices

Now the error is sending messages to the devices, not getting the token

We have identified and believe we have resolved the issue.

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?
I am not getting the error message but I am also not able to generate the token

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...

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.
On my end, the errors have subsided without any change to my implementation (version 8.7.0)

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