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
API Key not found error #57
Comments
It seems like the API key you are using is invalid. Perhaps you copied it incorrectly. You can also try to generating a new browser API key. |
Yeah – I don't know what I did here. I swear I copied it right out of the Firebase console, but alas I did end up with a weird key in there somehow. False alarm, thanks for taking a look @bojeil-google |
i am having the same problem with signup codes thank you {"error":{"code":400,"message":"API Key not found. Please pass a valid API key.","errors":[{"message":"API Key not found. Please pass a valid API key.","domain":"global","reason":"badRequest"}],"status":"INVALID_ARGUMENT"}} |
In my case the issue was that I had previously created a project with the same name. For me, since this was a new project, the easiest solution was to delete the entire project (in firebase AND in the cloud resource manager) and then create it from scratch. |
@resurge , do you mean you had two projects with literally the same value in the field called "Project name"? (in the link you pasted to the Google IAM & Admin page). I am getting the same error and my project also has the same name as a previous project, so I changed that field (ie renamed the project), but it did not fix the error. But I suspect that since you completely deleted the project, you also tried simply renaming, without success? Then what led you to the more drastic step of deleting the project? (I am reluctant to do so since mine is pretty far along). |
hi guys, I figured it out without having to delete my project. The solution was "REGENERATE KEY" in the top right of the screenshot below. |
@mephix So I'm suspecting this is an issue with firebase itself and not this library, but this was the highest ranking Google result for this error message so I thought it could be helpful to write my workaround here. |
@resurge Yes it was very helpful, you saved me somewhere between nine and infinity hours of frustration, thankyou. Hopefully this helps others too until it gets fixed. |
open firebase project overview copy the api key and paste it in your var config{ apikey =".....",...} location |
How to fetch the API key from .env.I'm working with firebase auth with react but if I'm giving key in code directly it works but if I hide my key using DOTENV it gives me an error like that....
its give me the same error
|
Hey guys I was also facing very same problem and it was kind of frustrating but I solved this just go on firebase console and then go in authentication inside sign in methods scroll down to authorized domain and remove localHost:3000 as default after that you can use your firebase link easy without any problem. |
This issue has been resolved.You need to just follow these steps
REACT_APP_FIREBASE_KEY = "my-api-key-is-here"
import * as firebase from "firebase/app";
import "firebase/auth";
const fireConfig = firebase.initializeApp({
apiKey: process.env.REACT_APP_FIREBASE_KEY,
....
});
export default fireConfig; |
I was trying to bypass login test in cypress in which the data is stored in firebase but I am getting this error {"error":{"code":400,"message":"API key not valid. Please pass a valid API key.","errors":[{"message":"API key not valid. Please pass a valid API key.","domain":"global","reason":"badRequest"}],"status":"INVALID_ARGUMENT"}} I followed this documentation I have put this in command.js page }); and created .env file separately and added the API there |
What u did |
Hello,
I am following the README instructions very closely but cannot get email/password authentication to work for the life of me:
When choosing my email address from the dropdown, I get the following error:
When looking at the HTTP traffic, I see that the API key is in fact present:
Any ideas? Totally stuck on this – thanks in advance!
The text was updated successfully, but these errors were encountered: