quickstart-unity
quickstart-unity copied to clipboard
firebase
libc.so Crash after updating to firebase unity sdk 8.6.1/8.6.2
[REQUIRED] Please fill in the following fields:
- Unity editor version: 2019.4.30f1
- Firebase Unity SDK version: 8.6.2
- Source you installed the SDK: .unitypackage
- Problematic Firebase Component:
- Other Firebase Components in use: (Auth, Database, functions, Fcm, .)
- Additional SDKs you are using: (Facebook, AdMob, etc.)
- Platform you are using the Unity editor on: Mac
- Platform you are targeting: Android
- Scripting Runtime: IL2CPP
We are getting this crash after after to firebase Unity sdk 8.6.1.
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Unable to repro What's the issue repro rate? 1 % user impacted
LOGS:
Crashed: Thread: SIGQUIT 0x0000000000000000
#00 pc 0x1682c libc.so
#01 pc 0x42673 libc.so
#02 pc 0x42673 libc.so
#03 pc 0x1de23 libc.so
#04 pc 0x42827 libc.so
#05 pc 0x2637f3 libart.so
#06 pc 0x43d8fa libart.so
#07 pc 0x32fe11 libart.so
#08 pc 0x2a0b6d libart.so
#09 pc 0x44038e libart.so
#10 pc 0x65e5e libc.so
#11 pc 0x43eeae libart.so
#12 pc 0x440916 libart.so
#13 pc 0x3d3db5 libart.so
#14 pc 0xd828f libart.so
Thread
#00 pc 0x43f84 libc.so
#01 pc 0x138e4a libFirebaseCppApp-8_6_2.so
I found a few problems with this issue:
- I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
- This issue does not seem to follow the issue template. Make sure you provide all the required information.
Hi @AjayC-Bsw,
In order to identify what's causing this, could you provide a minimal, reproducible example of your project along with the complete steps to replicate the issue? Could you also provide a complete stack trace along with the Firebase product/s used?
We are having the same issue. We cant reproduce the bug ourselves, and the crashlytics doesn't give us much info also. The only thing we noticed is that the free memory of the crashed users is below 100MB for some 20MB. Happens on booth 8.6.1/8.6.2. The crashes happen mostly when the app is put in the background or coming back from one. The thing that comes to mind is a memory leek but we are not sure. Until this is fixed we will go back to the previous version we where using 8.2.0 since we don't get this crashes on that version. I hope this additional info whose helpful
@paulinon Firebase products used - Database, RemoteConfig, Fcm, installation, Crashlytics, Functions, Analytics
Steps to Reproduce -
- Enable Don't keep activity on From Device Setting.
- Login to Facebook with Chrome ( Uninstall Facebook App from Device )
- After facebook Login App Will Restart.
or Same thing Happens with When Rewards Ads comes in Landscape mode.
We are using other crash reporting tools too that is not reporting any crash neither we are getting anything in logcat but Crashlytics shows app crashed.
HI @AjayC-Bsw,
It would be great if you provide a minimal, reproducible example of your project along with the complete steps to replicate your issue. I'm unable to begin my investigation with the provided infromation so far.
@paulinon I have the same issue.Crashing on Android and also havn't see any useful info in the logcat. unity version 2020.3.20f1 Target Platform: Android Scripting Runtime: IL2CPP FirebaseAnalytics 8.6.2 FirebaseMessaging 8.6.2 FirebaseCrashlytics 8.6.2 I found that while ExternalDependencyManager was resolving, it says that some conflicting dependencies were found. But I don`t konw what dependencies are conflicted. Here is the warning: WARNING: Some conflicting dependencies were found. The following dependency versions were modified: com.android.support:appcompat-v7:25.3.1 --> androidx.appcompat:appcompat:1.1.0 com.android.support:cardview-v7:25.3.1 --> androidx.cardview:cardview:1.0.0 com.android.support:customtabs:25.3.1 --> androidx.browser:browser:1.0.0 com.android.support:support-v4:25.3.1 --> androidx.legacy:legacy-support-v4:1.0.0 com.facebook.android:audience-network-sdk:6.2.1 --> com.facebook.android:audience-network-sdk:+ com.google.ads.mediation:facebook:6.2.0.1 --> com.google.ads.mediation:facebook:6+ com.google.ads.mediation:unity:3.6.2.0 --> com.google.ads.mediation:unity:3+ com.google.android.gms:play-services-ads:20.2.0 --> com.google.android.gms:play-services-ads:+ com.google.android.gms:play-services-base:17.5.0 --> com.google.android.gms:play-services-base:+ com.google.android.gms:play-services-base:17.6.0 --> com.google.android.gms:play-services-base:+ com.google.firebase:firebase-analytics:19.0.0 --> com.google.firebase:firebase-analytics:+ com.google.firebase:firebase-common:20.0.0 --> com.google.firebase:firebase-common:+ com.google.firebase:firebase-crashlytics-ndk:18.2.4 --> com.google.firebase:firebase-crashlytics-ndk:+ com.google.firebase:firebase-iid:21.1.0 --> com.google.firebase:firebase-iid:+ com.google.firebase:firebase-messaging:22.0.0 --> com.google.firebase:firebase-messaging:+
Hey @AjayC-Bsw. 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!
We saw the same crash issue in our game after updating to 8.6.1/8.6.2 and needed to revert to the version we had previously integrated (8.1.0) in order to resolve.
Similar to others, we were not able to repro the crash on test devices but it was occurring for 1% of players when live which would put us above the bad behavior threshold.
Unity version 2019.4.30
Any news ? It was occurring for about 26% of all crashs in my app . All I know is this issue happens when low RAM free ( < 200mb , sometime 200-500mb ) . No problem with ver 8.1.0 , 8.2.0
Unity 2020.3.15
yes. I find it write log and crash
@yingnierxiao Please share your findings.
Guys,
- Same issue here when updating to Firebase 8.6.2 ( Firebase Core SDK 8.6.2, FirebaseAnalytics 8.6.2, FirebaseCrashlytics 8.6.2 )
- Unable to repro like the others but as you can see happens.
Hi @AjayC-Bsw and other folks in the thread,
Version 8.7.0 of the SDK has been released recently. Could you try this out and see if it resolves the issue?
Hey @AjayC-Bsw. 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!
Hey @AjayC-Bsw. 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!
Hi guys, the issue is still happening to us on 8.6.2 but we prefer rollback to 8.2.0 to be safe instead of releasing with 8.7.0 since the guys here mentions that is still happening on 8.7.0 but not on 8.2.0. Unfortunately there is no more information we can add to the ticket apart from all the mentioned above and the report from firebase crashlytics.
Summary:
- We cant reproduce the bug ourselves, and crashlytics doesn't give us much info also.
- Starts happening after updating to 8.6.1/8.6.2, according to the people here does not seem to happen in 8.1.0/8.2.0
- We do see an spike of crashes in crashlytics of libc.so
Hopefully this helps to get to the bottom of the issue!
As said before in the thread, we're also seeing the exactly same crash after upgrading Firebase to a version later than 8.4.0 — we tried with 8.5.0, 8.6.1, 8.6.2, and 8.7.0.
We can see the crash on our internal devices on Crashlytics dashboard, but the strange thing is that we don't see the crash in the device, what might point out to a silent crash. Another useful information: at least for us, the crash doesn't seem to be captured by Google Play — we only got the crash reported on Crashlytics.
So far, the only solution was to roll-back to version 8.4.0 in our case.
FYI: Unity 2019.4.21f1 with Firebase analytics, crashlytics, cloud messaging, and remote config.
Hey @AjayC-Bsw. 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!
Hi, guys! We can repro this when we update to 8.6.1 from 8.2.0, we have not tried 8.7.0 since people here mention it is not fixed. Thanks!
Hey @AjayC-Bsw. 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!
Hello, has anyone tried 8.8.0 version?
We are holding update for some time now because of this crash, so we are stuck on v8.2.0. But on other hand, there is an ANR fix in v8.6.0...
I've recently updated the SDK to version 8.8.0 and i'm getting this Crash too, i'm using unity 2020.3.22f1. I'll attach below any information that i have. Based on analytics data, the player is a little far in the game, played 10 minutes or more until the crash.
(Important) This shows to be in the Application Close, when the player close the game the crash is triggered, but i'm not receiving on google play crash report. Only in the crashlytics. The player does not have notion about it too, the crash is silent.
Crashed: Thread : SIGABRT 0x0000000000000000 #00 pc 0x6159e libc.so #01 pc 0x2dfec libc++.so #02 pc 0xbaa4e libc.so #03 pc 0x2dfec libc++.so #04 pc 0xb7bde libc.so #05 pc 0x3606d libc++.so #06 pc 0x475f1 libc++.so #07 pc 0x475e7 libc++.so #08 pc 0x14ec7 libaaudio.so #09 pc 0x429ef libaudioclient.so #10 pc 0x61cea libaudioclient.so #11 pc 0x44821 libaudioclient.so #12 pc 0xbc25e libc.so #13 pc 0xda1d libutils.so #14 pc 0x15e46a libandroid_runtime.so #15 pc 0xd97f libutils.so #16 pc 0x15e45e libandroid_runtime.so #17 pc 0x81f85 libandroid_runtime.so #18 pc 0x81f2b libandroid_runtime.so #19 pc 0xbaa4e libc.so #20 pc 0xaba7b libc.so #21 pc 0xaba65 libc.so #22 pc 0x62a43 libc.so #23 pc 0xaba65 libc.so #24 pc 0xd63b libutils.so
Hey @AjayC-Bsw. 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!
Hello guys!
- We can also confirm that rolling back to 8.2.0 fixes the crashes.
- Also tried with 8.8.0 and getting the crash too in Unity 2020.3.8f1 ( it is not reproducible, seems a silent crash and it shows up only in Firebase crashlytics )
Hope this help to fix it! ty!
Hey, we get this issue after upgrading Firebase from 7.2 to 8.8. Like others mentioned, seems to be a silent crash (it's not tracked by Google Play Console). We use Unity 2020.3.26. ~2% of users affected.
I'm having the same issue after update to Firebase 8.6.2. We can't reproduce and crashlytics don't give us much info.
Hey @AjayC-Bsw. 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!