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. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Bug Native crash of /Fatal AndroidRuntime Exception detected

Discussion in 'Android' started by fatogregnome, Jul 18, 2022.

  1. fatogregnome

    fatogregnome

    Joined:
    Jun 5, 2022
    Posts:
    13
    Hello
    When publishing to google play, I encountered the following problems.Other divice is ok,but the pixel 2 is crashed.




    Fatal AndroidRuntime Exception detected.
    FATAL EXCEPTION: UnityMain
    Process: com.TaoYuanCun.com.WalkHero, PID: 6663
    java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2021.2.14f1c1 (7c06c4af091b)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    Revision: '0'
    ABI: 'arm'
    Timestamp: 2022-07-17 20:17:35-0700
    pid: 6663, tid: 7628, name: UnityMain >>> com.TaoYuanCun.com.WalkHero <<<
    uid: 10093
    signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    r0 00000001 r1 e1e1a760 r2 00003435 r3 00000077
    r4 00000000 r5 00000001 r6 00000001 r7 c27751e0
    r8 00000002 r9 c277a13c r10 00000000 r11 c2774cac
    ip eba542d0 sp c5b2f3c8 lr c8e89a1c pc 00000000

    *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2021.2.14f1c1 (7c06c4af091b)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    Revision: '0'
    ABI: 'arm'
    Timestamp: 2022-07-17 20:17:35-0700
    pid: 6663, tid: 7628, name: UnityMain >>> com.TaoYuanCun.com.WalkHero <<<
    uid: 10093
    signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    r0 00000001 r1 e1e1a760 r2 00003435 r3 00000077
    r4 00000000 r5 00000001 r6 00000001 r7 c27751e0
    r8 00000002 r9 c277a13c r10 00000000 r11 c2774cac
    ip eba542d0 sp c5b2f3c8 lr c8e89a1c pc 00000000


    Handling an uncaught exception thrown on the thread UnityMain.
    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 2021.2.14f1c1
    Device model : unknown GCE x86 phone
    Device fingerprint: generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys
    Build Type : Release
    Scripting Backend : IL2CPP
    ABI : armeabi-v7a
    Strip Engine Code : true
    Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2021.2.14f1c1 (7c06c4af091b)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    Revision: '0'
    ABI: 'arm'
    Timestamp: 2022-07-17 20:17:35-0700
    pid: 6663, tid: 7628, name: UnityMain >>> com.TaoYuanCun.com.WalkHero <<<
    uid: 10093
    signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    r0 00000001 r1 e1e1a760 r2 00003435 r3 00000077
    r4 00000000 r5 00000001 r6 00000001 r7 c27751e0
    r8 00000002 r9 c277a13c r10 00000000 r11 c2774cac
    ip eba542d0 sp c5b2f3c8 lr c8e89a1c pc 00000000

    An unhandled exception was thrown by the app.
    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version : 2021.2.14f1c1
    Device model : unknown GCE x86 phone
    Device fingerprint: generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys
    Build Type : Release
    Scripting Backend : IL2CPP
    ABI : armeabi-v7a
    Strip Engine Code : true
    Caused by: java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    Version '2021.2.14f1c1 (7c06c4af091b)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    Revision: '0'
    ABI: 'arm'
    Timestamp: 2022-07-17 20:17:35-0700
    pid: 6663, tid: 7628, name: UnityMain >>> com.TaoYuanCun.com.WalkHero <<<
    uid: 10093
    signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    r0 00000001 r1 e1e1a760 r2 00003435 r3 00000077
    r4 00000000 r5 00000001 r6 00000001 r7 c27751e0
    r8 00000002 r9 c277a13c r10 00000000 r11 c2774cac
    ip eba542d0 sp c5b2f3c8 lr c8e89a1c pc 00000000
     
  2. jarotheking

    jarotheking

    Joined:
    Mar 20, 2019
    Posts:
    3
    Another one here .. same device, same error when uploading to google play store
     
  3. andy314159

    andy314159

    Joined:
    Jun 28, 2020
    Posts:
    1
    Same here. Same error same device. Other devices okay. If I look at build history I am only getting the error in latest build. Unfortunately I did a few major things in the latest build: upgraded to unity 2021 and added URP. Not sure which one is causing it!
     
  4. BorikN

    BorikN

    Joined:
    Mar 5, 2021
    Posts:
    2
    Same bug. Just upgraded to unity 2021.3.6.
     
  5. jarotheking

    jarotheking

    Joined:
    Mar 20, 2019
    Posts:
    3
    Hey, so I maybe found a solution. I tried to build with all Target Architectures(ARMv7, ARM64 and x86 and x86-64). I am not getting these errors anymore but I do get 2 new ones:

    FATAL EXCEPTION: GoogleApiHandler
    Process: com.google.android.dialer, PID: 1869

    and
    FATAL EXCEPTION: main
    Process: com.google.android.googlequicksearchbox:interactor, PID: 1502


    This is all there is. The good thing is that now the pixel 2 virtual doesnt crash on start. so this is maybe something regarding my project.
     
  6. Masashi-Wada

    Masashi-Wada

    Joined:
    Jul 6, 2010
    Posts:
    80
    Hi, I've been receiving the same report a few days ago.
    I am using 2020.3.36.

    I don't know what a GCE x86 phone is, but if it's a Google virtual device, it's either bad or it's starting an ARM-only APK despite being x86.

    I think this is a Google issue. My build doesn't include x86, so it won't work on x86 CPUs.
     
  7. jarotheking

    jarotheking

    Joined:
    Mar 20, 2019
    Posts:
    3
    So in the end I upgraded Unity to 2021.3.6 and builded with target architectures set to ARM64 only and it went through without any errors. If you can do that then it should work.

    I havent tried to build with only ARM64 on this .3.3 version, so it can be that only the target architecture is the "solution"
     
  8. namminh2005

    namminh2005

    Joined:
    Oct 11, 2019
    Posts:
    5
    I have same error on Google Pixel 2 (virtual)
     
    B-Erolskiy and JohnDoubleUB like this.
  9. ASondej

    ASondej

    Joined:
    Sep 15, 2020
    Posts:
    9
    Same here, apart from adding Unity IAP package, nothing important happened for my app, but I keep getting those errors since yesterday for an app update.
     
  10. Gordyus

    Gordyus

    Joined:
    Mar 3, 2016
    Posts:
    9
    Same error same virtual device, nothing really change in the app. I've try to upgrade the Unity version from 2021.2.18 to 2021.3.6 but it does not work.
     
  11. Kevin1970

    Kevin1970

    Joined:
    Dec 21, 2017
    Posts:
    10
    I too have same error on Google Pixel 2 (virtual).

    I'm not understanding why the ABI (Application binary interface?) is listed as ARMEABI (ARM?) where the device appears to be Intel X86?

    WTF is that all about? Are Google just wasting our time with this sh*t?


     
  12. JohnDoubleUB

    JohnDoubleUB

    Joined:
    Oct 31, 2019
    Posts:
    2
    Can confirm that I changed it so that I was only targeting ARM64 much like you and the simulated devices on google play console all pass without any errors for me too.

    I'm using Unity 2020.3.28f1 currently

    Don't know if its any help but incase it is here are the project settings I currently have:
    upload_2022-7-29_12-17-43.png

    I think I saw somewhere about being able to upload multiple app bundles, I wonder if exporting two separate versions targeting the different architectures would work? Just a thought, this is my first time messing around with mobile app development
     
  13. neodigy

    neodigy

    Joined:
    Jul 25, 2020
    Posts:
    1
    I have the same error with the same device, too.
    In my case, I select all architectures (include x86 chrome os, x86-64 chrome os), "Target Devices" switch to All Devices
    Screen Shot 2022-07-29 at 19.57.35.png

    Now the internal test has no error report.

    Screen Shot 2022-07-29 at 19.58.41.png
     
  14. ByteStormGmbH

    ByteStormGmbH

    Joined:
    Mar 21, 2021
    Posts:
    17
    We have the exact same problem here with the Google Pixel 2 Virt. Test.
    Looks like a Google Bug to me. We didn't have the problem before with the same settings.

    Update : Thanks for the tip @neodigy, with your solution it actually works. Now we just have to find out what's going on with the Pixel 2 device.

    Update 2 : Another test has shown that if you set it to OpenGLES 3.2 without Vulkan with only ARMv7 and ARMv8, it also works in the Play Store. This means that you no longer need the Chrome Packages.
     
    Last edited: Aug 1, 2022
    neodigy likes this.
  15. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Same thing with 2021.1.11f1 or 2021.3.7f1 LTS.

    2 errors after upload build :

    Fatal AndroidRuntime Exception detected => pixel 2
    Native crash of com.xxx.xxx => pixel 2

    I need to update my applications quickly and I need ARMv7 and ARM64 support :(

    Thx
     
  16. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Is it possible to submit the application even with this error under pixel?
     
  17. ByteStormGmbH

    ByteStormGmbH

    Joined:
    Mar 21, 2021
    Posts:
    17
    You have to change the settings in your Unity player settings so that Pixel2 is no longer used.
    For the time being, we have solved this with the setting OpenGLES 3.2 without Vulcan.

     
  18. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Thanks but the game crashes with these settings.

    It would be nice to have an answer from Unity to this problem now.

    Thx
     
  19. ByteStormGmbH

    ByteStormGmbH

    Joined:
    Mar 21, 2021
    Posts:
    17
    It depends on the error you received. Some similar errors also come from faulty plugins.
    It depends on the error you received. Some similar errors also come from faulty plugins.
     
  20. namminh2005

    namminh2005

    Joined:
    Oct 11, 2019
    Posts:
    5
    I downgraded to Unity 2020 and not get error on pixel 2
     
  21. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Version 2020 plz ?
     
  22. namminh2005

    namminh2005

    Joined:
    Oct 11, 2019
    Posts:
    5
    I used version 2020.3.14f1 LTS
     
  23. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Thx but app crash on start with this version.
     
    Last edited: Aug 10, 2022
  24. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    I'm still waiting for an urgent solution from the Unity team like many others I think.
     
    ByteStormGmbH likes this.
  25. ByteStormGmbH

    ByteStormGmbH

    Joined:
    Mar 21, 2021
    Posts:
    17
    Can you give us your crash Report?
     
  26. unitycodergp

    unitycodergp

    Joined:
    Feb 1, 2017
    Posts:
    47
    Exactly the same bug as the author of the original post. Just like everyone else.
     
  27. AsifNaeem

    AsifNaeem

    Joined:
    Apr 12, 2016
    Posts:
    23
    Facing the similar crashes on different devices
    Unity Version is 2021.3.5f

     
  28. flintcheeze

    flintcheeze

    Joined:
    Sep 10, 2015
    Posts:
    80
    Still no solution to this what is happening, I am tired
     
  29. RameshPoreddy

    RameshPoreddy

    Joined:
    Aug 3, 2017
    Posts:
    4
    We are also getting this prelaunch on GCE x86 phone after migrating to unity 2020.3.41f. None of our games in unity 2019 getting this report.
     

    Attached Files:

  30. flintcheeze

    flintcheeze

    Joined:
    Sep 10, 2015
    Posts:
    80
    Apk crash on start fix!
    Delete all android resolved library
    It will work
    But I highly advice you should delete the libraries little by little till you have a playable apk
    The crash is as a result of duplicate aar and plugins which Unity ignores on build