FirebaseApp is not initialized in this process

Question

FirebaseApp is not initialized in this process

hram opened this issue 3 years ago · 66 comments

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
For help troubleshooting your application that does not fall under one
of the above categories, reach out to the personalized
Firebase support channel.

[REQUIRED] Step 2: Describe your environment

Android Studio version:
Firebase Component: com.google.firebase:firebase-bom:31.2.2
Component version:

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

Add annotation @AddTrace to function onCreate() in the Application class
Init firebase FirebaseApp.initializeApp(this) inside function onCreate()
Start app
Application crashes on startup

Relevant Code:

Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process <my app id>:Metrica. Make sure to call FirebaseApp.initializeApp(Context) first.
        at com.google.firebase.FirebaseApp.getInstance(FirebaseApp.java:179)
        at com.google.firebase.perf.config.RemoteConfigManager.getInitialStartupMillis(RemoteConfigManager.java:91)
        at com.google.firebase.perf.config.RemoteConfigManager.<init>(RemoteConfigManager.java:85)
        at com.google.firebase.perf.config.RemoteConfigManager.<clinit>(RemoteConfigManager.java:52)
        at com.google.firebase.perf.config.RemoteConfigManager.getInstance(RemoteConfigManager.java:119) 
        at com.google.firebase.perf.config.ConfigResolver.<init>(ConfigResolver.java:78) 
        at com.google.firebase.perf.config.ConfigResolver.getInstance(ConfigResolver.java:86) 
        at com.google.firebase.perf.application.AppStateMonitor.<init>(AppStateMonitor.java:98) 
        at com.google.firebase.perf.application.AppStateMonitor.getInstance(AppStateMonitor.java:87) 
        at com.google.firebase.perf.metrics.Trace.<init>(Trace.java:106) 
        at com.google.firebase.perf.metrics.Trace.create(Trace.java:98) 
        at com.google.firebase.perf.FirebasePerformance.startTrace(FirebasePerformance.java:213) 
        at <my app id>.App.onCreate(Unknown Source:6) 
        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1118) 
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5791) 
        at android.app.ActivityThread.-wrap1(Unknown Source:0) 
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661) 
        at android.os.Handler.dispatchMessage(Handler.java:105) 
        at android.os.Looper.loop(Looper.java:164) 
        at android.app.ActivityThread.main(ActivityThread.java:6541) 
        at java.lang.reflect.Method.invoke(Native Method) 
        at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240) 
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)

Answer 1 · 2023-02-17T07:06:48.000Z

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Answer 2 · 2023-02-17T15:59:55.000Z

Hi @hram, thanks for reaching out to us. I'm not experiencing the same behavior with the steps you've provided. I added @AddTrace to my application class, but there seems to be no issue.

Relevant code:

class MainApplication: Application() {
    @AddTrace(name = "onCreateTrace", enabled = true /* optional */)
    override fun onCreate() {
        FirebaseApp.initializeApp(this)
        super.onCreate()
    }
}

Dependencies:

  implementation platform('com.google.firebase:firebase-bom:31.2.2')
  implementation 'com.google.firebase:firebase-analytics-ktx'
  implementation 'com.google.firebase:firebase-perf-ktx'

Manifest:

    <application
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        ...
        android:name=".MainApplication"
        tools:targetApi="31">

Am I missing anything?

Answer 3 · 2023-02-24T02:02:52.000Z

Hey @hram. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

Answer 4 · 2023-03-01T16:07:37.000Z

@argzdev I believe the app has to startup a separate process where onCreate is called again. It seems Firebase now fails to initialize on non main processes.

<service
  android:name="com.company.NewProcess"
  android:process=":NewProcess" />

Starting this service would result in a crash.

Answer 5 · 2023-03-01T18:15:58.000Z

Hi @tevjef, thanks for the insight. I'm not sure if I'm doing something wrong, but I still can't replicate the same behavior even with the service.

