Admob 19.7.0 large increase in native crashes - Fatal signal 11 (SIGSEGV) during loading WebView library

1,584 views
Skip to first unread message

Alexander VI

unread,
Mar 22, 2021, 11:16:05 PM3/22/21
to Google Mobile Ads SDK Developers
I see a huge spike in crashes - Fatal signal 11 (SIGSEGV) in Google Play Console.
It started on March 24th.

All crashes related to loading system webview library:
---
#00 pc 00000000034529dc /data/app/com.google.android.webview-ImuqHGfiU3UXH1nRbYo55Q==/base.apk!libmonochrome.so (offset 0x2d3000)
---
#00 pc 0000000002919eba /data/app/com.android.chrome-2/base.apk (offset 0xb09000)
---
#00 pc 0000000002919eba /data/app/com.android.chrome-bSzvL_ColEJkHiQqVzH9TQ==/base.apk (offset 0xb09000)
---
I even faced the same crash during development and testing on Galaxy S5 with Android 6 , here is the logcat output:
03-23 02:52:40.093 22752-22752/? E/Zygote: v2
03-23 02:52:40.093 22752-22752/? I/libpersona: KNOX_SDCARD checking this for 10347
03-23 02:52:40.093 22752-22752/? I/libpersona: KNOX_SDCARD not a persona
03-23 02:52:40.103 22752-22752/? W/SELinux: Function: selinux_compare_spd_ram, index[1], priority [2], priority version is VE=SEPF_SECMOBILE_6.0.1_0032
03-23 02:52:40.103 22752-22752/? E/Zygote: accessInfo : 0
03-23 02:52:40.103 22752-22752/? W/SELinux: SELinux: seapp_context_lookup: seinfo=default, level=s0:c512,c768, pkgname=com.mycomp.myapp
03-23 02:52:40.103 22752-22752/? I/art: Late-enabling -Xcheck:jni
03-23 02:52:40.123 22752-22752/? D/TimaKeyStoreProvider: TimaSignature is unavailable
03-23 02:52:40.123 22752-22752/? D/ActivityThread: Added TimaKeyStore provider
03-23 02:52:40.153 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.163 22752-22752/com.mycomp.myapp W/ActivityThread: Application com.mycomp.myapp can be debugged on port 8100...
03-23 02:52:40.183 22752-22752/com.mycomp.myapp I/art: Starting a blocking GC Explicit
03-23 02:52:40.203 22752-22752/com.mycomp.myapp I/art: Explicit concurrent mark sweep GC freed 21396(1059KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 14MB/24MB, paused 232us total 21.128ms
03-23 02:52:40.223 22752-22752/com.mycomp.myapp V/StudioTransport: Agent command stream started.
03-23 02:52:40.233 22752-22752/com.mycomp.myapp I/MultiDex: VM with version 2.1.0 has multidex support
03-23 02:52:40.233 22752-22752/com.mycomp.myapp I/MultiDex: Installing application
03-23 02:52:40.233 22752-22752/com.mycomp.myapp I/MultiDex: VM has multidex support, MultiDex support library is disabled.
03-23 02:52:40.243 22752-22773/com.mycomp.myapp V/StudioProfiler: Acquiring Application for Events
03-23 02:52:40.253 22752-22752/com.mycomp.myapp W/ComponentDiscovery: Class com.google.firebase.dynamicloading.DynamicLoadingRegistrar is not an found.
03-23 02:52:40.263 22752-22752/com.mycomp.myapp I/FirebaseApp: Device unlocked: initializing all Firebase APIs for app [DEFAULT]
03-23 02:52:40.283 22752-22752/com.mycomp.myapp I/FirebaseCrashlytics: Initializing Firebase Crashlytics 17.4.0
03-23 02:52:40.323 22752-22778/com.mycomp.myapp I/DynamiteModule: Considering local module com.google.android.gms.measurement.dynamite:46 and remote module com.google.android.gms.measurement.dynamite:46
03-23 02:52:40.323 22752-22778/com.mycomp.myapp I/DynamiteModule: Selected remote version of com.google.android.gms.measurement.dynamite, version >= 46
03-23 02:52:40.323 22752-22778/com.mycomp.myapp V/DynamiteModule: Dynamite loader version >= 2, using loadModule2NoCrashUtils
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.google.android.gms-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 67, previously 69
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 5556, previously 5557
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 67, previously 69
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 5556, previously 5557
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 67, previously 69
03-23 02:52:40.333 22752-22778/com.mycomp.myapp W/ResourceType: ResTable_typeSpec entry count inconsistent: given 5556, previously 5557
03-23 02:52:40.363 22752-22778/com.mycomp.myapp W/System: ClassLoader referenced unknown path: /data/data/com.google.android.gms/app_chimera/m/00000046/n/armeabi-v7a
03-23 02:52:40.363 22752-22778/com.mycomp.myapp W/System: ClassLoader referenced unknown path: /data/data/com.google.android.gms/app_chimera/m/00000046/n/armeabi
03-23 02:52:40.363 22752-22778/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000046/MeasurementDynamite.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.363 22752-22778/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000046/MeasurementDynamite.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.393 22752-22752/com.mycomp.myapp I/FirebaseInitProvider: FirebaseApp initialization successful
03-23 02:52:40.403 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.423 22752-22794/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.google.android.gms-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.453 22752-22794/com.mycomp.myapp I/DynamiteModule: Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:210402101
03-23 02:52:40.453 22752-22794/com.mycomp.myapp I/DynamiteModule: Selected remote version of com.google.android.gms.ads.dynamite, version >= 210402101
03-23 02:52:40.453 22752-22794/com.mycomp.myapp V/DynamiteModule: Dynamite loader version >= 2, using loadModule2NoCrashUtils
03-23 02:52:40.463 22752-22794/com.mycomp.myapp W/System: ClassLoader referenced unknown path: /data/data/com.google.android.gms/app_chimera/m/00000047/n/armeabi-v7a
03-23 02:52:40.463 22752-22794/com.mycomp.myapp W/System: ClassLoader referenced unknown path: /data/data/com.google.android.gms/app_chimera/m/00000047/n/armeabi
03-23 02:52:40.473 22752-22794/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000047/dl-AdsFdrDynamite.integ_210402101000000.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.473 22752-22794/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000047/dl-AdsFdrDynamite.integ_210402101000000.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.513 22752-22791/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.513 22752-22791/com.mycomp.myapp V/FA: App measurement collection enabled
03-23 02:52:40.523 22752-22791/com.mycomp.myapp V/FA: App measurement enabled for app package, google app id: com.mycomp.myapp, 1:138510249478:android:6ae0d41a5c3161e4
03-23 02:52:40.523 22752-22791/com.mycomp.myapp I/FA: App measurement initialized, version: 39015
03-23 02:52:40.523 22752-22791/com.mycomp.myapp I/FA: To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
03-23 02:52:40.523 22752-22791/com.mycomp.myapp I/FA: To enable faster debug mode event logging run:
      adb shell setprop debug.firebase.analytics.app com.mycomp.myapp
03-23 02:52:40.523 22752-22791/com.mycomp.myapp D/FA: Debug-level message logging enabled
03-23 02:52:40.573 22752-22791/com.mycomp.myapp V/FA: Connecting to remote service
03-23 02:52:40.593 22752-22791/com.mycomp.myapp V/FA: Connection attempt already in progress
03-23 02:52:40.603 22752-22791/com.mycomp.myapp V/FA: Connection attempt already in progress
03-23 02:52:40.643 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.653 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.663 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.mycomp.myapp-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.683 22752-22752/com.mycomp.myapp D/SecWifiDisplayUtil: Metadata value : none
03-23 02:52:40.733 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.google.android.gms-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.803 22752-22752/com.mycomp.myapp I/DynamiteModule: Considering local module com.google.android.gms.ads.dynamite:0 and remote module com.google.android.gms.ads.dynamite:210402101
03-23 02:52:40.803 22752-22752/com.mycomp.myapp I/DynamiteModule: Selected remote version of com.google.android.gms.ads.dynamite, version >= 210402101
03-23 02:52:40.803 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/data/com.google.android.gms/app_chimera/m/00000047/dl-AdsFdrDynamite.integ_210402101000000.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.803 22752-22752/com.mycomp.myapp D/DynamitePackage: Instantiated singleton DynamitePackage.
03-23 02:52:40.803 22752-22752/com.mycomp.myapp D/DynamitePackage: Instantiating com.google.android.gms.ads.ChimeraMobileAdsSettingManagerCreatorImpl
03-23 02:52:40.843 22752-22752/com.mycomp.myapp I/Ads: Updating ad debug logging enablement.
03-23 02:52:40.873 22752-22752/com.mycomp.myapp I/WebViewFactory: Loading com.google.android.webview version 89.0.4389.90 (code 438909000)
03-23 02:52:40.923 22752-22752/com.mycomp.myapp W/ResourcesManager: getTopLevelResources: /data/app/com.google.android.webview-1/base.apk / 1.0 running in com.mycomp.myapp rsrc of package null
03-23 02:52:40.933 22752-22752/com.mycomp.myapp W/ResourceType: Found multiple library tables, ignoring...
03-23 02:52:40.933 22752-22752/com.mycomp.myapp W/ResourceType: Found multiple library tables, ignoring...
03-23 02:52:40.973 22752-22822/com.mycomp.myapp W/System.err: mkdir failed: EEXIST (File exists) : /data/user/0/com.mycomp.myapp/cache/WebView
03-23 02:52:41.043 22752-22752/com.mycomp.myapp I/cr_LibraryLoader: Loaded native library version number "89.0.4389.90"
03-23 02:52:41.053 22752-22752/com.mycomp.myapp I/cr_CachingUmaRecorder: Flushed 4 samples from 4 histograms.
03-23 02:52:43.193 22752-22752/com.mycomp.myapp A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 22752 (re.myapp)

-------
It looks like you are making some changes in remote configurations of ads.
Please undo these changes.

Alexander VI

unread,
Mar 22, 2021, 11:22:12 PM3/22/21
to Google Mobile Ads SDK Developers
Correction: This started on March 22nd.  

вторник, 23 марта 2021 г. в 05:16:05 UTC+2, Alexander VI:

Heberth Vargas

unread,
Mar 23, 2021, 12:11:20 AM3/23/21
to Google Mobile Ads SDK Developers
i have a problem similar

backtrace: #00 pc 0000000002919eba /data/app/com.google.android.trichromelibrary_438909030-WfCQunfzwxdl6uLhNMj6QQ==/base.apk!libmonochrome.so (offset 0x645000)

with many diffferent devices with android 10 
but i have other similar errors with other android versions
this is a error for android 7.1
backtrace: #00 pc 0000000002919eba /data/app/com.android.chrome-2/base.apk (offset 0xb09000)

this for android 8.1
backtrace: #00 pc 0000000000280eba /data/app/com.android.chrome-3NAND_Q9CZtYifDHk2jvMw==/base.apk (offset 0x31a2000) #00 pc 00000000006f5b9d /data/app/com.android.chrome-3NAND_Q9CZtYifDHk2jvMw==/base.apk (offset 0x20d5000)

also i have this error for android 11 
java.lang.RuntimeException: at android.app.ActivityThread.performDestroyActivity (ActivityThread.java:5566) at android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:5605) at android.app.servertransaction.DestroyActivityItem.execute (DestroyActivityItem.java:44) at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176) at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2278) at android.os.Handler.dispatchMessage (Handler.java:106) at android.os.Looper.loop (Looper.java:246) at android.app.ActivityThread.main (ActivityThread.java:8430) at java.lang.reflect.Method.invoke (Method.java) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:596) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1130) Caused by: java.lang.NullPointerException: at com.google.android.gms.ads.internal.overlay.l.v (l.java:2) at com.google.android.gms.ads.internal.overlay.l.u (l.java:7) at com.google.android.gms.ads.internal.overlay.l.l (l.java:2) at com.google.android.gms.ads.internal.overlay.client.b.bA (b.java:11) at gd.onTransact (gd.java:4) at android.os.Binder.transact (Binder.java:1079) at com.google.android.gms.internal.ads.zzgw.zzb (zzgw.java:7) at com.google.android.gms.internal.ads.zzarq.onDestroy (zzarq.java:6) at com.google.android.gms.ads.AdActivity.onDestroy (AdActivity.java:4) at android.app.Activity.performDestroy (Activity.java:8432) at android.app.Instrumentation.callActivityOnDestroy (Instrumentation.java:1344) at android.app.ActivityThread.performDestroyActivity (ActivityThread.java:5551) at android.app.ActivityThread.handleDestroyActivity (ActivityThread.java:5605) at android.app.servertransaction.DestroyActivityItem.execute (DestroyActivityItem.java:44) at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176) at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2278) at android.os.Handler.dispatchMessage (Handler.java:106) at android.os.Looper.loop (Looper.java:246) at android.app.ActivityThread.main (ActivityThread.java:8430) at java.lang.reflect.Method.invoke (Method.java) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:596) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1130)






