search

firebase / quickstart-unity

Firebase Quickstart Samples for Unity
https://firebase.google.com/games
Apache License 2.0
836 stars 431 forks source link

libc.so Crash after updating to firebase unity sdk 8.6.1/8.6.2 #1193

Closed AjayC-Bsw closed 1 year ago

AjayC-Bsw commented 2 years ago

[REQUIRED] Please fill in the following fields:

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
google-oss-bot commented 2 years ago

I found a few problems with this issue:

paulinon commented 2 years ago

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?

TheEye2108 commented 2 years ago

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

AjayC-Bsw commented 2 years ago

@paulinon Firebase products used - Database, RemoteConfig, Fcm, installation, Crashlytics, Functions, Analytics

Steps to Reproduce -

  1. Enable Don't keep activity on From Device Setting.
  2. Login to Facebook with Chrome ( Uninstall Facebook App from Device )
  3. 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.

paulinon commented 2 years ago

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.

jykgod commented 2 years ago

@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:+

google-oss-bot commented 2 years ago

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!

MiketoString commented 2 years ago

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

tienhagioi commented 2 years ago

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 Capture

yingnierxiao commented 2 years ago

yes. I find it write log and crash

AjayC-Bsw commented 2 years ago

yes. I find it write log and crash

@yingnierxiao Please share your findings.

hgonzalezsgn commented 2 years ago

Guys,

Screen Shot 2021-12-17 at 09 09 23

paulinon commented 2 years ago

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?

google-oss-bot commented 2 years ago

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!

vachh commented 2 years ago

i update to version 8.7.0, It still has this problem

google-oss-bot commented 2 years ago

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!

hgonzalezsgn commented 2 years ago

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:

Hopefully this helps to get to the bottom of the issue!

nanddo commented 2 years ago

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.

image image

google-oss-bot commented 2 years ago

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!

jdelvalle commented 2 years ago

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!

1 2
mustafamadde22 commented 2 years ago

we are using version 8.7.0, the problem continues

google-oss-bot commented 2 years ago

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!

carmatija commented 2 years ago

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...

thiagolr commented 2 years ago

I also rolled back to 8.2.0 and things improved a lot!

matheustaveiros commented 2 years ago

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.

1 2

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

google-oss-bot commented 2 years ago

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!

hgonzalezsgn commented 2 years ago

Hello guys!

Hope this help to fix it! ty!

Arvtesh commented 2 years ago

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.

raphaelns-developer commented 2 years ago

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.

google-oss-bot commented 2 years ago

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!

jonsimantov commented 2 years ago

We're looking into this. Just to make sure we have an understanding of this issue, it sounds like it occurs when:

According to Crashlytics reports, it seems to be happening on application exit. Is that all accurate?

Has anyone found any information narrowing down any subset of Android OS versions, devices, etc.?

Thanks for everyone's help tracking this down.

manelizzard commented 2 years ago

Thank you @jonsimantov.

All that is accurate in our case but the application exit case. We cannot confirm that as we are not 100% sure on when the crash happens.

brzaknemanja commented 2 years ago

Hello, I can also confirm libc.so crash in firebase dashboard when I do Application.Quit() and re-enter the game. In my case re-entering the game after Application.Quit() returns the game to login state where Firebase app is initialized. I don't know if that is relevant to this issue. I've tried suggestions like Disposing Firebase before Application.Quit() but it didn't help. This starter happening after switch from Firebase 7.** to 8.8.0 latest release.

Packages in project: Firebase App (Core) 8.8.0 Firebase Crashlytics 8.8.0 Firebase Remote Config 8.8.0 Google Analytics 8.8.0 Facebook SDK 11.0.0 Fairbid SDK 3.24.0 Google Play Games 0.10.06