AndroidManifest:

<application
...
        <service
            android:name=".RandomService"
            android:process=":NewProcess" />
</application>

Random Service code:

class RandomService: Service() {
override fun onBind(p0: Intent?): IBinder? = null

    @AddTrace(name = "onCreateServiceTrace", enabled = true)
    override fun onCreate() {
        super.onCreate()
        Log.d(TAG, "onCreate: ")
        FirebaseApp.initializeApp(this)
    }

    @RequiresApi(Build.VERSION_CODES.O)
    override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
        super.onStartCommand(intent, flags, startId)
        Log.d(TAG, "onStartCommand: ")
        return START_STICKY
    }

    override fun onDestroy() {
        super.onDestroy()
        stopForeground(STOP_FOREGROUND_REMOVE)
        stopSelf()
        Log.d(TAG, "Random Service is being killed")
    }
}

MainActivity:

    fun startRandomService(view: View) {
        Intent(this, RandomService::class.java).also { intent ->
            startService(intent)
        }
    }

    fun endRandomService(view: View) {
        Intent(this, RandomService::class.java).also { intent ->
            stopService(intent)
        }
    }

Answer 6 · 2023-03-01T19:16:11.000Z

@argzdev why do you call FirebaseApp.initializeApp(this) before super.onCreate()?
what happens if you put FirebaseApp.initializeApp(this) after super.onCreate()?

Answer 7 · 2023-03-01T19:32:54.000Z

Hi @hram, I tried it with both scenario (before or after onCreate()), but still unable to reproduce this behavior. I'm not sure what I'm missing here. That said, any chance you could share us a minimal reproducible example so I can investigate this further? Thanks!

Answer 8 · 2023-03-08T02:02:34.000Z

Hey @hram. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

Answer 9 · 2023-03-08T17:47:36.000Z

@argzdev https://github.com/tevjef/android-bugs/tree/firebase-android-sdk-issues-4693

When launching the app:

