How to understand what kind of failure Google got when checking?

Question

Google

The game is made on Unity, uploaded an alpha test to Google Play, he answered me like this (after checking)

spoiler

Native crash of com.MyCompany.MyGame
API not from SDK Ljava/lang/invoke/MethodHandles$Lookup;->(Ljava/lang/Class;I)V

details

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2020.3.25f1 (9b9180224418)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'samsung/starqlteue/starqlteue:8.0.0/R16NW/G960U1UEU1ARBG:user/release-keys'
Revision: '14'
ABI: 'arm64'
Timestamp: 2022-01-18 10:16:42-0800
pid: 11887, tid: 11912, name: UnityMain >>> com.MyCompany.MyGame <<<
uid: 10236
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

ну а в Logcat там вообще непонятно....

01-18 10:16:01.217: E/adbd(2456): recv: OPEN 0138187f 00000000 00ce:73 68 65 6C 6C 3A 5B 20 2D 65 20 2F 64 61 74 61 2F 6C 6F 63 61 .............. 73 74 61 74 75 73 00
01-18 10:16:01.217: E/adbd(2456): service_to_fd: shell:[ -e /data/local/tmp/5ace9caf-ce4b-4418-8baa-.............

2 more like this

spoiler

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/starqlteue/starqlteue:8.0.0/R16NW/G960U1UEU1ARBG:user/release-keys'
Revision: '14'
ABI: 'arm64'
pid: 12829, tid: 12878, name: UnityMain >>> com.......... <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'thread.cc:2023] Throwing new exception 'PushLocalFrame' with unexpected pending exception: java.lang.OutOfMemoryError: PushLocalFrame'
x0 0000000000000000 x1 000000000000324e x2 0000000000000006 x3 0000000000000008
x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0080808080808080
x8 0000000000000083 x9 5831b8fcea30abd9 x10 0000000000000000 x11 0000000000000001
x12 ffffffffffffffff x13 0000000000000008 x14 ffffffffffffffff x15 000060e95dea0be3
x16 000000766634a2e8 x17 00000076662ebbdc x18 0000007658a0b4b0 x19 000000000000321d
x20 000000000000324e x21 00000076430c63c0 x22 0000000000000002 x23 0000000000000201
x24 0000000000000011 x25 0000007645fa2d00 x26 0000000000000200 x27 0000000000000043
x28 000000764918fd51 x29 000000764918fa50 x30 000000766629e2a4
sp 000000764918fa10 pc 00000076662ebbe4 pstate 0000000060000000
backtrace:
#00 pc 000000000006bbe4 /system/lib64/libc.so (tgkill+8)
#01 pc 000000000001e2a0 /system/lib64/libc.so (abort+88)
#02 pc 0000000000437854 /system/lib64/libart.so (_ZN3art7Runtime5AbortEPKc+528)
#03 pc 0000000000437f64 /system/lib64/libart.so (_ZN3art7Runtime7AborterEPKc+24)
#04 pc 000000000052263c /system/lib64/libart.so (_ZN7android4base10LogMessageD1Ev+900)
#05 pc 0000000000462560 /system/lib64/libart.so (_ZNK3art6Thread24AssertNoPendingExceptionEv+1144)
#06 pc 0000000000128094 /system/lib64/libart.so (_ZN3art11ClassLinker9FindClassEPNS_6ThreadEPKcNS_6HandleINS_6mirror11ClassLoaderEEE+64)
#07 pc 0000000000311374 /system/lib64/libart.so (_ZN3art3JNI9FindClassEP7_JNIEnvPKc+1432)
#08 pc 00000000002ba198 /data/app/com.............-xDUt1MnAwkILx0YnPHxMWw==/lib/arm64/libunity.so
#09 pc 00000000002e4990 /data/app/com...........-xDUt1MnAwkILx0YnPHxMWw==/lib/arm64/libunity.so
#10 pc 000000000000ce7c /data/app/com.........-xDUt1MnAwkILx0YnPHxMWw==/oat/arm64/base.odex (offset 0x5000)

What to watch, where to start?