SCREEN_OFF/ConcurrentModificationException crash

[kmi...@gmail.com]

Hello,

I'm seeing this crash, that probably related to Ads SDK:

Fatal Exception: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.SCREEN_OFF flg=0x50200010 (has extras) } in com.google.android.gms.ads.internal.util.bw@9930524

       at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1493)

       at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(-.java:2)

       at android.os.Handler.handleCallback(Handler.java:873)

       at android.os.Handler.dispatchMessage(Handler.java:99)

       at android.os.Looper.loop(Looper.java:214)

       at android.app.ActivityThread.main(ActivityThread.java:7045)

       at java.lang.reflect.Method.invoke(Method.java)

       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)

Caused by java.util.ConcurrentModificationException

       at java.util.WeakHashMap$HashIterator.nextEntry(WeakHashMap.java:806)

       at java.util.WeakHashMap$EntryIterator.next(WeakHashMap.java:845)

       at java.util.WeakHashMap$EntryIterator.next(WeakHashMap.java:843)

       at com.google.android.gms.ads.internal.util.bv.a(bv.java:9)

       at com.google.android.gms.ads.internal.util.bw.onReceive(bw.java:2)

       at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0(LoadedApk.java:1483)

       at android.app.-$$Lambda$LoadedApk$ReceiverDispatcher$Args$_BumDX2UKsnxLVrE6UJsJZkotuA.run(-.java:2)

       at android.os.Handler.handleCallback(Handler.java:873)

       at android.os.Handler.dispatchMessage(Handler.java:99)

       at android.os.Looper.loop(Looper.java:214)

       at android.app.ActivityThread.main(ActivityThread.java:7045)

       at java.lang.reflect.Method.invoke(Method.java)

       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)

This started happening on April 11 in several versions of the app:

I see that this error was also reported on stackoverflow: https://stackoverflow.com/questions/55819985/weird-exception-only-in-1-user

I use the following play-services libs versions:

implementation "com.google.android.gms:play-services-location:16.0.0"
implementation "com.google.android.gms:play-services-maps:16.1.0"
implementation "com.google.android.gms:play-services-ads:17.1.3"
implementation "com.google.android.gms:play-services-oss-licenses:16.0.2"

If anybody has a clue how to workaround this please let me know.

[mobileadssdk...@google.com]

Hello there,

Thanks for reaching out to us. Are you able to reproduce the issue locally? Please send us the complete crash logs/ crashlytics links for us to take a look.

Regards,

Deepika Uragayala

Mobile Ads SDK Team

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/93565b4c-88ea-48b1-a476-304ce2c1257b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tomate Chines]

I'm having this issue either, not able to reproduce in dev only happening in production

Caused by java.lang.IllegalArgumentException: View=com.google.firebase.inappmessaging.display.internal.layout.FiamRelativeLayout{d3cfaf1 V.E...... ......ID 0,0-1080,0 #7f0900be app:id/modal_root} not attached to window manager
       at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:555)
       at android.view.WindowManagerGlobal.removeView(WindowManagerGlobal.java:436)
       at android.view.WindowManagerImpl.removeViewImmediate(WindowManagerImpl.java:132)
       at com.google.firebase.inappmessaging.display.internal.FiamWindowManager.destroy(FiamWindowManager.java:90)
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay.removeDisplayedFiam(FirebaseInAppMessagingDisplay.java:495)
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay.onActivityPaused(FirebaseInAppMessagingDisplay.java:221)
       at android.app.Application.dispatchActivityPaused(Application.java:249)
       at android.app.Activity.onPause(Activity.java:1739)
       at android.support.v4.app.FragmentActivity.onPause(FragmentActivity.java:470)
       at com.tomatedigital.adinjector.AdsAppCompatActivity.onPause(AdsAppCompatActivity.java:168)
       at com.tomatedigital.giveawaymaster.activity.MainActivity.onPause(MainActivity.java:133)
       at android.app.Activity.performPause(Activity.java:7487)
       at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1416)
       at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4130)
       at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4107)
       at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4081)
       at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4055)
       at android.app.ActivityThread.-wrap16(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1736)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loop(Looper.java:164)
       at android.app.ActivityThread.main(ActivityThread.java:7000)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

[kmi...@gmail.com]

Here's the link to this crash in Firebase: /*hidden*/

I'm not able to reproduce it locally, just observing that it started to happen without any action from our side.

Thanks,

Kirill

[mobileadssdk...@google.com]

Hello there,

Thanks for getting back to us. Can you please confirm that you are also seeing this issue with the latest version of the SDK? 

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/02/19 04:52:34 kmi...@gmail.com wrote:

Here's the link to this crash in Firebase: https://console.firebase.google.com/u/1/project/codified.co:api-project-915814917916/crashlytics/app/android:com.codified.hipyard/issues/5cb0ba57f8b88c2963ac03ba?time=last-thirty-days&sessionId=5CC906AE02EE0001396B57106333DB30_DNE_0_v2