the error started when i update the code for ads and i changed the depreccated InterstitialAd  and i used the new load method of InterstitialAd

John Doe

unread,
Mar 23, 2021, 1:05:20 AM3/23/21
to Google Mobile Ads SDK Developers
I want to upvote this. Crash happens in this line and commenting it fixes it.

MobileAds.initialize(getApplicationContext());

It is some kind of remote config. I woke up to see 3 of 8 games not starting. 2 hours later all 8 are affected. Please, roll back whatever changes you made. You basically ruined all our Apps (

AbSoft

unread,
Mar 23, 2021, 1:28:08 AM3/23/21
to Google Mobile Ads SDK Developers
Hi All,

the exact same crash log also happens in our app :
#00 pc 00000000034529dc /data/app/com.google.android.webview-4jRbuzYvPiIwCw4l3p_lXg==/base.apk!libmonochrome.so (offset 0x2d3000) 
A huge spike in crashes occurred since March 23th morning in our time.

we updated our app last week with "com.google.android.gms:play-services-ads:19.7.0" version and changed the deprecated Interstitial ads code.

@John Doe, if you commenting MobileAds.initialize(getApplicationContext()), does your app still serve ads ? is that init code not mandatory ?

Thanks you

John Doe

unread,
Mar 23, 2021, 1:42:19 AM3/23/21
to Google Mobile Ads SDK Developers
No, ads are not shown, at least on the phone affected (looks like it was a staged rollout after all). But it would save us from crashes and 1 star reviews.

Henrik Hagström

unread,
Mar 23, 2021, 2:14:47 AM3/23/21
to Google Mobile Ads SDK Developers
Hello

Same issue here, I noticed it first time around 9 hours ago:
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 8497

I can not even run my app in debug mode, becoming an urgent issue fast for many users, problem seems to be related to MobileAds.initialize
I also upgraded to com.google.android.gms:play-services-ads:19.7.0 yesterday.

/Henrik

John Doe

unread,
Mar 23, 2021, 2:39:49 AM3/23/21
to Google Mobile Ads SDK Developers
It does not look like 19.7 is a problem. The games with 19.3.0 are still affected.

More info - clearing app's data fixes it. Closing the game and reopening works. But force-closing the game by swiping it from the recent apps brings up the problem on the next start.

Message has been deleted

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 23, 2021, 3:49:11 AM3/23/21
to google-adm...@googlegroups.com

Hi All,

Thank you for reaching out to us.

Regard to this, the only way for us to investigate this is for you to provide us the captured Charles log that reproducing this issue.

With that, could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com?

Regards,

Google Logo
Princess Pamela Pineda
Mobile Ads SDK Team
 


ref:_00D1U1174p._5004Q2DxwuM:ref

John Doe

unread,
Mar 23, 2021, 5:26:58 AM3/23/21
to Google Mobile Ads SDK Developers
Sample project is not needed. Opening Phone's Settings\General\Google results in that crash.

2021-03-23 12:25:01.135 22656-22656/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 22656 (.android.gms.ui)
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: Build fingerprint: 'lge/judyln_lao_ru/judyln:8.0.0/OPR1.170623.032/182621450704d.FGN.RU:user/release-keys'
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: Revision: '12'
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: ABI: 'arm64'
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: pid: 22656, tid: 22656, name: .android.gms.ui  >>> com.google.android.gms.ui <<<
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG: Cause: null pointer dereference
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x0   0000000000000000  x1   0000007a659f61ec  x2   7265646f63654400  x3   726f7463656c6553
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x4   0000000000000000  x5   0000000000000000  x6   716e7362646b6452  x7   7f7f7f7f7f7f7f7f
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x8   0101010101010101  x9   0000007a65753000  x10  0000007400027488  x11  0000000000000140
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x12  0000000000000001  x13  0000000000000000  x14  4b3d092f234ec266  x15  cae6c696f68e9634
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x16  0000007a69a9c0f0  x17  0000007a8871e9d0  x18  0000007a86cab000  x19  0000000000000003
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x20  0000000000000000  x21  000000740001fd40  x22  0000007fc358a058  x23  0000007400027488
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x24  0000007400027498  x25  0000000000000000  x26  0000007fc358a2f0  x27  0000000000000000
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     x28  00000074000b8270  x29  0000007fc3589fb0  x30  0000007a68a279dc
2021-03-23 12:25:01.218 22976-22976/? A/DEBUG:     sp   0000007fc3589f80  pc   0000007a68a279dc  pstate 0000000080000000
2021-03-23 12:25:01.219 22976-22976/? A/DEBUG: backtrace:
2021-03-23 12:25:01.219 22976-22976/? A/DEBUG:     #00 pc 00000000034529dc  /data/app/com.android.chrome-f05T-AOIXBzoxAXvdgwGUw==/base.apk (offset 0xa0f000)
2021-03-23 12:25:01.873 1377-1377/? E//system/bin/tombstoned: Tombstone written to: /data/tombstones//tombstone_06
Message has been deleted

ark.t...@gmail.com

unread,
Mar 23, 2021, 9:34:36 AM3/23/21
to Google Mobile Ads SDK Developers
Hi all. Isn't it related to the WebView failed update? Just search Google for "WebView crashing apps", there will be a ton of articles. My app got a lot of 1-star reviews because of it. Users who followed my instructions and updated WebView reported that it helped.

On Tuesday, March 23, 2021 at 2:29:23 PM UTC+1 Dmitry wrote:
Good day! Dears, how soon will the problem be resolved? The failures started on the evening of the previous day, i.e. about 18 hours ago. There is still no solution from the admob. The number of crashes is huge, the user experience is dropping. Is it worth releasing a minipatch by disabling ads, or will the team solve the problem today? Due to the fact that global changes on the side affected all versions of the SDK (maybe a couple of recent versions) at once, the developers do not even have the opportunity to roll back to the previous version.

вторник, 23 марта 2021 г. в 12:26:58 UTC+3, John Doe:
Message has been deleted

ark.t...@gmail.com

unread,
Mar 23, 2021, 9:45:25 AM3/23/21
to Google Mobile Ads SDK Developers
Users want their apps working. Updating WebView seems to fix it. For most users their devices will automatically update the fixed WebView version and apps will work again. Unfortunately our apps will lose many users and get many 1* reviews until then.

On Tuesday, March 23, 2021 at 2:42:19 PM UTC+1 Dmitry wrote:
Right. But a massive problem appeared at approximately 22.00 GMT +03.00, before that it had not existed. That is, something was changed on the other side. Because of this, forcing users to update something is not correct. Most of the audience will not do this, but will simply put 1 star and remove the application.

вторник, 23 марта 2021 г. в 16:34:36 UTC+3, ark.t...@gmail.com:

John Doe

unread,
Mar 23, 2021, 10:00:35 AM3/23/21
to Google Mobile Ads SDK Developers
Update According to this article, I tried updating both Android System Webview and Google Chrome (actually already had the latest WebView, so needed to update only Chrome) and it resolved this problem in all the games and apps at once...

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 23, 2021, 10:28:15 AM3/23/21
to spade...@gmail.com, google-adm...@googlegroups.com
Hi All,

Thank you for bringing this issue to our attention.I know I have spoken with John Doe. And it appears that this issue is not due to the SDK. While there is the question about the initializer() it does not appear to be anything else that is doing this from the SDK. 

As for the initializer() with the newest SDK version it is no longer needed to have that method in the app to start calling the ads. As you can see with the newest documents prepping for v20 that the apps no longer will be calling this. Instead it will be placed in the manifest.

Regards,
Google Logo
William Pescherine
Mobile Ads SDK Team
 


ref:_00D1U1174p._5004Q2DxwuM:ref

Eddy

unread,
Mar 23, 2021, 12:51:54 PM3/23/21
to Google Mobile Ads SDK Developers

So is the issue considered solved ? We have dozens of thousands of crashes and it doesn't seem to be going down. Any workaround besides disabling Admob altogether ?

Thanks
Eddy

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 23, 2021, 5:36:58 PM3/23/21
to blazz.a...@gmail.com, google-adm...@googlegroups.com
Hi All,

We want to thank everyone for your patience as well as your help with this issue. It is something we are aware of and our team is looking into this. Know that this has to do with an Android 11 patch that was pushed live yesterday. It is strongly recommended that you check out this post. As there is more help there as well as it is being watched closer by our team.

It is suggested right now to clear cache as the workaround for now.

Vladislav Haralampiev

unread,
Mar 24, 2021, 6:53:33 AM3/24/21
to Google Mobile Ads SDK Developers
The issue you mentioned (from this post) happens only on Android 11, right? The one from this thread happens also on other Android versions. For sure I have seen it on Android 10 and Android 8. And the crashes continue today.

By the way, I think the same problem was affecting GMail. According to their Service details page the issue is resolved. Do you have an idea how they resolved it --- users need to update Chrome and WebView and that's it?

D P

unread,
Mar 24, 2021, 9:10:48 AM3/24/21
to Google Mobile Ads SDK Developers
Is there a compensation scheme for lost users / revenue and negative reviews caused by these issues  which are out of our control?

ark.t...@gmail.com

unread,
Mar 24, 2021, 9:12:52 AM3/24/21
to Google Mobile Ads SDK Developers
@Vladislav, updating WebView and/or Chrome helped users of my app with this bug.

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 24, 2021, 10:10:26 AM3/24/21
to vladislav....@gmail.com, google-adm...@googlegroups.com
Hi Vladislav,

Thank you for the response back. From what I have seen. It would appear that clearing the cache and a few other changes to the settings as posted in the other thread as you have stated should help to resolve this. But one of the biggest things to know, is that this is not an AdMob SDK issue. I would suggest also looking into the Android developer forums. As this is a higher level issue not related to AdMob.

INDOGAMING

unread,
Mar 24, 2021, 10:16:41 AM3/24/21
to Mobile Ads SDK Forum Advisor Prod, vladislav....@gmail.com, google-adm...@googlegroups.com
Ok

--

---
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/SjMeE000000000000000000000000000000000000000000000QQH8OM00V6nrfCE_QzWvch3mfLvZ6Q%40sfdc.net.

Vladislav Haralampiev

unread,
Mar 24, 2021, 3:29:12 PM3/24/21
to Google Mobile Ads SDK Developers
Thank you for the information. @mobileadssdkforumadvisor --- yes, I agree that the problem is not directly caused by the AdMob SDK. But, at least for the future, maybe you can consider doing something about the crashing WebView problem. I think that you can override onRenderProcessGone of the WebView to avoid crashing the whole app if the WebView itself crashes. In onRenderProcessGone you can either try to recover AdMob after some timeout (or just stop calling WebView methods, stop the ads etc.). WebView crashes were also happening in the past --- they were happening rarely, but still, sometimes we were seeing crashes of this type (often because of a corrupted ad). Detecting problems of this type sounds as a good improvement for the stability of AdMob SDK.

Cihan

unread,
Mar 24, 2021, 5:28:47 PM3/24/21
to Google Mobile Ads SDK Developers
I have the same issue, my app cannot be open anymore all of a sudden because of this crash. The only thing I can tell to my users is to update Android System Webview. I lost tons of users and got many 1 stars.....

Mobile Ads SDK Forum Advisor Prod

unread,
Mar 25, 2021, 2:26:56 AM3/25/21
to cihant...@gmail.com, google-adm...@googlegroups.com

Hi All,

Thank you for reaching out to us.

I know how frustrating it can be and as much as we would want to assists you on this. I'm afraid that this is already out of our expertise. What we can offer now is that you post this to other developer forum like StackOverflow. We hope that you get a positive response from them the soonest time possible.

Regards,

Google Logo
Princess Pamela Pineda
Mobile Ads SDK Team
 


ref:_00D1U1174p._5004Q2DxwuM:ref
Reply all
Reply to author
Forward
0 new messages