Invalid api key error

@nicolasgarnier — resolved this myself please go ahead and close this issue

Replaced the API key and it worked

I’m glad things worked out for you!

@nicolasgarnier
Hi Nicolas,
I’m quite new to firebase and would like to use authentication service for Google in a simple Angular2 test app.

But get the error: message: «Your API key is invalid, please check you have copied it correctly.»}

I would appreciate if you help me with it.

Regards,
Rozita

@nicolasgarnier I am getting these errors and i have checked and checked the API Key (even though i just copied and pasted it). Would could be causing this?

Regards,

Terry

I am also getting the error @terrysmyth is getting.
{code: "auth/invalid-api-key", message: "Your API key is invalid, please check you have copied it correctly."}

@Paloman fixed it by re-copying and pasting my API key, so try that

@eddyekofo94 I did :/ but it didn’t work… if you don’t mind me asking, are you using the google-services.json file to import the key? or directly through initialize app? also is this a native android app? thanks for all your help

@Paloman
Yes I am the google-services.json to import the key, I am using ASP.Net Core. But sorry I don’t know how it is implemented in Android.
I don’t know how it works on Android, if you’re still stuck I can go look it up later.

I am getting this error in core javascript.

I too am getting this error. Using Google Authentication works perfectly in develop but not in production after deploy. I’m at a loss to figure out why and/or where this needs to be configured.

Replaced the API key and it worked

Yes, but where?

I have the solution finally, just check how you have imported your firebaseConfig.js where you have initilize your firebase.
most of the case we export default firebaseConfig and import it as a object

import {firebaseConfig} from ‘./src/config/FirebaseConfig’; ===== Wrong Order
import FirebaseConfig from ‘./src/config/FirebaseConfig’; ===== Correct Order

Hello, this is my current config file

const config = {
  apiKey: process.env.API_KEY,
  authDomain: process.env.AUTH_DOMAIN,
  databaseURL: process.env.DBURL,
  projectId: process.env.PID,
  storageBucket: process.env.BUCKET,
  messagingSenderId: process.env.MSGID
};

export default config;

and I am using it like so-

import firebase from "firebase/app";
import config from "./config";

firebase.initializeApp(config);

When I use the key string directly in the config file it works but not when it is used as my env variables..

This may or may not be of any use to you, but are the env variables set in a .env file in the root dir?

@bhaskar-nair2

My firebase.js

const config = {
  apiKey: process.env.REACT_APP_API_KEY,
  authDomain: process.env.REACT_APP_AUTH_DOMAIN,
  databaseURL: process.env.REACT_APP_DATABASE_URL,
  projectId: process.env.REACT_APP_PROJECT_ID,
  storageBucket: process.env.REACT_APP_STORAGE_BUCKET,
  messagingSenderId: process.env.REACT_APP_MESSAGING_SENDER_ID,
};

.env file

REACT_APP_API_KEY="key"
REACT_APP_AUTH_DOMAIN="domain"
REACT_APP_DATABASE_URL="url"
REACT_APP_PROJECT_ID="id"
REACT_APP_STORAGE_BUCKET="bucket"
REACT_APP_MESSAGING_SENDER_ID="id"

Had the same problem while building a react-native app:
Before:
export const firebaseConfig = { apiKey: "", etc etc };

After:
export default firebaseConfig = { apiKey: "", etc etc };

Replaced the API key and it worked

Where should I reset the API? I never assigned any authentication API anywhere in Firebase Console.

I’m using Flutter and received this error after migrate to AndroidX and switch to another notebook (the notebook where I did migration was working perfectly fine).

[ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: PlatformException(FirebaseException, An internal error has occurred. [ API key expired. Please renew the API key. ], null)

[ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: PlatformException(FirebaseException, An internal error has occurred. [ API key expired. Please renew the API key. ], null)
E/flutter ( 6509): #0      StandardMethodCodec.decodeEnvelope 
package:flutter/…/services/message_codecs.dart:564
E/flutter ( 6509): #1      MethodChannel.invokeMethod 
package:flutter/…/services/platform_channel.dart:302
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #2      FirebaseAuth.signInWithCredential
package:firebase_auth/src/firebase_auth.dart:278
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #3      AuthProvider.signInFirebase
package:wavecheck/…/resources/auth_provider.dart:117
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #4      Repository.signInFirebase
package:wavecheck/…/resources/repository.dart:35
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #5      AuthenticationBloc.startApp.<anonymous closure>
package:wavecheck/…/blocs/authentication_bloc.dart:55
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #6      _rootRunUnary  (dart:async/zone.dart:1132:38)
E/flutter ( 6509): #7      _CustomZone.runUnary  (dart:async/zone.dart:1029:19)
E/flutter ( 6509): #8      _FutureListener.handleValue  (dart:async/future_impl.dart:126:18)
E/flutter ( 6509): #9      Future._propagateToListeners.handleValueCallback  (dart:async/future_impl.dart:639:45)
E/flutter ( 6509): #10     Future._propagateToListeners  (dart:async/future_impl.dart:668:32)
E/flutter ( 6509): #11     Future._complete  (dart:async/future_impl.dart:473:7)
E/flutter ( 6509): #12     _SyncCompleter.complete  (dart:async/future_impl.dart:51:12)
E/flutter ( 6509): #13     _rootRunUnary  (dart:async/zone.dart:1132:38)
E/flutter ( 6509): #14     _CustomZone.runUnary  (dart:async/zone.dart:1029:19)
E/flutter ( 6509): #15     _FutureListener.handleValue  (dart:async/future_impl.dart:126:18)
E/flutter ( 6509): #16     Future._propagateToListeners.handleValueCallback  (dart:async/future_impl.dart:639:45)
E/flutter ( 6509): #17     Future._propagateToListeners  (dart:async/future_impl.dart:668:32)
E/flutter ( 6509): #18     Future._complete  (dart:async/future_impl.dart:473:7)
E/flutter ( 6509): #19     _SyncCompleter.complete  (dart:async/future_impl.dart:51:12)
E/flutter ( 6509): #20     _AsyncAwaitCompleter.complete  (dart:async-patch/async_patch.dart:28:18)
E/flutter ( 6509): #21     _completeOnAsyncReturn  (dart:async-patch/async_patch.dart:294:13)
E/flutter ( 6509): #22     AuthProvider.signInGoogleSilently (package:wavecheck/src/resources/auth_provider.dart)
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #23     Repository.signInGoogleSilently
package:wavecheck/…/resources/repository.dart:33
E/flutter ( 6509): <asynchronous suspension>
E/flutter ( 6509): #24     AuthenticationBloc.startApp
package:wavecheck/…/blocs/authentication_bloc.dart:49
E/flutter ( 6509): #25     _AsyncAwaitCompleter.start  (dart:async-patch/async_patch.dart:49:6)
E/flutter ( 6509): #26     AuthenticationBloc.startApp
package:wavecheck/…/blocs/authentication_bloc.dart:43
E/flutter ( 6509): #27     main
package:wavecheck/main.dart:6
E/flutter ( 6509): #28     _runMainZoned.<anonymous closure>.<anonymous closure>  (dart:ui/hooks.dart:199:25)
E/flutter ( 6509): #29     _rootRun  (dart:async/zone.dart:1124:13)
E/flutter ( 6509): #30     _CustomZone.run  (dart:async/zone.dart:1021:19)
E/flutter ( 6509): #31     _runZoned  (dart:async/zone.dart:1516:10)
E/flutter ( 6509): #32     runZoned  (dart:async/zone.dart:1500:12)
E/flutter ( 6509): #33     _runMainZoned.<anonymous closure>  (dart:ui/hooks.dart:190:5)
E/flutter ( 6509): #34     _startIsolate.<anonymous closure>  (dart:isolate-patch/isolate_patch.dart:300:19)
E/flutter ( 6509): #35     _RawReceivePortImpl._handleMessage  (dart:isolate-patch/isolate_patch.dart:171:12)
E/flutter ( 6509):

Solved: Downloaded again google-services.json

@bhaskar-nair2 what was your solution? It seems that it’s not seeing my .env file

What I did
const firebaseConfig = {apiKey: '', etc, etc}
then I exported it
export deafault firebaseConfig

import
import firebaseConfig from './firebase'

This was in Angular 8

for my case I needed to restart my dev server since I entered them while it was already running

I have the solution finally, just check how you have imported your firebaseConfig.js where you have initilize your firebase.
most of the case we export default firebaseConfig and import it as a object

import {firebaseConfig} from ‘./src/config/FirebaseConfig’; ===== Wrong Order
import FirebaseConfig from ‘./src/config/FirebaseConfig’; ===== Correct Order

This is the main problem. I was also trying to load my firebaseConfig object at runtime, using the import() function, at the time of initializing my FirebaseApp. Now I don’t have this issue any more after importing the firebaseConfig object at the top of the file, as described by @akashrauniyar35

I solved it moving env variables from
now.json -> env: {}
to .env file

This may or may not be of any use to you, but are the env variables set in a .env file in the root dir?

@bhaskar-nair2

My firebase.js

const config = {
  apiKey: process.env.REACT_APP_API_KEY,
  authDomain: process.env.REACT_APP_AUTH_DOMAIN,
  databaseURL: process.env.REACT_APP_DATABASE_URL,
  projectId: process.env.REACT_APP_PROJECT_ID,
  storageBucket: process.env.REACT_APP_STORAGE_BUCKET,
  messagingSenderId: process.env.REACT_APP_MESSAGING_SENDER_ID,
};

.env file

REACT_APP_API_KEY="key"
REACT_APP_AUTH_DOMAIN="domain"
REACT_APP_DATABASE_URL="url"
REACT_APP_PROJECT_ID="id"
REACT_APP_STORAGE_BUCKET="bucket"
REACT_APP_MESSAGING_SENDER_ID="id"

Thanks, this is exactly my problem. I mistakenly put the .env file under src folder.

If anyone having problem with the .env file in react project

2 things to keep in mind

1. Make extra sure that .env with key=value pairs is located at the root of the react project

2. After creating the .env RESTART dev server so that webpack picks up the new project changes. It will rebuild the project taking into accouunt the newly created .env file. Otherwise webpack has no information that you created this file.

Replaced Api key in the json file and It worked, thnaks everyone

Another gotcha which got me:

My .env file is APPENDED in the pipeline. I forgot to add a newline (n) to the end of the .env files that are already in my repo when I added something to it.

So, if you’re appending your .env files in your pipelines which are already slightly populated in the repo itself, end in a newline.

In fact, end every file always with a newline. It’s a convention, and ignoring it apparently leads to bugs like this.

If anyone is still having trouble, what I found to work is initializing an app with a name i.e. not using the «[DEFAULT]» app and passing that app in whenever you require another firebase function. This helps prevent confusion of where which app with which key should be used.

Source of Firebase Javascript Documentation

import firebase from 'firebase';
import firebaseConfig from './firebaseConfig.js'

var app = undefined;
try {  // Check if the app already exists
	app = firebase.app("NewName");
}
catch(e) {
	app = firebase.initializeApp( firebaseConfig , "NewName");
}

console.log( firebase.auth( app ).currentUser  );

Thank you so much @abe157. You just saved me days.

I had the same issue. I solved it by doing:

1. Make sure that your filename is .env.local instead of env.local (that dot is a lot imp :P).
2. Your env file should be stored in root directory of your project instead of src or any other folder.

For some reason, it worked for me when I changed file’s name from .env.local to .env

If you are using React, my problem was that I didn’t write .env variables with REACT_APP_(name of the variable)
Pretty funny but at the same time frustrating.

Make sure you are not using quotes or commas in your .env file. I had the same issue, but fixed it after removing quotes

Solution: change the version of google services at project level gradle and sync your project and reinstall.
classpath ‘com.google.gms:google-services:4.3.0’

I solved !

1º — I went to ‘Project Settings’ and there I created an application.

2º — As I was using Docker, my NuxtJS shared the application using my ip, so I put my ip in Firebase’s authorized domains.
Even if Dokcer puts my application in the localhost url.

for my case I needed to restart my dev server since I entered them while it was already running

thank you, it was working on my live server but not on localhost but restarting the server resolved my issue, twas this easy

if someone experiencing this with Nextjs and firebase this solution may help

in next.config.js add this

module.exports = {
  env : {
    FIREBASE_API_KEY: process.env.apiKey,
    AUTH_DOMAIN: process.env.authDomain,
    PROJECT_ID: process.env.projectId,
    STORAGE_BUCKET: process.env.storageBucket,
    MESSAGING_SENDER_ID: process.env.messagingSenderId,
    APP_ID: process.env.appId,
  }
}

then in your firebase config

const firebaseConfig = {
  apiKey: process.env.FIREBASE_API_KEY,
  authDomain: process.env.AUTH_DOMAIN,
  projectId: process.env.PROJECT_ID,
  storageBucket: process.env.STORAGE_BUCKET,
  messagingSenderId: process.env.MESSAGING_SENDER_ID,
  appId: process.env.APP_ID,
}

then restart the server, it should work.

If people are still experiencing this issue, I had the same problem when using a .env.local file for all of the info for firebase what I had to do was stop the test site and restart it again so it realises there’s a new .env file I don’t know why but it worked so

Hello everyone I am actually having this problem for some reason firebase works locally but once deployed I get this error {code: «auth/invalid-api-key», message: «Your API key is invalid, please check you have copied it correctly.»} no really sure what to do?

here is my config file

import app from 'firebase/app'
import 'firebase/storage'

const config = {
    apiKey: process.env.REACT_APP_API_KEY,
    authDomain: process.env.REACT_APP_AUTH_DOMAIN,
    databaseURL: process.env.REACT_APP_DATABASE_URL,
    projectId: process.env.REACT_APP_PROJECT_ID,
    storageBucket: process.env.REACT_APP_STORAGE_BUCKET,
    messagingSenderId: process.env.REACT_APP_MESSAGING_SENDER_ID,
};

const firebase = app.initializeApp(config)

export default firebase

and here is my .env.development

REACT_APP_API_KEY=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_AUTH_DOMAIN=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_DATABASE_URL=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_PROJECT_ID=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_STORAGE_BUCKET=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_MESSAGING_SENDER_ID=xxxxxxxxxxxxxxxxxxxxxx
//everything is correct ! what is going on

and I am importing the config file correctly

import firebase from './index'

I’m having this exact same issue. @HassenH1, were you ever able to fix this?

I have same error but only in test, I have tried all solutions from here, but it’s not helping. I’m using Jest

I had the same issue. I solved it by doing:

1. Make sure that your filename is .env.local instead of env.local (that dot is a lot imp :P).
2. Your env file should be stored in root directory of your project instead of src or any other folder.

This worked for me too… kindly follow the above steps for react app and restart your local server… Thanks

In case anybody is using Github’s action to deploy to Firebase:

You most probably (.git)ignoring the .env file so Github builds your solution without those credentials. My solution was to add SpicyPizza/create-envfile to my workflow, while the ENV config was saved securely in my repo’s Actions secrets

In case you are using NextJS be aware that you need to add the NEXT_PUBLIC_ prefix to the .env vars so they are exposed to the browser, your .env.local would look something like this

NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=something.firebaseapp.com
NEXT_PUBLIC_FIREBASE_PUBLIC_API_KEY=yourapikey
NEXT_PUBLIC_FIREBASE_PROJECT_ID=yourprojectname

when i pulled my repo, there was only a .venv.deploy, adding a .env.local with the correct config fixed my issue

@code-vagabond doesn’t seems a good idea to make public your api keys

After spending hours here nothing worked for me except direct adding the string into the firebaseConfig, even checking with console the data as string was there but the sdk continues to complaining and I didn’t want to expose my keys on the file.

But actually find a simple way just apiKey: String(process.env.NEXT_PRIVATE_APIKEY), for some reason even that key being a string before String() now it works.

Another information is this was a problem only with auth sdk, firestore sdk alone works fine without any «hack»

@octavioamu hi, yes in my case I only needed my public API key for Firebase initialisation which is obviously ok to share. In your case you are trying to initialise firebase-admin I imagine

@code-vagabond true, Im not using the admin just firestore + auth but yes I guess you are controlling the access via domain allowed, but I prefer to not direct expose it on the code + manage the keys by .env file for dev vs prod scenarios.

In case you are using NextJS be aware that you need to add the NEXT_PUBLIC_ prefix to the .env vars so they are exposed to the browser, your .env.local would look something like this

NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=something.firebaseapp.com
NEXT_PUBLIC_FIREBASE_PUBLIC_API_KEY=yourapikey
NEXT_PUBLIC_FIREBASE_PROJECT_ID=yourprojectname

thanks!

Hello everyone I am actually having this problem for some reason firebase works locally but once deployed I get this error {code: «auth/invalid-api-key», message: «Your API key is invalid, please check you have copied it correctly.»} no really sure what to do?
here is my config file

import app from 'firebase/app'
import 'firebase/storage'

const config = {
    apiKey: process.env.REACT_APP_API_KEY,
    authDomain: process.env.REACT_APP_AUTH_DOMAIN,
    databaseURL: process.env.REACT_APP_DATABASE_URL,
    projectId: process.env.REACT_APP_PROJECT_ID,
    storageBucket: process.env.REACT_APP_STORAGE_BUCKET,
    messagingSenderId: process.env.REACT_APP_MESSAGING_SENDER_ID,
};

const firebase = app.initializeApp(config)

export default firebase

and here is my .env.development

REACT_APP_API_KEY=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_AUTH_DOMAIN=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_DATABASE_URL=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_PROJECT_ID=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_STORAGE_BUCKET=xxxxxxxxxxxxxxxxxxxxxx
REACT_APP_MESSAGING_SENDER_ID=xxxxxxxxxxxxxxxxxxxxxx
//everything is correct ! what is going on

and I am importing the config file correctly

import firebase from './index'

I’m having this exact same issue. @HassenH1, were you ever able to fix this?

same here, any updates on this problem?? @PurplePineapple123

saintaze

Yes thanks saintaze, that worked for me.

Using NextJS with Firebase v9. Here is my solution..

So, I have the same problem with the .env variables not working, but it does work when hard coding the string. I noticed in the .env they are single quoted when evaluated. This is dumb, but I just concatenated an empty string to the end of each process.env.VAR like so:

apiKey: process.env.API_KEY + «»;

for me it appears the difference was the api key as a single quote string ‘my-key’ and a double quote string «my-key». I think appending an empty string to the end is dumb and would love a recommendation.

Thanks @RobLMartin. your hacky solution worked for me…

Thanks @RobLMartin. your hacky solution worked for me…

Wish it wasn’t a thing.

Hello, this is my current config file

const config = {
  apiKey: process.env.API_KEY,
  authDomain: process.env.AUTH_DOMAIN,
  databaseURL: process.env.DBURL,
  projectId: process.env.PID,
  storageBucket: process.env.BUCKET,
  messagingSenderId: process.env.MSGID
};

export default config;

and I am using it like so-

import firebase from "firebase/app";
import config from "./config";

firebase.initializeApp(config);

When I use the key string directly in the config file it works but not when it is used as my env variables..

I also faced the same problem. When I used the key string directly it works but it didn’t work on environment variables.
It shows Uncaught FirebaseError: Firebase: Error (auth/invalid-api-key) error.
But, this error I solved after relocating my .env.local file in the root folder from the src folder.
You could try this way to solve this error.

oooh!!! I restart my project, and it works!

If you’re like me, I had this issue when deploying an app to Heroku. There were no issues with my code, it’s that Heroku expects you to have your config vars set on the Heroku side, so go into the panel and set your config vars in the Settings section. No need to change code or restart app, just redeploy to Heroku once the config vars are set.