I recently updated with the latest version of sdkbox 2.7.1.0 to update admob specifically to remove uiWebview. On IOS, all is fine. However, I have a problem with Android. The pre-launch report reports a bug with one specific device (Pixel on Android 7.1). The app does not crash, it just do not launch. It tries to launch for a while, then the pre-launch robot stops and shut down the app. I tried different combination:
PROP_TARGET_SDK_VERSION 27, 28, 29.
PROP_BUILD_TOOLS_VERSION 29.0.3, 27.0.3
com.google.android.gms:play-services-ads:17.2.0, 18.3.0, 19.3.0
com.google.android.gms:play-services-base:16.1.0 or just no service-base at all
And they all end up with the same result. All devices pass except Pixel on 7.1.(I have no problem on my test devices however I do not have a 7.1 to try with). I contacted Google and they said there are no known issue with this device.
The only way I was able to make it work is by replacing the PluginAdMob.jar by the previous one and it works. Well kinda. It seems to work, I published the app, but some Huawei devices gets a crash
: #00 pc 000000000006bd00 /system/lib64/libc.so (tgkill+8)
#01 pc 000000000006919c /system/lib64/libc.so (pthread_kill+64)
#02 pc 0000000000023e68 /system/lib64/libc.so (raise+24)
#03 pc 000000000001c8ec /system/lib64/libc.so (abort+52)
#04 pc 000000000042e5f8 /system/lib64/libart.so (art::Runtime::Abort()+352)
#05 pc 00000000000e5424 /system/lib64/libart.so (art::LogMessage::~LogMessage()+1204)
#06 pc 0000000000451124 /system/lib64/libart.so (art::AssertNoPendingException() const+836)
#07 pc 00000000001247d8 /system/lib64/libart.so (art::ClassLinker::FindClass(art::Thread*, char const*, art::Handleart::mirror::ClassLoader)+68)
#08 pc 0000000000324e50 /system/lib64/libart.so (art::JNI::FindClass(_JNIEnv*, char const*)+2780)
#09 pc 0000000000379160 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so (sdkbox::JNIUtils::GetClassObjectFromName(char const*, _JNIEnv*)+48)
#10 pc 00000000003796c8 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so (sdkbox::JNIUtils::GetJNIStaticMethodInfo(char const*, char const*, char const*, _JNIEnv*)+56)
#11 pc 00000000003759c4 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so (sdkbox::SdkboxCore::isGooglePlayServicesAvailable()+136)
#12 pc 0000000000362570 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so
#13 pc 000000000035fd90 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so (sdkbox::SdkboxCore::sessionStart()+280)
#14 pc 000000000035fe44 /data/app/com.bewgames.templeruins-1/lib/arm64/libMyGame.so (sdkbox::SdkboxCore::onStart()+36)
#15 pc 00000000007f6d3c /data/app/com.bewgames.templeruins-1/oat/arm64/base.odex (offset 0x7b5000)
So I assume the old jar file is missing a class or something. But why only 2-3 specific huawei device? This is unknown. Anyway, this is kind of a patch that I should not have to do.
I also tried to download the sdkbox files manually, and import them manually. Same result.
Anyone else had the same issue? Any idea what could be happening?