FirebaseApp with name [DEFAULT] doesn't exist

Question

After migrating to Firebase Cloud Messaging.When opening my app it crashes and throws an error saying java.lang.IllegalStateException: FirebaseApp with name [DEFAULT] doesn't exist. I already put my new google-services.json and update my SDK.

Here's my MainActivity

public class MainActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

//Check Google play service
    GoogleApiAvailability googleAPI = GoogleApiAvailability.getInstance();
    int resultCode = googleAPI.isGooglePlayServicesAvailable(this);

    if (resultCode != ConnectionResult.SUCCESS) {
        if (GooglePlayServicesUtil.isUserRecoverableError(resultCode)) {
            GooglePlayServicesUtil.getErrorDialog(resultCode, this,
                    PLAY_SERVICES_RESOLUTION_REQUEST).show();
        } else {
            Log.e(LOG_TAG, "This device is not supported.");
            finish();
        }
    }

    Log.i(TAG, "InstanceID token: " + FirebaseInstanceId.getInstance().getToken());

}
}

score 115 · Accepted Answer · answered May 21 '16 at 11:09

115

Please do double check, you added

apply plugin: 'com.google.gms.google-services'

at the bottom of app's gradle file and then clean and rebuild the project

answered May 21 '16 at 11:09

Venkatesan

1,174
1
8
3

I removed the `apply plugin: 'com.google.gms.google-services'` from my app gradle but encounter a new error when calling `FirebaseInstanceId.getInstance().getToken()` in my `MainActivity` my app crashes. – natsumiyu May 23 '16 at 00:57
1

my bad... i needed to add the `apply plugin: 'com.google.gms.google-services' ` ? trying to add it i still encounter error. it says `Didn't find class "com.google.android.gms.dynamite.descriptors.com.google.firebase.auth.ModuleDescriptor"` – natsumiyu May 23 '16 at 02:17
Hi Mori, you can ignore this error as of now and they will fix this issue in the next release. thats what firebase team says :) . – Venkatesan May 25 '16 at 07:35
When I add this I get: "Error:Execution failed for task ':app:mergeModernDebugResources'. > [string/google_api_key] //app/src/main/res/values/defaults.xml [string/google_api_key] //app/build/generated/res/google-services/modern/debug/values/values.xml: Error: Duplicate resources" I also did not see this step in the setup or migration guides for FCM. Do you have a link I may have missed? – C Nick Jun 14 '16 at 14:48
1

Flutter may require `flutter clean & flutter run` as suggested in the answer as well. – Nae Dec 25 '18 at 14:34
1

What if I use Firebase Java Admin? (Java Backend and not Android client app) – user924 May 30 '19 at 19:59

score 21 · Answer 2 · answered Jul 24 '16 at 04:08

Not sure, if it is relevant here. But there is another scenario when this crash can happen.

If your app has a service (with different process) and you're creating your own Application class, the service and the foreground app will use the same Application class (not same instance) to initialize. Now when I am using com.google.firebase:firebase-crash dependancy to handle crashes, it creates a background service your.app.packagename:background_crash. For some reason, this was inducing crashes on my app. Specifically, because in my Application class, I was making a call like,

FirebaseDatabase.getInstance().setPersistenceEnabled(true);

I am assuming, the background service when initing with our Application class, somehow Firebase is not initialized. To fix this, I did

if (!FirebaseApp.getApps(this).isEmpty())
        FirebaseDatabase.getInstance().setPersistenceEnabled(true);

This also happens with ads. If a user clicks on an ad then returns to the app Firebase with no longer be available. — theJosh, Sep 29 '16 at 22:31
@Codevalley, In my case, there was another process (Adobe Creative SDK Image Editor) called app:editor. It was using same application class, thus trying to get token from non-existing firebase app. Checking before getting token solved my problem. Thank you so much! :) — rzaaeeff, Jul 26 '17 at 11:57

score 12 · Answer 3 · answered Jun 27 '16 at 17:55

12

I've had similar problem, and for me it was a bug/problem with manifest merger. I've found out that FirebaseInitProvider has not been injected into final manifest file because of tools:node="replace" in my app's manifest file. So, try to remove this xml tag and FirebaseInitProvider will be injected and Firebase can be initialized properly.

answered Jun 27 '16 at 17:55

jmodrako

334
2
6

can you please update your answer for those who are not much familier with merger tool @jmodrako – Shubham AgaRwal Jun 30 '16 at 16:37
Currently i have updated to tools:replace="android:name" instead of tools:node="replace". hope that help – Shubham AgaRwal Jun 30 '16 at 16:44

score 11 · Answer 4 · answered Jun 24 '16 at 13:19

build.gradle file:

buildscript {
    repositories {
        jcenter()
        mavenLocal()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.1.2'
        classpath 'com.google.gms:google-services:3.0.0'
    }
}

