Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Краш у Vungle на телефонах без гугл сервисов. #288

Open
stayf opened this issue Oct 27, 2024 · 2 comments
Open
Labels
transmitted Issue transmitted to inner service

Comments

@stayf
Copy link

stayf commented Oct 27, 2024

Использую com.yandex.android:mobileads:7.6.0 и добавил недавно com.yandex.ads.mediation:mobileads-vungle:7.4.1.0
Выложил сборку в рустор. И полетели краши у телефонов без гугл плей сервисов.
Девайсы: Realme 11, CTR-L81, ADY-LX9, Legion Y70, BV5200 Pro, S98Pro
Краш прям критический, прошу обратить внимание и пофиксить оперативно или подсказать, что мне сделать, чтобы его убрать на телефонах без плей сервисов.

          Fatal Exception: java.io.IOException: Google Play services not available
       at com.google.android.gms.ads.identifier.AdvertisingIdClient.zzb(com.google.android.gms:play-services-ads-identifier@@17.1.0:21)
       at com.google.android.gms.ads.identifier.AdvertisingIdClient.getAdvertisingIdInfo(com.google.android.gms:play-services-ads-identifier@@17.1.0:3)
       at com.vungle.ads.internal.platform.AndroidPlatform.getGoogleAdvertisingInfo(AndroidPlatform.kt:102)
       at com.vungle.ads.internal.platform.AndroidPlatform.getAdvertisingInfo(AndroidPlatform.kt:127)
       at com.vungle.ads.internal.network.VungleApiClient.getDeviceBody$vungle_ads_release(VungleApiClient.kt:652)
       at com.vungle.ads.internal.network.VungleApiClient.getDeviceBody(VungleApiClient.kt:636)
       at com.vungle.ads.internal.network.VungleApiClient.requestBody(VungleApiClient.kt:626)
       at com.vungle.ads.internal.network.VungleApiClient.requestAd(VungleApiClient.kt:339)
       at com.vungle.ads.internal.load.DefaultAdLoader.fetchAdMetadata(DefaultAdLoader.kt:58)
       at com.vungle.ads.internal.load.DefaultAdLoader.requestAd(DefaultAdLoader.kt:43)
       at com.vungle.ads.internal.load.BaseAdLoader.loadAd$lambda-0(BaseAdLoader.kt:203)
       at com.vungle.ads.internal.executor.VungleThreadPoolExecutor$Companion.wrapRunnableWithFail(VungleThreadPoolExecutor.kt:36)
       at com.vungle.ads.internal.executor.VungleThreadPoolExecutor$Companion.access$wrapRunnableWithFail(VungleThreadPoolExecutor.kt:31)
       at com.vungle.ads.internal.executor.VungleThreadPoolExecutor$Companion$getWrappedRunnableWithFail$2.run(VungleThreadPoolExecutor.kt:67)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
       at java.lang.Thread.run(Thread.java:1012)
        
@mobile-ads-github
Copy link
Collaborator

Спасибо за Ваше обращение, для разбора создана задача с номером PCODESUP-3924. Мы ознакомимся и вернемся с ответом в течение 2 дней, возможно запросим дополнительную информацию.

Thank you for your message, a task with the number PCODESUP-3924 has been created for analysis. We will get acquainted and return with the answer within 2 days, we may request additional information.

@mobile-ads-github mobile-ads-github added the transmitted Issue transmitted to inner service label Oct 27, 2024
@mobile-ads-github
Copy link
Collaborator

Добрый день! Передали в разработку, изучаем кейс

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
transmitted Issue transmitted to inner service
Projects
None yet
Development

No branches or pull requests

2 participants