java.lang.Error com.google.android.gms.ads.internal.webview.j.k

386 views
Skip to first unread message

LIVEZEN GM

unread,
Jun 21, 2019, 5:20:51 AM6/21/19
to Google Mobile Ads SDK Developers
We are using the Unity engine and Admob mediation.
The following types of crashes occur frequently.

java.lang.Error: FATAL EXCEPTION [FinalizerWatchdogDaemon] Unity version : 2019.1.3f1 Device model : Sony SOV37 Device fingerprint: KDDI/SOV37_jp_kdi/SOV37:9/52.0.C.5.46/893153200:user/release-keys Caused by
at com.google.android.gms.ads.internal.webview.j.k (com.google.android.gms.policy_ads_fdr_dynamite@20290004@20290004.249178941.249178941:3)
at com.google.android.gms.ads.internal.webview.v.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290004@20290004.249178941.249178941:4)
at com.google.android.gms.ads.internal.webview.t.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290004@20290004.249178941.249178941:10)
at com.google.android.gms.ads.nonagon.ad.rewardedvideo.c.finalize (com.google.android.gms.policy_ads_fdr_dynamite@20290004@20290004.249178941.249178941:2)
at java.lang.Daemons$FinalizerDaemon.doFinalize (Daemons.java:250)
at java.lang.Daemons$FinalizerDaemon.runInternal (Daemons.java:237)
at java.lang.Daemons$Daemon.run (Daemons.java:103)
at java.lang.Thread.run (Thread.java:764)


java.lang.Error: FATAL EXCEPTION [FinalizerWatchdogDaemon] Unity version : 2019.1.3f1 Device model : LGE LM-Q710(FGN) Device fingerprint: lge/cv7a_lao_com/cv7a:8.1.0/OPM1.171019.019/1911210011517:user/release-keys Caused by
at com.google.android.gms.ads.internal.webview.j.k (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:3)
at com.google.android.gms.ads.internal.webview.v.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:4)
at com.google.android.gms.ads.internal.webview.t.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:10)
at com.google.android.gms.ads.nonagon.ad.rewardedvideo.c.finalize (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:2)
at java.lang.Daemons$FinalizerDaemon.doFinalize (Daemons.java:250)
at java.lang.Daemons$FinalizerDaemon.runInternal (Daemons.java:237)
at java.lang.Daemons$Daemon.run (Daemons.java:103)
at java.lang.Thread.run (Thread.java:764)


java.lang.Error: FATAL EXCEPTION [FinalizerWatchdogDaemon] Unity version : 2019.1.3f1 Device model : LGE LG-H933 Device fingerprint: lge/joan_global_ca/joan:8.0.0/OPR1.170623.026/190301858a545:user/release-keys Caused by
at com.google.android.gms.ads.internal.webview.j.k (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:3)
at com.google.android.gms.ads.internal.webview.v.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:4)
at com.google.android.gms.ads.internal.webview.t.destroy (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:10)
at com.google.android.gms.ads.nonagon.ad.rewardedvideo.c.finalize (com.google.android.gms.policy_ads_fdr_dynamite@20290000@20290000.249178941.249178941:2)
at java.lang.Daemons$FinalizerDaemon.doFinalize (Daemons.java:250)
at java.lang.Daemons$FinalizerDaemon.runInternal (Daemons.java:237)
at java.lang.Daemons$Daemon.run (Daemons.java:103)
at java.lang.Thread.run (Thread.java:764)


Mobile Ads SDK Forum Advisor Prod

unread,
Jun 21, 2019, 6:08:10 AM6/21/19
to livez...@gmail.com, google-adm...@googlegroups.com
Hi there,

Thank you for reaching out to us.

There is currently a bug with WebView being garbage-collected while it is still displaying an ad. This has already been fixed by the Engineering team; however, there is yet to be an update on the release date for the fix. You may follow our blog and our Release Notes for future updates.

In the meantime, you may try this following workaround if you are using the new Rewarded Ad API: kindly retain a reference to the old rewarded ad object, and use a new variable when requesting for a new rewarded ad.

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5001UCYlX7:ref

LIVEZEN GM

unread,
Jun 21, 2019, 7:02:37 AM6/21/19
to Google Mobile Ads SDK Developers
Hi,

Thank you for your feedback.
We will wait for the new version.


2019년 6월 21일 금요일 오후 7시 8분 10초 UTC+9, mobileadssdkforumadvisor 님의 말:

Sailendu Behera

unread,
Jun 29, 2019, 1:39:37 PM6/29/19
to Google Mobile Ads SDK Developers
Hello, is this issue fixed in plugin version 3.18 or we have to wait for the next version?

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 30, 2019, 7:54:55 PM6/30/19
to sailend...@gmail.com, google-adm...@googlegroups.com
Hi Sailendu,


Thank you for reaching out to us.

I'm afraid the issue may still be present in v3.18 of the Android AdMob SDK, since this version had focused more on the AndroidX migration. In the meantime, you may follow our blog and our Release Notes for future updates.

Sailendu Behera

unread,
Jul 1, 2019, 4:18:48 AM7/1/19
to Google Mobile Ads SDK Developers
Hello, you said on June 21 that the issue has been fixed by engineering team, and it's been 10 days, so please release the update as this bug is really affecting our app's crash rate. Please...

LIVEZEN Corp.

unread,
Jul 3, 2019, 7:03:04 PM7/3/19
to Google Mobile Ads SDK Developers
Hello,

The latest version 3.18 crashes on google login.(GPGS)

Regards,


2019년 6월 21일 (금) 오후 8:02, LIVEZEN GM <livez...@gmail.com>님이 작성:
--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/a2a08efb-4410-473b-ae81-122ee20a1e7b%40googlegroups.com.

Mobile Ads SDK Forum Advisor Prod

unread,
Jul 3, 2019, 7:55:11 PM7/3/19
to livez...@gmail.com, google-adm...@googlegroups.com
Hi there,

Could you kindly provide the details below using the Reply privately to author option so that I can investigate the issue?
  • Error logs encountered
  • A copy of your sample project (that reproduces the issue)
  • Steps for replicating the issue
Reply all
Reply to author
Forward
0 new messages