Alarming java.lang.Error starting with version 2019.3.8 and 2019.3.10

Dear all,

few weeks ago I published an update to my app that was originally compiled with 2019.2.16. Crash rate was negligible (0.21 %)
For the update I used Unity 2019.3.8 and immediately I started getting java.lang.Error mainly on Huawei devices running 8.0. My crash rate cilmbed to 1.5% .
The I changed Unity tot 2019.3.10 in an attempt to slow down the crashes, it did the trick but I still have a 0.5% crash rate.

All the java.lang.Error crashes are something like:

Code (CSharp):

1. java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2. Version '2019.3.10f1 (5968d7f82152)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
3. Build fingerprint: 'HUAWEI/AGSEEA/HWAGS-Q:8.0.0/HUAWEIAGS-W09/126(C431):user/release-keys'
4. Revision: '0'
5. ABI: 'arm64'
6. Timestamp: 2020-04-27 16:34:48+0100
7. pid: 29196, tid: 30606, name: Thread-96  >>> net.homeip.alphabet <<<
8. uid: 10107
9. signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4a
10. Cause: null pointer dereference
11. x0  0000000000000000  x1  0000000000000000  x2  000000744cd8b730  x3  000000744cd8b860
12. x4  0000000000000000  x5  0000000000000005  x6  0000000000000000  x7  0000000000000000
13. x8  000000745e900650  x9  000000000000000a  x10 0000000000004001  x11 0000000000000000
14. x12 000000745fd8d000  x13 0000000000000001  x14 0000000000000069  x15 0000000000000001
15. x16 00000074c401f1e0  x17 00000074e3066ab0  x18 00000074d24098f0  x19 000000744cd8b860
16. x20 0000000000000000  x21 0000000000000000  x22 000000744cd8b730  x23 0000000000000003
17. x24 0000000000000000  x25 0000007459a462a0  x26 0000000000000000  x27 0000000000000000
18. x28 0000000000000004  x29 000000744cd8b988
19. sp  000000744cd8b6a0  lr  00000074c337e810  pc  000000745e930b74
20. backtrace:
21.   at .
22.   at .
23.   at .
24.   at .
25.   at .
26.   at libil2cpp.0x6dfb74 (Native Method)  [B]il2cpp::vm::Method::GetParamCount(MethodInfo const*)[/B]
27.   at libunity.0x2e980c (Native Method)
28.   at libunity.0x2f6c60 (Native Method)
29.   at libunity.0x1684dc (Native Method) [B]UnityJavaProxy_invoke(_JNIEnv*, _jobject*, long, _jstring*, _jobjectArray*)[/B]
30.   at base.0xa55c0 (Native Method)

Could someone help to understand where in the code this could be triggered?


Regards,
Antonio.

 

Hello, I know that it has been almost 3 years since this has been posted, but did you find a solution for that? If you remember! I'm having something very similar but I can't find the exact source since I can't reproduce it on demand.

 

I have replaced our ad mediation from AdMob to AppLovin MAX, and 100% of this super frequent "GetParamCount" crashes aren't there anymore.

 

@damelin hey which version of AdMob in AppLoving Max are you using? We are facing similar issue.

 

I'm currently using the AppLovin google adapter 21.5.0.0, which seems to be the latest version of AdMob for Android at the moment.