Observe firebase is initialized properly.
Click the Next button to start a service in a new process
Observe failure in Logcat this error

                                                     java.lang.ExceptionInInitializerError
                                                                                                    	at com.google.firebase.perf.config.RemoteConfigManager.getInstance(RemoteConfigManager.java:119)
                                                                                                    	at com.google.firebase.perf.config.ConfigResolver.<init>(ConfigResolver.java:78)
                                                                                                    	at com.google.firebase.perf.config.ConfigResolver.getInstance(ConfigResolver.java:86)
                                                                                                    	at com.google.firebase.perf.application.AppStateMonitor.<init>(AppStateMonitor.java:98)
                                                                                                    	at com.google.firebase.perf.application.AppStateMonitor.getInstance(AppStateMonitor.java:87)
                                                                                                    	at com.google.firebase.perf.metrics.Trace.<init>(Trace.java:106)
                                                                                                    	at com.google.firebase.perf.metrics.Trace.create(Trace.java:98)
                                                                                                    	at com.google.firebase.perf.FirebasePerformance.startTrace(FirebasePerformance.java:213)
                                                                                                    	at com.example.myapplication.App.onCreate(Unknown Source:2)
                                                                                                    	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1266)
                                                                                                    	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6785)
                                                                                                    	at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
                                                                                                    	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2134)
                                                                                                    	at android.os.Handler.dispatchMessage(Handler.java:106)
                                                                                                    	at android.os.Looper.loopOnce(Looper.java:201)
                                                                                                    	at android.os.Looper.loop(Looper.java:288)
                                                                                                    	at android.app.ActivityThread.main(ActivityThread.java:7898)
                                                                                                    	at java.lang.reflect.Method.invoke(Native Method)
                                                                                                    	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
                                                                                                    	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)
                                                                                                    Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.example.myapplication:NewProcess. Make sure to call FirebaseApp.initializeApp(Context) first.
                                                                                                    	at com.google.firebase.FirebaseApp.getInstance(FirebaseApp.java:179)
                                                                                                    	at com.google.firebase.perf.config.RemoteConfigManager.getInitialStartupMillis(RemoteConfigManager.java:91)
                                                                                                    	at com.google.firebase.perf.config.RemoteConfigManager.<init>(RemoteConfigManager.java:85)
                                                                                                    	at com.google.firebase.perf.config.RemoteConfigManager.<clinit>(RemoteConfigManager.java:52)
                                                                                                    	at com.google.firebase.perf.config.RemoteConfigManager.getInstance(RemoteConfigManager.java:119) 
                                                                                                    	at com.google.firebase.perf.config.ConfigResolver.<init>(ConfigResolver.java:78) 
                                                                                                    	at com.google.firebase.perf.config.ConfigResolver.getInstance(ConfigResolver.java:86) 
                                                                                                    	at com.google.firebase.perf.application.AppStateMonitor.<init>(AppStateMonitor.java:98) 
                                                                                                    	at com.google.firebase.perf.application.AppStateMonitor.getInstance(AppStateMonitor.java:87) 
                                                                                                    	at com.google.firebase.perf.metrics.Trace.<init>(Trace.java:106) 
                                                                                                    	at com.google.firebase.perf.metrics.Trace.create(Trace.java:98) 
                                                                                                    	at com.google.firebase.perf.FirebasePerformance.startTrace(FirebasePerformance.java:213) 
                                                                                                    	at com.example.myapplication.App.onCreate(Unknown Source:2) 
                                                                                                    	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1266) 
                                                                                                    	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6785) 
                                                                                                    	at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) 
                                                                                                    	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2134) 
                                                                                                    	at android.os.Handler.dispatchMessage(Handler.java:106) 
                                                                                                    	at android.os.Looper.loopOnce(Looper.java:201) 
                                                                                                    	at android.os.Looper.loop(Looper.java:288) 
                                                                                                    	at android.app.ActivityThread.main(ActivityThread.java:7898) 
                                                                                                    	at java.lang.reflect.Method.invoke(Native Method) 
                                                                                                    	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) 
                                                                                                    	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Answer 10 · 2023-03-08T19:06:51.000Z

Thanks @tevjef, I was able to reproduce the same behavior now. I'll notify our engineers.

Answer 11 · 2023-03-29T09:05:50.000Z

Hi @argzdev Any update on this ? ...
I'm trying to create foregroundService with new process and my service has some firebase usage .I'm getting error Default FirebaseApp is not initialized in this process com.example.dev:locationProcess.

Answer 12 · 2023-04-17T10:07:45.000Z

Hi all, sorry for the radio silence. Our engineers are currently working on other issues at the moment. However, rest assured that this will be worked on as soon as possible. That said, I'd like to ask for help to kindly give an emoji thumbs up on the original author's post for tracking. This'll help us prioritize issues based on severity and demand. Thanks!

Answer 13 · 2023-04-19T07:45:51.000Z

We also facing this issue when start a service in new process. The crash still happing in firebase BoM version com.google.firebase:firebase-bom:31.3.0. After investigating, the crash only happened if we used Firebase Perf in our app. We need to upgrade firebase-BoM because of this warning:

Answer 14 · 2023-05-08T02:10:46.000Z

How it's goin?

Answer 15 · 2023-05-08T10:17:59.000Z

Let me notify our engineers again and see if we can get some updates.

Answer 16 · 2023-05-08T13:38:14.000Z

iam also getting the same error

//app gradle
implementation 'com.google.android.gms:play-services-maps:18.1.0'
implementation 'com.google.firebase:firebase-crashlytics:18.3.7'
implementation 'com.google.firebase:firebase-analytics:21.2.2'

//project level
classpath 'com.google.gms:google-services:4.3.15'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.9.5'

//Application class
override fun onCreate() {
super.onCreate()
FirebaseApp.initializeApp(this)
FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true)

