-
Notifications
You must be signed in to change notification settings - Fork 892
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 is missing required authention credential.Expected OAuth 2 access token cookie or other valid authentication credential. #8513
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
I saw same issue has been raised 3 years back but didn't see any solution for that, can we get more clarity on this issue as in the comment of this issue https://github.com/firebase/firebase-js-sdk/issues/5081 its mentioned that its a backend issue and resolved without doing any changes in js sdk. |
I see "invalid argument" in your screenshotted error message. In your original post I see "Request is missing required authentication credential.". Are these happening at the same time or are you getting two different errors? Is this a web app or a Node app? What is the value of |
@hsubox76 its a react web app,The screenshot error message i am getting in browser console and whatever in the original post i am getting that in network logs. |
How do you have access to process.env if it's a web app? What do you mean by "network logs"? Are these two errors happening at the same time? Is this still a problem if you use the latest version of Firebase? I see the version you're using is 2 years old. |
@hsubox76 i don't have access to process.env instead i am making use of window object. |
If you are in a browser environment where the built-in The screenshot of the network request errors you shared shows a 400 bad request error mentioning that the request contains an invalid argument. Is the issue you are reporting caused by a 401 Unauthorized of a 400 bad request? |
Could you elaborate on what you mean here? My understanding is that there's another issue with FCM that was resolved three years ago- how does this relate to this issue? |
@hsubox76 @dlarocque sorry my bad in the below code snippet |
@hsubox76 @dlarocque Actually i am running selenium for doing FCM registration for 200 users and its failing(giving above error) only for 2-3 users. |
@amitromi9470 Could you please respond to my second question here: #8513 (comment) |
@dlarocque Please refer this comment #8513 (comment) |
I am not sure why it would fail for ~1% of registrations, assuming that they are all done under the same conditions. For us to be able to determine whether this is a bug with the Firebase JS SDK, we need to be able to reproduce this issue. The snippet you have shared works reliably for me. Would you be able to share exact steps we can follow to reproduce this issue? If you're not able to share steps for a reproduction, I recommend checking out Firebase Support. |
Operating System
Ubuntu 22.04.4
Environment (if applicable)
Chrome Version 126.0.6478.182, react: 17.0.1
Firebase SDK Version
firebase: 9.9.4
Firebase SDK Product(s)
Auth
Project Tooling
React, Javascript.
Detailed Problem Description
I am trying to register FCM token for 200 users,But out of 200 users for some users its failing to register token with 401 error.This is the error i am getting
{
"error":{
"code":401,
"message":"Request is missing required authention credential.Expected OAuth 2 access token cookie or other valid authentication credential. see https://developers.google.com/identity/sign-in/web/devconsole project.",
"status": UNAUTHORISED
}
}
Steps and code to reproduce issue
const firebaseApp = initializeApp(firebaseConfig);
export const messaging = getMessaging(firebaseApp);
let swRegistration;
const requestForToken = async (registerFCMToken) => {
try {
swRegistration = await navigator.serviceWorker.register(
${process.env.PUBLIC_URL}/firebase-messaging-sw.js
);messaging.swRegistration = swRegistration;
} catch (err) {
console.log('An error occurred while retrieving token. ', err);
throw err;
}
};
The text was updated successfully, but these errors were encountered: