R

38

370

We're seeing a few exceptions with the message Default FirebaseApp is not initialized in this process com.example.app. Make sure to call FirebaseApp.initializeApp(Context) first. in our Android app in which we just added Firebase Remote Config.

The stack trace is as follows:

Fatal Exception: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.example.app. Make sure to call FirebaseApp.initializeApp(Context) first.
       at com.google.firebase.FirebaseApp.getInstance(Unknown Source)
       at com.google.firebase.remoteconfig.FirebaseRemoteConfig.getInstance(Unknown Source)
       at com.example.app.fragments.SomeFragment.updateFooter(SourceFile:295)
       at com.example.app.fragments.SomeFragment.onCreateView(SourceFile:205)
       at android.support.v4.app.Fragment.performCreateView(SourceFile:2080)
       at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1108)
       at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1290)
       at android.support.v4.app.BackStackRecord.run(SourceFile:801)
       at android.support.v4.app.FragmentManagerImpl.execSingleAction(SourceFile:1638)
       at android.support.v4.app.BackStackRecord.commitNowAllowingStateLoss(SourceFile:679)
       at android.support.v4.app.FragmentPagerAdapter.finishUpdate(SourceFile:143)
       at android.support.v4.view.ViewPager.populate(SourceFile:1240)
       at android.support.v4.view.ViewPager.populate(SourceFile:1088)
       at android.support.v4.view.ViewPager.setAdapter(SourceFile:542)
       at com.example.app.SomeActivity.onSomeAsyncCallback(SourceFile:908)
       at com.example.app.SomeDataRetriever.onAsyncHttpCompleted(SourceFile:72)
       at com.example.app.io.AsyncHttp.onPostExecute(SourceFile:141)
       at com.example.app.io.AsyncHttp.onPostExecute(SourceFile:19)
       at android.os.AsyncTask.finish(AsyncTask.java:679)
       at android.os.AsyncTask.access$500(AsyncTask.java:180)
       at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:696)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:150)
       at android.app.ActivityThread.main(ActivityThread.java:5665)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:799)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:689)

This is version 9.6.1 and we're also using other Firebase components:

compile 'com.google.firebase:firebase-ads:9.6.1'
compile 'com.google.firebase:firebase-config:9.6.1'
compile 'com.google.firebase:firebase-invites:9.6.1'
compile "com.google.firebase:firebase-messaging:9.6.1"

As I can see from the documentation and the Javadoc we shouldn't have to do any manual initialization in our case.

The exception happens on Android 4-6 on a variety of devices.

Edit:

I see this question gets a little bit of attention. I think this explanation can be interesting for some of you: https://firebase.googleblog.com/2016/12/how-does-firebase-initialize-on-android.html

Rachele answered 17/10, 2016 at 8:19 Comment(16)

Try searching SO for "Default FirebaseApp is not initialized". There are a lot of different circumstances that might cause this. – Babbage 17/10, 2016 at 18:22

Yeah, I have. Didn't find any with matching circumstances, so that's why I'm asking. Could've mentioned that in the Q. – Rachele 17/10, 2016 at 19:18

Are you able to produce a minimal example the reproduces this problem, and show the manifest, build.gradle, and Activity? – Babbage 17/10, 2016 at 20:35

Do you initialise Firebase in a ContentProvider or in your Application class? – Tourney 17/10, 2016 at 22:15

We initialize Firebase in our Application class. We'll move that. However, the app should in theory be a single process app. In that case nothing should be wrong, should it? Looking at the numbers now, the exception has happened to 26 of more than 1 million users that should've run the same callback as in the stack trace. – Rachele 18/10, 2016 at 12:14

Hi, may I know do you solve your problem? We have the same problem here too. We are using com.google.firebase:firebase-core:10.0.1 and FirebaseRemoteConfig.getInstance. We don't call FirebaseApp.initializeApp explicitly as it is not stated in documentation. Our code works for most users. Except, we experience similar crash log, for a very few users using Android 4.1 – Chitkara 4/1, 2017 at 15:47

I experience the same problem for a small percentage of players. Using the latest 10.0.1 – Asquint 6/1, 2017 at 7:58

We're seeing this in like 0.0025% of our users.. So it isn't a big issue, but it still is a few thousand users. – Rachele 6/1, 2017 at 9:15

@DougStevenson Any thoughts on why me and dmitry would see this for just a very small part of our user base? You asked for a minimal example to reproduce the problem, but it seems like we need a big user base to reproduce it. Personally I haven't seen this issue on any our devices. – Rachele 6/1, 2017 at 9:32

@RoySolberg I read that blog post, but my app is single-process. And I am pretty sure that the most of us would have preferred calling initialiser instead of getting a "magical" bug affecting some users but not happening on our test devices :-( – Asquint 6/1, 2017 at 10:24

@Asquint Agreed. I wonder if it could be Firebase (or maybe some other lib we're using) firing up a second process and then our apps wouldn't be single-process any longer. – Rachele 6/1, 2017 at 13:31

Those who mentioned that they are using FirebaseRemoteConfig.getInstance() shouldn't worry because internally .getInstance does call FirebaseApp var0 = FirebaseApp.getInstance();. – Tanganyika 21/7, 2017 at 9:28

btw, I'm facing same issue while executing test cases for one of FirebaseMessage class component. No issue in actual code functionality, it's working as expected. Any suggestion ! – Stenosis 2/7, 2018 at 8:28

We are also facing this issue just on line - "val firebaseRemoteConfig = FirebaseRemoteConfig.getInstance()" – Fib 3/4, 2020 at 14:33

Only Firebase assistant can correct the dependencies, and connect the project with the Firebase developers console. It also provides the necessary code. – Denudate 1/5, 2020 at 4:20

For me what worked was actually updating Android Studio to the latest version. – Mccreary 17/3 at 5:25

C

174

I had this same issue some time ago.

You're trying to get an instance of Firebase without initialize it. Please add this line of code before you try to get an instance of Firebase, in your main function or a FutureBuilder:

FirebaseApp.initializeApp();

Catechin answered 10/1, 2017 at 13:11 Comment(18)

Did you add this to an extended Application class and onCreate or in your activity before using an Firebase API? – Marismarisa 20/3, 2017 at 15:54

@Marismarisa Only in ExtendedApplication.onCreate(). – Rachele 10/4, 2017 at 7:11

@RoySolberg Was this enough to completely solve the issue in your case? – Medial 11/12, 2017 at 8:24

@Sébastien Yes. We have not seen the issue since we added that line. – Rachele 11/12, 2017 at 11:57

Well, this did not work for me (still a few crashes in production). I will try adding the init code to my first Activity onCreate(). – Medial 13/12, 2017 at 8:18

@Sébastien using in main class with this instead of contexts will resolve the issue give it a try – Halland 12/2, 2018 at 10:23

It's important to note that besides this initialization, the google services must be applied as follows: apply plugin: 'com.google.gms.google-services' – Westhead 7/3, 2018 at 20:29

in which file do i have to add this MainActivity.java? – Dyeline 26/7, 2018 at 7:31

For me version com.google.gms:google-services:4.1.0 was crashing but com.google.gms:google-services:4.0.1 worked – Important 3/10, 2018 at 9:5

PSIXO's solution worked for me as well. Change the project's build.gradle to use classpath 'com.google.gms:google-services:4.0.1' instead of 4.1.0 and the crash no longer happens in my app (which is just the sample MLKit starter app). – Faa 16/11, 2018 at 20:27

Downgrading google service plugin from version 4.1.0 to version 4.0.1 in my project's build.gradle worked for me. classpath 'com.google.gms:google-services:4.0.1' – Muskogean 5/3, 2019 at 18:31

Using following latest versions helped me resolve the issue. No need to downgrade :) classpath 'com.android.tools.build:gradle:3.4.2' classpath 'com.google.gms:google-services:4.3.0' – Cliffcliffes 10/7, 2019 at 13:2

I tried adding it in my SplashActivity but my app crashes when receiving the push notification. – Rhigolene 24/7, 2019 at 9:19

@Rhigolene you should add it to your main activity, your Splash Activity only runs when you open the app. – Catechin 24/7, 2019 at 11:16

@GabrielLidenor thank you it doesn't crash now but it still doesn't display in my emulator. – Rhigolene 25/7, 2019 at 7:43

Only Firebase assistant can correct the dependencies, and connect the project with the Firebase developers console. It also provides the necessary code. – Denudate 1/5, 2020 at 4:19

Guys exactly in which file do we have to put FirebaseApp.initializeApp(this); ??? – Cardie 23/5, 2020 at 18:28

pamobo0609's solution about adding the google play services plugin solved it, has nothing to do with initializing anything – Notions 13/11, 2020 at 11:14

S

490

Make sure to add to your root-level build.gradle

buildscript {
    // ...
    dependencies {
        // ...
        classpath 'com.google.gms:google-services:4.3.2'
    }
}

Then, in your module level Gradle file (usually the app/build.gradle), add the 'apply plugin' line at the bottom of the file to enable the Gradle plugin:

apply plugin: 'com.android.application'

android {
  // ...
}

dependencies {
  // ...
  implementation 'com.google.firebase:firebase-core:9.6.1'
  // Getting a "Could not find" error? Make sure you have
  // the latest Google Repository in the Android SDK manager
}

// ADD THIS AT THE BOTTOM
apply plugin: 'com.google.gms.google-services'

As said in documentation. I had exception as in a question above when forgot to add this in my gradle files.

Sullen answered 17/10, 2016 at 11:22 Comment(12)

Check, and check. Just verified that we the Gradle files as described. I should mention that the code works okay for a lot of users. – Rachele 17/10, 2016 at 13:19

It could be that you are mixing your library versions. I had the same issue when I tried using compile 'com.google.firebase:firebase-core:9.8.0' so I changed to compile 'com.google.firebase:firebase-core:9.6.0' to match my other libraries. Original answer You're mixing Firebase SDK versions. as explained – Wastebasket 22/11, 2016 at 17:53

'apply plugin: 'com.google.gms.google-services' worked for me. – Zane 11/12, 2016 at 8:15

Did not help in my case. And the issue affects extremely small percentage of players. So, most likely it is not a problem with the code or settings, but with interoperability with play services installed n the user's devices :-( – Asquint 6/1, 2017 at 8:0

thanks :) I forget to add this line in build.gradle : apply plugin: 'com.google.gms.google-services' – Ascender 9/3, 2017 at 20:30

why does the plugin have to be last? – Nap 10/3, 2017 at 21:38

This was the only problem, no need to initialize either – Gnosis 24/8, 2018 at 15:36

If an answer has this many upvotes it should be the first answer in the list. In my case I made the mistake of putting the apply plugin in the project level gradle file. – Figge 10/5, 2020 at 9:22

apply plugin: 'com.google.gms.google-services' this worked for me as well – Histrionic 14/7, 2021 at 5:42

This worked for me as well after a frustrated search.. thank you – Subterranean 20/8, 2021 at 4:10

There is an issue I am also using apply plugin: 'com.google.firebase.firebase-perf' apply plugin: 'com.google.firebase.crashlytics' These are needed below apply plugin: 'com.google.gms.google-services' If I keep these three plugins on top they do work, but I am left with the issue If I move them to bottom project build fails – Rase 16/11, 2022 at 4:10

apply plugin: 'com.google.gms.google-services' solved my issue – Noel 6/1, 2023 at 9:58

C

174

I had this same issue some time ago.

You're trying to get an instance of Firebase without initialize it. Please add this line of code before you try to get an instance of Firebase, in your main function or a FutureBuilder:

FirebaseApp.initializeApp();