iam able to open the app in debug mode but iam not able to open the release build ,when iam trying to open the release build iam getting the issue as mentioned below.

Caused by: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process <com.appID>. Make sure to call FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(FirebaseApp.java:179)

Answer 17 · 2023-05-08T18:33:05.000Z

Hi @vineeshLee, looking at your imports I don't see firebase-perf, so I'm not sure if you're experiencing the same issue here. Can you provide a full stacktrace so we can conduct an initial investigation?

Answer 18 · 2023-06-02T05:38:34.000Z

Sorry to be a pain but are there any updates about this issue?

The only way I have found so far to circumvent it if you're using an SDK that has a remote process is by manually initialising Firebase and making sure it gets initialised before the SDK in question...

Answer 19 · 2023-06-12T10:20:52.000Z

Sorry for the radio silence here, @ThrowJojo. Our engineers are still working on this. We'll reply back here once we have further updates. Thanks!

Answer 20 · 2023-06-29T10:06:40.000Z

h @argzdev , are there any updates.

Answer 21 · 2023-07-13T08:58:12.000Z

Let me share some new information on this issue:

The issue first appeared in firebase-bom:31.2.0 and not 31.2.2.
The issue still exists in the latest version firebase-bom:32.1.1
The issue seems related to runtime configuration, in case of upgrading the application (with changes from firebase-bom:31.1.1 and below) the issues doesn't happens! Only on fresh installs that have changes from firebase-bom:31.2.0 and above.
Based on the error message and the version the culprit is likely standard Firebase executors:

Answer 22 · 2023-07-26T00:37:47.000Z

Thanks a lot for highlighting the issue. Similar to the reference mentioned above, this issue seem to be raising out of Firebase Performance/Remote Config using the Firebase executors instead of its own executors. We are working to reproduce/fix this issue at the earliest. Will keep this issue posted as and when we have updates.

Thanks for your patience as we work through this issue.

Answer 23 · 2023-08-03T04:34:00.000Z

I have the same problem

Answer 24 · 2023-08-07T02:46:09.000Z

any update？

Answer 25 · 2023-08-07T04:04:26.000Z

putting 'com.google.gms.google-services' on plugins in app/build.gradle solved my problem

plugins {
    id 'com.google.gms.google-services'
}

Answer 26 · 2023-08-07T13:57:10.000Z

this is open from February, when can we expect it's resolution

Answer 27 · 2023-08-10T02:26:43.000Z

I have the same problem

Answer 28 · 2023-08-11T12:29:58.000Z

So I was facing this problem and I'm working with React Native and in this case was integrating push notification for android with Braze and FCM. I did the following:

Open Android Studio.
Added apply plugin: 'com.google.gms.google-services' to app/build.gradle.
Also added classpath 'com.google.gms:google-services:4.3.4' to build.gradle and clicked Sync Now and that fixed my issue.

Also in my case didn't have to add this FirebaseApp.initializeApp(this)... it worked with the above steps.

Answer 29 · 2023-08-15T21:08:58.000Z

After detailed analysis, here are our learnings on the issue:

Possibility 1:
Firebase App can be initialized in multiple ways - Either through dependency on Google Services (using the plugin) or using configuration options. When using configuration options based initialization, typically this is done in the Application onCreate API. When using @AddTrace annotation for the Application's onCreate API, that would force referring to FirebaseApp's instance at the start of the onCreate function. Unfortunately that is going to cause an exception since FirebaseApp is not initialized in the beginning of the onCreate method. There is no cleaner way to fix this issue.

The recommendation in this case would be to refactor the implementation on the application's onCreate API into its own separate function and add @AddTrace annotation to that instead of the application's onCreate function. This should avoid the problem.

Possibility 2:
Like the last comment above, you can depend on the GoogleServices which will initialize FirebaseApp before the Application's onCreate that can avoid the exception. That is exactly the reason why we did not have to do a separate FirebaseApp.initializeApp() in this approach.