allprojects {
    repositories {
        jcenter()
        mavenLocal()
    }
}

\app\build.gradle file:

apply plugin: 'com.android.application'

android {
    ..
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    ..
    compile 'com.google.firebase:firebase-core:9.0.2'
    compile 'com.google.firebase:firebase-messaging:9.0.2'
}

apply plugin: 'com.google.gms.google-services'

Error:(90, 0) Plugin with id 'com.google.gms.google-services' not found. — Gilberto Ibarra, Nov 01 '16 at 23:35

score 10 · Answer 5 · edited May 23 '17 at 10:31

10

@jmodrako answer solved my problem... tools:node="replace" to tools:node="merge"

Explained... on AndroidManifest.xml

From

<application
...
tools:node="replace">

To

<application
...
tools:node="merge">

Merge problems with library themes? Build problems solved using tools:replace="android:theme"

Credits to https://stackoverflow.com/a/38060272/2765087

edited May 23 '17 at 10:31

Community

1
1

answered Sep 08 '16 at 03:06

Carlos Eduardo Liedtke Borges

101
1
5

score 2 · Answer 6 · answered Jun 29 '16 at 08:37

2

Move your firebase initialization inside the onCreate of Application class. Also if you have enabled offline persistence, FirebaseDatabase.getInstance().setPersistenceEnabled(true) should come before any other initializations.

answered Jun 29 '16 at 08:37

Ramya Ramesh

299
3
18

clicked down vote accidentally now so not allowing me to upvote :( – Developine Aug 23 '16 at 11:58

score 2 · Answer 7 · answered Jul 07 '19 at 16:30

2

Verify all configurations as below:

1-firebase project setting: google-services.json is correct?

2- add firebase SDK

3- clean - rebuild your project

hopefully, this helps!

answered Jul 07 '19 at 16:30

Mr Special

1,576
1
20
33

score 2 · Answer 8 · answered May 16 '20 at 15:32

2

Add the following line to app/build.gradle

apply plugin: 'com.google.gms.google-services'  // Google Services plugin

And the following line to project build.gradle

classpath 'com.google.gms:google-services:4.3.3'

answered May 16 '20 at 15:32

user1188867

3,726
5
43
69

score 0 · Answer 9 · answered May 25 '16 at 08:50

0

Android Studio

apply plugin: 'com.google.gms.google-services' (build.gradle - Module layer)
Menu~>Build~>CleanProject

Works for me ok.

answered May 25 '16 at 08:50

Maxim Firsoff

2,038
22
28

score 0 · Answer 10 · edited Oct 29 '18 at 14:01

0

In your dependency just add:

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
...
compile 'com.google.firebase:firebase-core:9.0.2'
compile 'com.google.firebase:firebase-messaging:9.0.2'
}

apply plugin: 'com.google.gms.google-services'

edited Oct 29 '18 at 14:01

Biswajit Roy

508
2
7
19

answered Jul 28 '16 at 19:51

pavel

1,603
22
19

score 0 · Answer 11 · edited Jan 11 '18 at 10:33

0

Register your application in Firebase and copy the google-services.json to your root project.

Apply classpath 'com.google.gms:google-services:3.1.0 to you root build.gradle.

Apply apply plugin: 'com.google.gms.google-services to your project gradle.

edited Jan 11 '18 at 10:33

pRaNaY

24,642
24
96
146

answered Jun 16 '17 at 11:16

score 0 · Answer 12 · answered Dec 13 '18 at 10:55

0

Change the Build Action (GoogleServicesJson) to the File Name Google-Services.Json.

answered Dec 13 '18 at 10:55

Abdul basha

16
2

score 0 · Answer 13 · answered Mar 07 '19 at 06:01

In my case I was not initializing Firebase on app startup, I had to do the following to resolve it

@Service
public class FirebaseSetup implements CommandLineRunner {
    public void run(String... args) throws Exception {
        initializeFirebase();
    }
    private void initializeFirebase() throws FileNotFoundException, IOException {
        FileInputStream serviceAccount = new FileInputStream(ResourceUtils.getFile("classpath:ssf1-v1-firebase-adminsdk-zr72u-afcb5bc13b.json"));
        FirebaseOptions options = new FirebaseOptions.Builder().setCredentials(GoogleCredentials.fromStream(serviceAccount)).build();
        FirebaseApp.initializeApp(options);
    }
}

score 0 · Answer 14 · answered Feb 06 '21 at 07:11

Add classpath 'com.google.gms:google-services:3.0.0' to build.gradle

dependencies {
        ..
        classpath 'com.google.gms:google-services:3.0.0'
    }

Add this at the end of the app\build.gradle

apply plugin: 'com.google.gms.google-services'

This worked for me

FirebaseApp with name [DEFAULT] doesn't exist

14 Answers14

Linked

Related