To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsubscrib...@googlegroups.com.

To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/93565b4c-88ea-48b1-a476-304ce2c1257b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/d94562c0-708a-4222-aa1e-b672ce7629f5%40googlegroups.com.

[kmi...@gmail.com]

As I already mentioned I use version 17.1.3 of SDK, while the latest one is 17.2.0. But I rarely do a "blind" SDK version update in my projects, because it's often a cause of new crashes/issues, so I prefer to wait for some time until at least bug fixes will be released. 

Can you confirm, that this issue can be potentially fixed in 17.2.0?

On Thursday, May 2, 2019 at 10:32:25 PM UTC+3, mobileadssdk-forumadvisor wrote:

Hello there,

Thanks for getting back to us. Can you please confirm that you are also seeing this issue with the latest version of the SDK? 

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/02/19 04:52:34 kmi...@gmail.com wrote:

Here's the link to this crash in Firebase: /*hidden*/

[mobileadssdk...@google.com]

Hello there,

A fix for this issue has been fixed and rolled out to all the current versions. Can you please confirm the frequency of crashes as of today after updating the SDK to the latest version?

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/03/19 05:24:02 kmi...@gmail.com wrote:

As I already mentioned I use version 17.1.3 of SDK, while the latest one is 17.2.0. But I rarely do a "blind" SDK version update in my projects, because it's often a cause of new crashes/issues, so I prefer to wait for some time until at least bug fixes will be released. 

Can you confirm, that this issue can be potentially fixed in 17.2.0?

On Thursday, May 2, 2019 at 10:32:25 PM UTC+3, mobileadssdk-forumadvisor wrote:

Hello there,

Thanks for getting back to us. Can you please confirm that you are also seeing this issue with the latest version of the SDK? 

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 05/02/19 04:52:34 kmi...@gmail.com wrote:

Here's the link to this crash in Firebase: https://console.firebase.google.com/u/1/project/codified.co:api-project-915814917916/crashlytics/app/android:com.codified.hipyard/issues/5cb0ba57f8b88c2963ac03ba?time=last-thirty-days&sessionId=5CC906AE02EE0001396B57106333DB30_DNE_0_v2

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/d94562c0-708a-4222-aa1e-b672ce7629f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/27def942-5287-46a4-9a0c-379c23327958%40googlegroups.com.

[kmi...@gmail.com]

Hello!

The crash is gone. Thank you very much for such quick support and fix, I appreciate it!

Thanks,

Kirill

Here's the link to this crash in Firebase: /*hidden*/

[Tomate Chines]

What version, of what sdk are you talking about?

play-services-location last update was october 2018

play-services-ads last update was march 2019

[Tomate Chines]

I AM USING THE LASTEST VERSION OF THE SDK AND I DO GET THIS EXCEPTION...

you guys should learn how to test your code

[mobileadssdk...@google.com]

Hello Tomate,

This crash below that you reported is not the same as the crash that is reported on this actual thread. Please open a new thread for better tracking purposes and we will take a look into this again. 

Caused by java.lang.IllegalArgumentException: View=com.google.firebase.inappmessaging.display.internal.layout.FiamRelativeLayout{d3cfaf1 V.E............ID 0,0-1080,0 #7f0900be app:id/modal_root} not attached to window manager

Regards,

Deepika Uragayala
Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/27def942-5287-46a4-9a0c-379c23327958%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

---
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-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/be1a9baf-a8a0-4bc7-a002-48595069e0a5%40googlegroups.com.

[Jean W]

Hello, 

Our app is still facing the same issue with ConcurrentModificationException, we are using 'com.google.android.gms:play-services-ads:17.2.1' and still geting the below crash on google play.

java.util.ConcurrentModificationException:

at java.util.ArrayList$Itr.next (ArrayList.java:831)

at java.util.Collections$UnmodifiableCollection$1.next (Collections.java:1115)

at com.google.android.gms.ads.omid.library.walking.async.g.a (g.java:4)

at com.google.android.gms.ads.omid.library.walking.async.g.onPostExecute (g.java)

at android.os.AsyncTask.finish (AsyncTask.java:660)

at android.os.AsyncTask.-wrap1 (AsyncTask.java)

at android.os.AsyncTask$InternalHandler.handleMessage (AsyncTask.java:677)

at android.os.Handler.dispatchMessage (Handler.java:110)

at android.os.Looper.loop (Looper.java:203)

at android.app.ActivityThread.main (ActivityThread.java:6309)

at java.lang.reflect.Method.invoke (Method.java)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1063)

at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:924)

Thank you.

[Mobile Ads SDK Forum Advisor Prod]

Hi Jean,

Thank you for reaching out to us.

As per checking, this is an issue previously reported by other publisher which the Engineering team is currently working on. I also relayed the information that you provided to them. I'll get back to you for any feedback.

Regards,
Teejay Pimentel
Mobile Ads SDK Team
 

ref:_00D1U1174p._5001UBm0bX:ref