But the caveat in this approach would be to avoid analytics dependency since that is not currently supported.

Note:
We don't this is exactly because of the changes brought because of the Firebase Executor that has caused this issue. But changing to FirebaseExecutor has brought this needs to visibility (since FirebaseExecutor based approach avoids FirebaseApp initialization to later until necessary).

Please update the comment thread if the above approaches does not solve your problem.

Answer 30 · 2023-08-16T05:52:02.000Z

please note that this is occuring too when app has to startup a separate process , related to Firebase initialization on non main processes.

Answer 31 · 2023-08-17T19:09:25.000Z

Same problem in .NET MAUI 😢

For MAUI I can confirm that adding Xamarin.GooglePlayServices.Analytics to your project (binding library for the above mentioned google services analytics package) work.

Answer 32 · 2023-08-24T01:02:36.000Z

Hey @hram. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

Answer 33 · 2023-08-24T05:13:33.000Z

do not close it automatically

Answer 34 · 2023-09-11T15:19:40.000Z

Hi, any progress on this issue?

Answer 35 · 2023-09-19T02:30:45.000Z

Thật đáng tiếc vì đến bây giờ sự cố vẫn chưa đc khắc phúc

Answer 36 · 2023-09-19T23:08:36.000Z

@hram Did the above suggestion work for you? Suggestions in this comment .

Answer 37 · 2023-10-17T01:28:15.000Z

I have the same issue with my application that have foreground service as a separated process.

Without FirebaseApp.initializeApp() there are no initialization at all, adding this in onStartCommand() does the job, but only for service.

Adding FirebaseApp.initializeApp() into the application's onCreate make app crash when open for some users. Seems like for some reason firebase cannot be used in more than one process for some reason.

Answer 38 · 2023-10-17T06:52:10.000Z

classpath 'com.google.gms:google-services:4.3.8' is OK but classpath 'com.google.gms:google-services:4.4.0' crash

Answer 39 · 2023-11-11T00:22:08.000Z

In my case helped downgrade google-services from 4.4.0 to 4.3.15

gradle wrapper: 7.5.1
android gradle plugin: 7.3.1
crashlytics gradle plugin: 2.9.9
google-services: 4.3.15 (~~4.4.0~~)
firebase bom: 32.5.0

Answer 40 · 2023-11-11T18:09:43.000Z

I faced same issue today.i tried everthing and at the end of the day it fixed🥴 .
i'm adding build.gradle(project/module) here

Build.gradle(Project)

buildscript {
    dependencies {
        classpath 'com.google.gms:google-services:4.3.15'
    }
}// Top-level build file where you can add configuration options common to all sub-projects/modules.
plugins {
    id 'com.android.application' version '7.3.0' apply false
    id 'com.android.library' version '7.3.0' apply false

}

Build.gradle(Module)

plugins {
    id 'com.android.application'
}

