I’ve been testing admob rewarded for a while and some times the ad finishes ok but some times it finishes with black screen. Don’t really know why but it’s not perfectly working on Android with 64 bit.
I see a big number of error in Android vitals with this last version:
java.util.concurrent.TimeoutException :
at com.google.android.gms.ads.internal.webview.j.k (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:3)
at com.google.android.gms.ads.internal.webview.v.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:4)
at com.google.android.gms.ads.internal.webview.t.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:10)
at com.google.android.gms.ads.nonagon.ad.interstitial.b.finalize (com.google.android.gms.policy_ads_fdr_dynamite@20300002@20300002.251657827.251657827:5)
at java.lang.Daemons$FinalizerDaemon.doFinalize (Daemons.java:209)
at java.lang.Daemons$FinalizerDaemon.run (Daemons.java:192)
at java.lang.Thread.run (Thread.java:818)
I read 2 threads discussing the issue, and it seems to be something on google’s backend, because it’s affected people with apps that havent changed their app or SDKs for months. A google employee mentioned their next release will fix it.
https://github.com/googleads/googleads-mobile-android-examples/issues/170
https://groups.google.com/forum/#!topic/google-admob-ads-sdk/cbr_oV4Yzfg
The last post on this thread mentions …
“I solved the problem by not calling “interstitial.loadad() (for loading next ad)” directly after interstitial.show() . So don’t load next ad until your shown ad is closed.”
That might be worth trying to see if it fixes this issue.
In the thread the issue seems to be affecting around 5% of session, and affects both rewarded and interstitial, and affect people with versions of GMS back to 15.0.1.
Since, the problem existed before 64bit betas, and the threads don’t mention it being 64-bit only. I’m assuming the problem is on 32 and 64bit.