Unity Android app crash after start .Error: signal 6 (SIGABRT), code -6

Unity Engine
,
1

Hi,
I have two Android devices - one with 64bit architecture and second with 32bit. Both were working fine. But today suddenly application crashes after start with his error on 32bit device:

2019-10-28 15:34:27.316 24912-24954/? E/CRASH: pid: 24912, tid: 24954, name: UnityMain  >>> com.myCompany.myApp <<<
2019-10-28 15:34:27.858 24912-24954/? E/CRASH:     #02  pc 007951dc  /data/app/com.myCompany.myApp-6edSH8bTsYzw6LwqWQ7D0A==/lib/arm/libil2cpp.so (il2cpp::vm::MetadataCache::GetMethodPointer(Il2CppImage const*, unsigned int)+124)
2019-10-28 15:34:27.858 24912-24954/? E/CRASH:     #03  pc 007a3ed0  /data/app/com.myCompany.myApp-6edSH8bTsYzw6LwqWQ7D0A==/lib/arm/libil2cpp.so (il2cpp::vm::MetadataCache::Initialize()+2148)
2019-10-28 15:34:27.872 24912-24954/? E/AndroidRuntime: FATAL EXCEPTION: UnityMain
    Process: com.myCompany.myApp, PID: 24912
    java.lang.Error: signal 6 (SIGABRT), code -6 (?), fault addr --------
    Build fingerprint: 'lge/mlv5_global_com/mlv5:8.1.0/O11019/19067002244a3:user/release-keys'
    Revision: '0'
    pid: 24912, tid: 24954, name: UnityMain  >>> com.myCompany.myApp <<<
        r0 00000000  r1 0000617a  r2 00000006  r3 00000008
        r4 00006150  r5 0000617a  r6 85840b84  r7 0000010c
        r8 00000000  r9 858416f4  sl 00000001  fp 85840bc8
        ip 86a77c84  sp 85840b70  lr a8da793d  pc a8da147a  cpsr 85840880
   
        at libc.abort(abort:63)
        at libc.__assert2(__assert2:20)
        at libil2cpp.il2cpp::vm::MetadataCache::GetMethodPointer(Il2CppImage const*, unsigned int)(vm:124)
        at libil2cpp.il2cpp::vm::MetadataCache::Initialize()(vm:2148)

Only thing that maybe happened was to use Play Services Resolver - however I had reverted changes.
Please help.

2

Did you make any headway on this?

3

did you reproduce the crash on your device? Does your device have low memory when the crash happens? How much free RAM does the device have when it crashed?
Considering OP’s post was from 2019, it’s better you make your own thread with detailed information on your Unity version and what info you collected.