android {
    namespace 'tech.bugscreator.smartpay'
    compileSdk 34

    defaultConfig {
        applicationId "tech.bugscreator.smartpay"
        minSdk 24
        targetSdk 32
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}

dependencies {

    implementation 'androidx.appcompat:appcompat:1.6.1'
    implementation 'com.google.android.material:material:1.9.0'
    implementation 'androidx.constraintlayout:constraintlayout:2.1.3'
    implementation 'com.google.android.material:material:1.10.0'
    implementation(platform("com.google.firebase:firebase-bom:32.5.0"))
    implementation("com.google.firebase:firebase-analytics")

    implementation("com.google.firebase:firebase-firestore")
    testImplementation 'junit:junit:4.13.2'
    androidTestImplementation 'androidx.test.ext:junit:1.1.5'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'

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

i added google service dependency using classpath and in module level i apply plugin and it resolved my issue

Answer 41 · 2023-11-18T14:38:41.000Z

was facing issue with 'com.google.gms:google-services:4.4.0' but it solved when i changed it to 4.3.0 , Thanks to @engineerStuardo

Answer 42 · 2023-11-21T13:46:10.000Z

Any work around for this issue? While we wait for the next update that hopefully fixes it

Answer 43 · 2023-11-30T19:10:00.000Z

I even tried to downgrade to 4.3.15 and it still happening :-(

Answer 44 · 2023-12-06T16:39:38.000Z

Downgrade to 4.3.15 helps to me

Answer 45 · 2024-01-08T12:43:49.000Z

@engineerStuardo Thank you. Its really helped. version : 4.3.4

Answer 46 · 2024-01-16T16:55:19.000Z

classpath 'com.google.gms:google-services:4.3.8' is OK but classpath 'com.google.gms:google-services:4.4.0' crash

thanks!!!!!!!!!!

Answer 47 · 2024-02-18T19:56:44.000Z

classpath 'com.google.gms:google-services:4.3.8' is OK but classpath 'com.google.gms:google-services:4.4.1' crash

Answer 48 · 2024-02-18T19:58:29.000Z

classpath 'com.google.gms:google-services:4.3.8' is OK but classpath 'com.google.gms:google-services:4.4.0' crash

thank you bro!

Answer 49 · 2024-02-26T11:34:35.000Z

Hi @visumickey and @argzdev do we have any update on the fix.
I am still experiencing this issue and I tried the recommended fixes above and nothing works for me(unless downgrading dependencies, which is not what we want to do at the moment).

Answer 50 · 2024-03-04T13:30:28.000Z

The original problem was related to the :Metrica process (it is an analytics service of Yandex, the largest advertising provider in the CIS). In new versions of the library, the process has been renamed to :AppMetrica
The problem can be solved as follows:

class App : Application() {
    var mainProcess = false
    var metricaProcess = false
  
    override fun onCreate() {
        val processName = ProcessUtil.getProcessName(this)
        mainProcess = processName==packageName
        metricaProcess = processName.contains(":AppMetrica") || processName.contains(":Metrica")

        if (!metricaProcess) { // you do not need to initialise anything manually inside the Metrica process
            if (!mainProcess) {
                // if you created the service yourself in a separate process (via android:process=":Something"), you should manually initialise Firebase in that process.
                FirebaseApp.initializeApp(this)
            }
            
             // put old onCreate code here, e.g:
             // FirebaseCrashlytics.getInstance().setUserId("someId")
             // if (mainProcess) MobileAds.initialize(this) { } // you probably don't want ads in the background process
             // ...
             
        }
        super.onCreate()
    }
}

ProcessUtil.java:
https://gist.github.com/vellrya/6ab5d915f1002a8e1ae3205ba715f0d7

This method works with the newest versions of libraries, there is no need to downgrade dependency versions.

Answer 51 · 2024-03-15T13:47:50.000Z

Yes, i just updated com.google.gms:google-services from 4.3.15 to 4.4.1 and it's started crashing for me for above issue. Added initialization in Activity as well as in APplication file, still crashes for me.
Line where it's breaking for above error, even i tried to initialize FirebaseApp before i am using that, still not fixed
FirebaseAuth.getInstance().currentUser

Answer 52 · 2024-03-21T12:58:13.000Z

I have tested the following versions of com.google.gms:google-services:
4.3.15: working ✅
4.4.0: not working ❌
4.4.1: not working ❌

Firebase (Flutter) versions:

firebase_core: ^2.27.1
firebase_auth: ^4.17.9
firebase_messaging: ^14.7.20

Answer 53 · 2024-04-26T03:44:23.000Z

Hi, any progress on this issue? com.google.gms:google-services 4.4.1: not working

Answer 54 · 2024-04-29T18:14:14.000Z

I had this same issue due to an Activity being designated to a separate process. Downgrading versions did not work for me. However, manually initializing Firebase as outlined in #4599 resolved the issue.

Disable the FirebaseInitProvider in the AndroidManifest
Manually initialize Firebase in your Application via FirebaseApp.initializeApp(this, builder.build())

Unfortunately manually initializing Firebase apparently breaks _app_start tracing with BOM version 32.2.0 or later.

Answer 55 · 2024-07-03T10:11:20.000Z

集成了下面的sdk 功能， firebase-crashlytics 统计到线上用户报错 Caused by java.lang.IllegalStateException
Default FirebaseApp is not initialized in this process com.moonjoy.cointalh. Make sure to call FirebaseApp.initializeApp(Context) first.
本地无法复现。请问是什么问题导致的？

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

implementation 'com.google.firebase:firebase-crashlytics:18.6.4'
implementation 'com.google.firebase:firebase-analytics:21.6.2'
// Firebase Performance Monitoring 对勾
implementation ('com.google.firebase:firebase-perf:20.5.2'){
exclude group: 'com.squareup.okhttp3'
}
// Firebase messaging
implementation 'com.google.firebase:firebase-messaging:23.4.1'
// Firebase config
implementation 'com.google.firebase:firebase-config:21.6.3'

Answer 56 · 2024-07-11T09:34:06.000Z

Same here, upgrading to "com.google.gms:google-services:4.4.2" breaks my app. I will stay with "com.google.gms:google-services:4.3.10" until it gets resolved

Answer 57 · 2024-07-15T15:39:02.000Z

Hi all, sorry for the radio silence. Our engineers are currently working on other issues at the moment. However, rest assured that this will be worked on as soon as possible. That said, I'd like to ask for help to kindly give an emoji thumbs up on the original author's post for tracking. This'll help us prioritize issues based on severity and demand. Thanks!

Any update on this @argzdev ? 😅😅

Answer 58 · 2024-08-05T15:35:49.000Z

Same here, upgrading to "com.google.gms:google-services:4.4.2" breaks my app. I will stay with "com.google.gms:google-services:4.3.10" until it gets resolved

Same for me

it seems that it could be due to some refactoring: google/play-services-plugins#269
News: https://github.com/google/play-services-plugins/tree/main/google-services-plugin#new-in-version-440

Place the google-services.json file for your project in the app/ directory.
Alternatively, you can use variant specific source-sets, for example: debug/google-services.json.

This did trigger the error Default FirebaseApp is not initialized in this process
Related issues:

Answer 59 · 2024-08-22T01:17:13.000Z

4.3.15는 괜찮은것 같습니다.

Answer 60 · 2024-09-10T11:17:48.000Z

Any progress on this issue? Even I am facing it after upgrading Firebase BoM to 33.2.0

Answer 61 · 2024-09-15T11:56:12.000Z

Here's what the Javadoc from the FIrebaseApp.java class says :-

"Any FirebaseApp initialization must occur only in the main process of the app. Use of Firebase in processes other than the main process is not supported and will likely cause problems related to resource contention."

So, going by the maintainers' recommendation, we're not supposed to initialize Firebase in non-main processes. I did initalize Firebase in a non-main process in the Application onCreate() and it did stop the crash, but I'm not sticking to this solution because it may have side effects that may only be realized in production.

Answer 62 · 2024-09-15T16:02:37.000Z

If an exception is going to be thrown then we should be allowed to catch it. At the very least this should be failing gracefully. Analytics should not be crashing apps in production.

Answer 63 · 2024-09-16T12:15:31.000Z

Hi @visumickey and @argzdev do we have any update on the fix.

Answer 64 · 2024-10-04T13:40:49.000Z

Knock-knock-knock, is there any update?

Answer 65 · 2024-10-10T20:10:16.000Z

@ernazarsembayev we landed a fix for this, it will go out in the next-next release due to timing.

Answer 66 · 2024-11-08T16:17:48.000Z

This fix was released in Perf version 21.0.2