Closed PickleJesus123 closed 4 years ago
stowy
commented
4 years ago Hi @famishedmammal - thanks for reporting. This looks like an issue with the Android SDK, specifically exoplayer3. Are there any other crash logs? It would be better to track if you reported the issue on the developer forum as they have email support and can file and track bugs etc.
PickleJesus123
commented
4 years ago Hey @stowy , thanks for the quick reply. I've made a post on the developer forum as you recommended.
90% of the errors are Java.lang.Error relating to "split_config". Could it be that the newest version of Admob Plugin isn't suited to NDK R19 which Unity uses in 2019.3.0f5? Or perhaps something essential is getting stripped now that developers always split their binaries (ARMv7 + ARM64) and always use il2cpp in 'build options'? As I mentioned in my original post, there seem to be various issues with GoogleMobileAdsPlugin's build.gradle file, which I assume is indicative of deeper issues.
We are also getting errors like this:
java.lang.Error: Version '2019.3.0f5 (44796c9d3c2c)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a' Build fingerprint: 'HUAWEI/ATU-L22/HWATU-QG:8.0.0/HUAWEIATU-L22/157(C636):user/release-keys' Revision: '0' ABI: 'arm64' Timestamp: 2020-01-21 16:57:36+0800 pid: 29918, tid: 30499, name: Thread-46 >>> com.my.appname <<< uid: 10363 signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4a Cause: null pointer dereference x0 0000000000000000 x1 0000000000000000 x2 0000007c176d0450 x3 0000007c176d0580 x4 0000000000000000 x5 0000000000000168 x6 0000007caf8028c0 x7 ef23a294ad47a75e x8 0000007c2f1711ec x9 000000000000000a x10 0000000000004000 x11 0000007c176d2588 x12 0000000000000000 x13 0000007c176d2588 x14 0000007c176d24f0 x15 0000000000007723 x16 0000007c93bd3200 x17 0000007cb27632b0 x18 0000000000004000 x19 0000007c176d0580 x20 0000000000000000 x21 0000000000000000 x22 0000007c176d0450 x23 0000000000000003 x24 0000000000000000 x25 0000007c29d0a0a0 x26 0000000000000000 x27 000000009c2d6648 x28 0000000000000004 x29 0000007c176d06a8 sp 0000007c176d03c0 lr 0000007c92bdd744 pc 0000007c2f19cbf0 backtrace: at libil2cpp.0x488bf0 (Native Method) at libunity.0x5bb740 (Native Method) at libunity.0x5c80a8 (Native Method) at libunity.0x2906ac (Native Method) at base.0x5b740 (Native Method)
thiagolr
commented
4 years ago Is this already fixed? When will it be available?
Since upgrading my live app to Unity 2019.3.0f5 and admob 4.2.1, the number of crashes has skyrocketed for my app (it has been beyond the bad behaviour threshold for a whole month now). Most of my crash clusters have "googleads.internal" somewhere in them.
I can't help but notice that when I press "export project" and open my unity app in anrdoid studio, the build.gradle file for GoogleMobileAdsPlugin has 'targetsdkversion=19' (super outdated). No ndk abifilters are present in the GoogleMobileAdsPlugin build.gradle file either. Also, along the top of the GoogleMobileAdsPlugin build.gradle file it says "apply plugin: android-library" which is another deprecated feature now that com.android.library is used.
I would like to emphasize that quite literally 100% of unity android developers use the "il2cpp" build option (not Mono!) due to Google Play's 64 bit requirement. Also, please keep in mind the newer versions of unity use google's ndk R19 now
Extra info about my project: we previously had Google Games Services but have since removed it. We previously used ad mediation through googleads (our network included: admob, unityads and chartboost) but have removed the code for it and PAUSED mediation on our console. App is crashing like crazy now.
Here are some sample crash clusters I have been getting a lot recently:
and: