mapkit-android-demo
mapkit-android-demo copied to clipboard
Samsung crashes on Android 5.0
Hello. This crash happens on startup of the app, only on Samsung devices with 5.0 android version.
Logs:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.example.package <<<
backtrace:
#00 pc 0000000000037388 /system/lib/libc.so (tgkill+12)
#00 pc 0000000000013fd1 /system/lib/libc.so (pthread_kill+52)
#00 pc 0000000000014bef /system/lib/libc.so (raise+10)
#00 pc 0000000000011531 /system/lib/libc.so (__libc_android_abort+36)
#00 pc 000000000000fcbc /system/lib/libc.so (abort+4)
#00 pc 0000000000012701 /system/lib/libc.so (__libc_fatal+16)
#00 pc 00000000000115b5 /system/lib/libc.so (__assert2+20)
#00 pc 000000000006b999 /data/app/com.example.package-2/lib/arm/libc++_shared.so
#00 pc 000000000006bb35 /data/app/com.example.package-2/lib/arm/libc++_shared.so
#00 pc 000000000007e59d /data/app/com.example.package-2/lib/arm/libc++_shared.so
#00 pc 000000000007e621 /data/app/com.example.package-2/lib/arm/libc++_shared.so (std::terminate()+84)
#00 pc 000000000016e1e4 /data/app/com.example.package-2/lib/arm/libcom.yandex.runtime.so
Example of devices:
Initialization code of yandex map kit in Application class
:
MapKitFactory.setApiKey(context.getString(R.string.yandex_maps_api_key))
if (!Android.isLolipopOrLater()) {
Thread.currentThread().contextClassLoader = context.classLoader
}
SearchFactory.initialize(context)
Yandex dependencies:
mobMetricaLib : "com.yandex.android:mobmetricalib:3.13.1",
mobileAds : "com.yandex.android:mobileads:2.141",
adMob : "com.yandex.ads.mediation:mobileads-admob:1.7.0",
adMobMediation : "com.yandex.ads.adapter:admob-mobileads:0.4.0",
myTarget : "com.yandex.ads.mediation:mobileads-mytarget:1.3.0",
mapkit : "com.yandex.android:mapkit:3.5.0",
search : "com.yandex.android:search:3.5.0"
How to fix it?
@eberkovich our users continue to experience this issue, could you help with resolving this bug? Thanks!
Hello, There will be release of mapkit on this week or beginning of the next, please check it. If the problem persists, please attach new full crash dump and logs.
@v-grishechko Do you still experience this problem?