Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Big Spike in Crashes after upgrading project in version 2019.4.20 from 2018.4.14

Discussion in 'Android' started by KevinErn, Mar 20, 2021.

  1. KevinErn

    KevinErn

    Joined:
    Mar 19, 2021
    Posts:
    2
    We are facing a big spike in Firebase Crashlytics and Android Vitals after updating our project in Unity 2019.4.20 Version for Android.
    And also we can not reproduce this issue in our test devices.
    The details and error logs are mentioned below:
    ***********
    Unity version : 2019.4.20f1
    Firebase : 6.16.1
    - Analytics
    - Cloud Messaging.
    - RemoteConfig
    - Crashlytics
    AdMob : v5.4.0 With Meditaions
    Proguard : Enabled
    Crashes ratio for Android OS Versions
    ------------------------
    45% Android 7
    22% Android 9
    11% Android 5
    11% Android 6
    11% Other (1)
    Devices
    ------------
    76% Samsung Devices
    11% Galaxy Tab A (2016)
    11% Galaxy Tab E 9.6
    11% Galaxy Tab A
    34% Other (3)
    Crash Log
    ---------------
    Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 2019.4.20f1
    Device model : samsung SM-T580
    Device fingerprint: samsung/gtaxlwifixx/gtaxlwifi:8.1.0/M1AJQ/T580XXS5CTK1:user/release-keys
    Caused by java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2019.4.20f1 (6dd1c08eedfa)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    Build fingerprint: 'samsung/gtaxlwifixx/gtaxlwifi:8.1.0/M1AJQ/T580XXS5CTK1:user/release-keys'
    Revision: '6'
    ABI: 'arm'
    Timestamp: 2021-03-19 07:50:38+0000
    pid: 6690, tid: 9089, name: Thread-267 >>> com.replaced.original.packagename <<<
    uid: 10141
    signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x320004f
    r0 03200037 r1 ca9f51f1 r2 00000001 r3 00002381
    r4 cbd9d500 r5 00000001 r6 9f1e5290 r7 9f1e5348
    r8 00000479 r9 9fede0a0 r10 c3b96300 r11 00000000
    ip c70fa178 sp 9f1e5290 lr caba93e3 pc cabcece0
    backtrace:
    #00 pc 00246ce0 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libunity.so (BuildId: 719cc44fd317601247922407d2e09339ab0ad224)
    #01 pc 002213df /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libunity.so (BuildId: 719cc44fd317601247922407d2e09339ab0ad224)
    #02 pc 00288f83 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libunity.so (BuildId: 719cc44fd317601247922407d2e09339ab0ad224)
    #03 pc 019a5884 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libil2cpp.so (BuildId: 1992d9f93c6b5b02b2216d9a9e050f29922f6b2b)
    #04 pc 00ed5364 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libil2cpp.so (BuildId: 1992d9f93c6b5b02b2216d9a9e050f29922f6b2b)
    #05 pc 008a85c4 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libil2cpp.so (BuildId: 1992d9f93c6b5b02b2216d9a9e050f29922f6b2b)
    #06 pc 0222a858 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM7wPw==/lib/arm/libil2cpp.so (BuildId: 1992d9f93c6b5b02b2216d9a9e050f29922f6b2b)
    #07 pc 01ee6478 /data/app/com.replaced.original.packagename--eH2N-IuYsndsdwIOM<truncated: 2806 chars>
    at libunity.0x246ce0()
    at libunity.0x2213df()
    at libunity.0x288f83()
    at libil2cpp.0x19a5884()
    at libil2cpp.0xed5364()
    at libil2cpp.0x8a85c4()
    at libil2cpp.0x222a858()
    at libil2cpp.0x1ee6478()
    at libil2cpp.0x1ee6478()
    at libil2cpp.0x5089a8()
    at libil2cpp.0x3fb068()
    at libil2cpp.0x3ffb0c()
    at libil2cpp.0x3ff870()
    at libil2cpp.0x3d4528()
    at libil2cpp.0x1a2f024()
    at libil2cpp.0x1a27d5c()
    at libil2cpp.0x1ff046c()
    at libil2cpp.0x1ff37a0()
    at libil2cpp.0x52faf8()
    at libil2cpp.0x3fb068()
    at libunity.0x21697d()
    at libunity.0x22005b()
    at libunity.0xec63f()
    at base.0x1bd655()
    ***********
    - We also tried solutions given in below Post to add "android.bundle.enableUncompressedNativeLibs=false" in Custom gradle template ,but nothing worked for us.
    Ref Link : https://forum.unity.com/threads/nat...ativerestartactivityindicator-v.546271/page-4

    - We have tried to backtrace this error log with the stack trace utility provided in the Android Logcat V1.2.1 Package, but every time it returns symbols missing.
    We have tried to attach symbols from bellow locations but nothing worked for us
    1. Unity\Hub\Editor\2019.4.20f1\Editor\Data\PlaybackEngines\AndroidPlayer\Variations\il2cpp\Common\StaticLibs
    2. Unity\Hub\Editor\2019.4.20f1\Editor\Data\PlaybackEngines\AndroidPlayer\Variations\il2cpp\Development\Symbols
    3. Unity\Hub\Editor\2019.4.20f1\Editor\Data\PlaybackEngines\AndroidPlayer\Variations\il2cpp\Release\Symbols
    4. Unity\Hub\Editor\2019.4.20f1\Editor\Data\PlaybackEngines\AndroidPlayer\NDK\platforms\<Android API>\arch-arm64\usr\lib
    5. Symbols Generated on AAB build path
    6. ProjectFolder\Temp\StagingArea\libs\
    Please Provide solution if you have any for the below questions
    1) Does unity provide any symbols on any other location which is useful in this type of scenarios?
    2) Is anyone facing same type of crashes in android with 2019.4.20 Version?

    Thanks in advance.
     
  2. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,663
    Since you're using il2cpp probably with Strip Engine Code On, the symbols for libil2cpp and libunity should be in zip package next to your app bundle, please use that to resolve stacktrace.
     
  3. KevinErn

    KevinErn

    Joined:
    Mar 19, 2021
    Posts:
    2
    Thanks @Tomas1856 for quick reply.
    We've already tried with symbols located in zip package next to our app bundle
    but it didn't worked
    Is there any other solution that we can try ?
     
  4. wheel_wang

    wheel_wang

    Joined:
    Feb 5, 2017
    Posts:
    6
    Same issue here! Android Game crash on start. No game version update. The latest version has been online for a week. Suddenly crashes report on firebase from yesterday. We are using 2019.4.21. Anyone know why?
     

    Attached Files:

  5. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,663
    What exactly didn't work? Resolving stacktrace is the first step in solving such problems, without this information, it's hard to move forward.
     
  6. damelin2

    damelin2

    Joined:
    Jan 8, 2013
    Posts:
    19
    If you see something like this in your crash's call stack: [anon:libwebview reservation]

    Your crashes are related to the bugged WebView update Google did yesterday. Players must update their Android System WebView on the Play Store. We had a ton of crash, out of nowhere since yesterday.

    I was hoping that we could do a client fix to prevent this, but not sure it's possible.

    https://www.engadget.com/android-gmail-stop-running-webview-234125352.html