-
Notifications
You must be signed in to change notification settings - Fork 368
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
[3.10.2] Issue with FirebaseApp not initialized #681
Comments
@xcaEi Thanks for the report, this seems to be the same as issue #552, it should have been fixed in the 3.9.3 release however. It is possible there could be some edge case here. Since it is just one device it could be some issue with it. I'll leave this issue open for a bit incase others are seeing this issue, or if you see more occurrences or can reproduce this issue. |
@xcaEi We haven't seen any other reports of this issue so it seems the issue is just isolated to the single device. Let us know if you are seeing it with other device models and we can reopen this issue and check it out again. Thanks. |
I have launched the app with onesignal3.10.2 but this issue is occurring repeatedly for the users who are using Samsung galaxy |
Hello, I have the same issue, but now with the last SDK (3.12.6), more different device models have this issue: Fatal Exception: java.lang.Error: FATAL EXCEPTION [firebase-iid-executor] Caused by java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.company.name. Make sure to call FirebaseApp.initializeApp(Context) first. UnityMain And here's list of devices: |
Hi @jkasten2 are you going to reopen the issue? |
@shefich I created a new issue to make sure it gets attention. This is causing us serious business impact in production so I hope they / we figure it out soon. |
Hello, i am also facing the same issue on Pixel with OS 10. Heres the log
|
Howdy everyone, |
Howdy! |
IssueThanks for all the stacktraces. It seems all the recent crashes have this specific I wasn't able to find any notes in Google's documentation about a bug like this but I would recommend updating to a newer version of firebase as Google may have fixed this. Possible FixesOption 1 (Recommend, if you meet the noted requirements)If you have OneSignal 3.13.0+, Jetifier, and AndroidX in your project I recommend updating to the latest implementation 'com.google.firebase:firebase-messaging:20.1.7' Option 2If you are using OneSignal 3.12.2+ version then you safely upgrade to implementation 'com.google.firebase:firebase-common:17.1.0' |
Closing due to inactivity |
Description:
I launched a new app recently and haven't had a problem until last night for one specific user who encountered the issue about 10 times yesterday and today.
As I don't use Firebase in my application, I think this might be the Firebase App created by OneSignal. However as it has only happened to one specific user, I think the issue might be with linked to his device.
Environment
One Signal SDK : 3.10.2
Play Services : 11.0.4
Android Support lib : 27.1.1
User Device : Teclast P10 (p10_m3f5_g in Google Play Console) on Android 7.1.2
Steps to Reproduce Issue:
I am guessing just launching the application but I have no information.
Anything else:
java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.jsl_prod.presse. Make sure to call FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(Unknown Source)
at com.google.firebase.iid.FirebaseInstanceId.getInstance(Unknown Source)
at com.google.firebase.iid.FirebaseInstanceIdService.zza(Unknown Source)
at com.google.firebase.iid.FirebaseInstanceIdService.handleIntent(Unknown Source)
at com.google.firebase.iid.zzc.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
The text was updated successfully, but these errors were encountered: