Closed huyptmaxmobile closed 1 year ago
Hello! You mean v5.7.0 and 5.8.0, right? However we don't use native calls in our sdk. So we need crash stack trace and your App Id to check the problem. Thank you
Hi, Sure, I have edited the versions. I only have this short stack trace from Play Console of both apps
*** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 18132 >>> com.xxx.xxx<<<
backtrace:
#00 pc 0x000000000005c310
#01 pc 0x0000000000058838 /data/data/com.xxx.xxx/app_pccache/5/7B8F7DD4852F73BBFA173EB6B41A78FEF0FC34F5/pcam.jar
'app_pccache' is not our cache. It might be related to AdMob, which uses native calls. You can check out these issues https://groups.google.com/g/google-admob-ads-sdk/search?q=app_pccache or contact AdMob for more information.
Hello, We started implementing Yandex Mobile Ads recently in parallel with Google Admob. We use Google Mobile Ads SDK and Yandex Mobile Ads SDK separately, not mediation. Most of the applications are still running fine with no errors since applying Yandex Mobile Ads. However, there are 2 applications that receive unusual crash reports on Google Play Console (not on Crashlytics), about 5-7% (Very large number) with this same error:
We are using Google Mobile Ads SDK v21.3.0. When we found the error we were using Yandex Mobile Ads SDK v5.7.0, we tried to upgrade to v5.8.0 and target SDK 33 but the error persisted.
Please help us fix this, if we can't solve this we will probably have to remove Yandex Ads in future updates.
Thank you!