Unity 2019.2.8f IL2CPP crash, but not Mono

Unity Engine
,
1

Hello! When I switched to the IL2CPP build, I got a lot of crashes of this type. I tested this in Android 6 and 10 on different phones with same result.
If you need source, i could sent it to Unity team member via pm. Or even all project via bug report.
Here is my crashalytics report

Fatal Exception: java.lang.Error: FATAL EXCEPTION [UnityMain]
Unity version     : 2019.2.8f1
Device model      : Google Pixel 3a
Device fingerprint: google/sargo/sargo:10/QP1A.190711.020.C3/5869620:user/release-keys

Caused by java.lang.Error: signal 6 (SIGABRT), code -1 (?), fault addr --------
Build fingerprint: 'google/sargo/sargo:10/QP1A.190711.020.C3/5869620:user/release-keys'
Revision: 'MP1.0'
pid: 6459, tid: 6665, name: UnityMain  >>> com.test.test<<<
    r0 00000000  r1 00001a09  r2 00000006  r3 9c4fc050
    r4 9c4fc064  r5 9c4fc048  r6 0000193b  r7 0000016b
    r8 9c4fc060  r9 9c4fc050  sl 9c4fc080  fp 9c4fc070
    ip 00001a09  sp 9c4fc020  lr e968f6c3  pc e968f6d6  cpsr bc901780

       at libc.abort(abort)
       at libil2cpp.__gnu_cxx::__verbose_terminate_handler()(__verbose_terminate_handler:226)
2

Anyone?

3

The stacktrace has only 2 frames? Is there more log ?

4

There are a lot of code, but all of this related to fabric calls.

How should i properly get full log from device?

Update:have sent to you via pm logcat report.

5

I’m having the same issue, I couldn’t replicate on empty project, because it involves implement all game again, because I haven’t certainly where is the problem. My suspect is that is being caused by the stripping process.