Search Unity

Fatal AndroidRuntime Exception on Google Play Pre-Launch Report

Discussion in 'General Discussion' started by hangarter, Jun 13, 2022.

  1. hangarter

    hangarter

    Joined:
    Mar 14, 2016
    Posts:
    23
    Hi All,

    I'm trying to publish for the first time a game on the google play store, and after finding the option in unity to make an asset bundle and building it, I uploaded to the store.
    So after the upload, I got in my console a report with two errors I can't figure out what could be:

    Code (CSharp):
    1. FATAL EXCEPTION: UnityMain
    2. Process: com.HangarterStudios.FrostbiteIceCubeAdventure, PID: 6886
    3. java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    4. Version '2022.1.1f1 (53d13f540f71)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    5. Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    6. Revision: '0'
    7. ABI: 'arm'
    8. Timestamp: 2022-06-12 23:49:34-0700
    9. pid: 6886, tid: 7930, name: UnityMain  >>> com.HangarterStudios.FrostbiteIceCubeAdventure <<<
    10. uid: 10093
    11. signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    12.     r0  00000001  r1  dba9a700  r2  00003434  r3  00000000
    13.     r4  00000000  r5  00000001  r6  dba9a700  r7  c103b795
    14.     r8  00000002  r9  ba5a328c  r10 00000000  r11 ba59ddec
    15.     ip  e4b622d0  sp  c38a33b8  lr  c0a611f0  pc  00000000
    And

    Code (CSharp):
    1. *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    2. Version '2022.1.1f1 (53d13f540f71)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
    3. Build fingerprint: 'generic/gce_x86_phone/gce_x86:9/PGR1.190916.001/5877764:userdebug/test-keys'
    4. Revision: '0'
    5. ABI: 'arm'
    6. Timestamp: 2022-06-12 23:49:34-0700
    7. pid: 6886, tid: 7930, name: UnityMain  >>> com.HangarterStudios.FrostbiteIceCubeAdventure <<<
    8. uid: 10093
    9. signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x0
    10.     r0  00000001  r1  dba9a700  r2  00003434  r3  00000000
    11.     r4  00000000  r5  00000001  r6  dba9a700  r7  c103b795
    12.     r8  00000002  r9  ba5a328c  r10 00000000  r11 ba59ddec
    13.     ip  e4b622d0  sp  c38a33b8  lr  c0a611f0  pc  00000000
    It strikes me as odd that it would throw an exception given that in Unity it works AND when deploying to my phone on Build And Run it works perfectly.

    Does anybody know what that could be?
     
    hangarter, Jun 13, 2022
    #1

  2. dreamo_lucas

    dreamo_lucas

    Joined:
    Jun 4, 2021
    Posts:
    1
    This is a bug in Google Play Test. gce_x86_phone is a virtual machine for x86 testing. The crash occurred while running the build for arm on that machine. If you exclude x86 from AndroidManifest.xml or Google Play Developer Console's Device Catalog to not support it, the test should not proceed. But sometimes this happens, and it's been happening a lot lately. Ignore it.
     
    dreamo_lucas, Jul 19, 2022
    #2