I can reproduce this crash every time I do Application.Quit() and re-enter the game. I see nothing on adb logcat that is relevenat (maybe I'm just not aware what should I see)

Is there any way to fix this? Does google play console recognize this crash? Becase it happens every time player exits game with back button firebase_1 .

chkuang-g commented 2 years ago

Hi folks,

Seems like the common theme here is

  1. On Android
  2. When other plugins, ex. Facebook, are in use
  3. After Firebase 8.6.1

This thread seem to mixed with different issues. We need your help to sort this out. Please answer the following questions

  1. Are all points above true to you?
  2. Are you able to reproduce it locally, or using this testapp? If so, please share additional logs (adb logcat) which provides may provide more insights about the crash location. Seems like those info on Crashlytics is not detailed enough.
  3. Are you using other plugins in your project? You can find out what other plugins are using EDM4U to resolve dependencies through Assets > External Dependency Manager > Android Resolver > Display Libraries. You can see what other Dependencies.xml are in your project.
  4. Are you using mainTemplate.gradle, a.k.a. Custom Gradle Template?
  5. Did you see any error or warning when force resolve? That is, Assets > External Dependency Manager > Android Resolver > Force Resolve. Did you see any conflict like what @jykgod mentioned in https://github.com/firebase/quickstart-unity/issues/1193#issuecomment-986430303?
  6. Does it crash every time? What's the timing. ex. at launch or at killed? Before crash, does Firebase API function properly to you?

Thank you! Shawn

jonsimantov commented 2 years ago
  • You are using the Firebase Unity SDK 8.5.0 or later

Can anyone confirm whether the issue definitely occurs in 8.5.0, and definitely does not occur in 8.4.0? We're working on tracking this down and very little changed between those two versions.

nronaldvdberg commented 2 years ago
  • You are using the Firebase Unity SDK 8.5.0 or later

Can anyone confirm whether the issue definitely occurs in 8.5.0, and definitely does not occur in 8.4.0? We're working on tracking this down and very little changed between those two versions.

Not sure where you got the 8.4.0 and 8.5.0 from - they were not mentioned in this thread, but perhaps you have more information than we have? From my reading of this thread the situation is:

So it could be 8.3, 8.4, or 8.5 that started the problem. Looking at the release notes, my bet would be on 8.4.

I'm having troubles since upgrading to 8.8 last week, so i will also roll back. To help narrow down the issue, i'll roll back to 8.3.

brzaknemanja commented 2 years ago

I can confirm that rolling back to 8.2 fixes this issue (was previously on 8.8)

jonsimantov commented 2 years ago

I can confirm that rolling back to 8.2 fixes this issue (was previously on 8.8)

Sorry for the request - would it be possible for you to try 8.4.0 and/or 8.5.0, to help us diagnose when the issue started to occur? Those versions were mentioned earlier in the thread.

nanddo commented 2 years ago

I can confirm that the crash doesn't reproduce in Firebase 8.4.0. We tested on all versions after 8.6 and they all present the issue.

I'll investigate if version 8.5.0 does reproduce or not and let you know -- we haven't tested this one yet.

FYI: We have Firebase App, Crashlytics, Cloud messaging, Remote Config on 8.4.0

YogeLike commented 2 years ago

we have the same error using 8.8.0 and do not know how to reproduce it locally.

nanddo commented 2 years ago

I confirmed that version 8.5.0 does not reproduce the issue. It seems to be exclusive from version 8.6.1 and above.

diegoarize-gamehouse commented 2 years ago

Does anyone know if the version 8.9.0 fixes the crash?

brzaknemanja commented 2 years ago

Hey all,

Has anyone tried releasing with version 8.9.0? Is this crash resolved in newest version?

Rano1 commented 2 years ago

we have the same error using 8.9.0.

RaphaelNSG commented 2 years ago

He,

Has anyone tried test with version 8.10.0?

PapayaRichter commented 2 years ago

Hey we are using the Firebase SDK 8.9.0 We experience the same problem, We don't get any complaints from clients but we see this in the Firebase Crashlytics We also running Sentry and we don't see anything about this bug (so it's firebase specific)

The image shows:

We were 7.2.0 before the upgrade

Screen Shot 2022-05-23 at 11 42 11

Hope it helps and please update when this is solved!

pankrzysztofb commented 2 years ago

We tested on Firebase SDK 9.0, still experienced this issue

raphaelns-developer commented 2 years ago

@paulinon Do you have any news about this issue? I had to downgrade the Firebase version of all my products because of it and now i have a lot of apps with one version of Firebase for Android and another from IOS.

ernesernesto commented 2 years ago

We recently upgrade to Firebase 8.10 and we got this issues too, now reverting back to old one (8.2 as people on this thread suggested)

murarivasudevan commented 2 years ago

We are experiencing the same issue ever since updating our games to 8.6.1 and above, and is our highest occurring crash by a long shot. Is there any progress towards fixing this issue?