Native AdMob: IllegalStateException: Too many receivers, total of 1000

[FRIST 008]

I get this kind of log on crashlytics.

    Fatal Exception: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 3244, callerPackage: com.nda.nda

       at android.os.Parcel.createException(Parcel.java:1974)

       at android.os.Parcel.readException(Parcel.java:1934)

       at android.os.Parcel.readException(Parcel.java:1884)

       at android.app.IActivityManager$Stub$Proxy.registerReceiver(IActivityManager.java:3690)

       at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1567)

       at android.app.ContextImpl.registerReceiver(ContextImpl.java:1528)

       at android.app.ContextImpl.registerReceiver(ContextImpl.java:1516)

       at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:636)

       at com.google.android.gms.ads.internal.util.br.a(br.java:7)

       at com.google.android.gms.ads.internal.activeview.ac.a(ac.java:6)

       at com.google.android.gms.ads.internal.activeview.ac.<init>(ac.java:8)

       at com.google.android.gms.ads.nonagon.ad.event.ei.a(ei.java:1)

       at com.google.android.gms.ads.nonagon.ad.nativead.p.a(p.java:79)

       at com.google.android.gms.ads.nonagon.ad.nativead.ag.a(ag.java:27)

       at com.google.android.gms.ads.nonagon.ad.nativead.bf.a(bf.java:15)

       at com.google.android.gms.ads.internal.formats.client.k.a(k.java:25)

       at fv.onTransact(fv.java:4)

       at android.os.Binder.transact(Binder.java:675)

       at com.google.android.gms.internal.ads.zzgu.zza(zzgu.java:21)

       at com.google.android.gms.internal.ads.zzaec.zza(zzaec.java:16)

       at com.google.android.gms.ads.formats.UnifiedNativeAdView.setNativeAd(UnifiedNativeAdView.java:52)

[FRIST 008]

version library implementation("com.google.firebase:firebase-ads19.3.0")

понедельник, 17 августа 2020 г. в 06:35:26 UTC+3, FRIST 008:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for reaching out to us.

Could you kindly provide the details below (via Reply privately to author) so that I can investigate the issue?

• Device names and Android versions of devices affected
• Copy of a sample project (replicating the issue)
• Steps to reproduce the issue

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23KhHZ:ref

[FRIST 008]

Reply privately to author  - disable for me...

1. Last Device: Android 9 Samsung Galaxy S8+ Portrait. 1.1 RAM free  and 8.02 GB free storage.

2. https://gist.github.com/frist008/6dc725da92d343dc01c3c8b0d153a2d9 You don't have clear guidelines for updating native ads. And I didn't find them on the internet. But this method turned out to be working. The crash started happening after I added a native ad update. row 36

3. I don't know. This log from crashlytics.

crash in row 26.

I have got 1 crash every week for 2k users online every day. Now 3 crashes for this month. Only for Samsung devices.

понедельник, 17 августа 2020 г. в 09:39:53 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi Frist 008,

Thank you for the additional information. I work along with Ziv. And will be helping you today with this issue.

Having looked over the previous conversation and checking out your code. I would make a few suggestions.

• There should be no need to refresh the Native Ad as the internal system itself does that. This would appear to be causing some conflict.

As this looks to be something related to firebase we normal do not support that. But I will be bringing this to my team to have them look more into this. To see if we can get any feedback regarding this.

Regards,
William Pescherine

[FRIST 008]

"internal system itself does that" Oo. Realy?

Your documentation https://support.google.com/admob/answer/3245199?hl=en says that "Refresh rate is disabled by default for native ads". This is true because I checked.

If you look at the test ad for more than five minutes, nothing happens. I think you need to write a sample project with an example of how to work correctly with native ads that are being updated. Otherwise, the community can make code like the one I sent.

Try Google search: android AdMob native ads refresh

There is practically no material. No verified answers.

понедельник, 17 августа 2020 г. в 20:43:02 UTC+3, mobileadssdkforumadvisor:

[FRIST 008]

Today report:  samsung  Android 10 Galaxy A71    Portrait  1.47 GB  RAM free  73.89 GB  storage free 

    Fatal Exception: java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 12941, callerPackage: com.***.***

       at android.os.Parcel.createException(Parcel.java:2096)

       at android.os.Parcel.readException(Parcel.java:2056)

       at android.os.Parcel.readException(Parcel.java:2004)

       at android.app.IActivityManager$Stub$Proxy.registerReceiver(IActivityManager.java:5488)

       at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1588)

       at android.app.ContextImpl.registerReceiver(ContextImpl.java:1549)

       at android.app.ContextImpl.registerReceiver(ContextImpl.java:1537)

       at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:641)

       at com.google.android.gms.ads.internal.util.br.a(br.java:7)

       at com.google.android.gms.ads.internal.activeview.ac.a(ac.java:6)

       at com.google.android.gms.ads.internal.activeview.ac.<init>(ac.java:7)

       at com.google.android.gms.ads.nonagon.ad.event.ei.a(ei.java:1)

       at com.google.android.gms.ads.nonagon.ad.nativead.p.a(p.java:75)

       at com.google.android.gms.ads.nonagon.ad.nativead.ag.a(ag.java:28)

       at com.google.android.gms.ads.nonagon.ad.nativead.bf.a(bf.java:16)

       at com.google.android.gms.ads.internal.formats.client.k.a(k.java:25)

       at fx.onTransact(fx.java:4)

       at android.os.Binder.transact(Binder.java:914)

       at com.google.android.gms.internal.ads.zzgu.zza(zzgu.java:21)

       at com.google.android.gms.internal.ads.zzaec.zza(zzaec.java:16)

       at com.google.android.gms.ads.formats.UnifiedNativeAdView.setNativeAd(UnifiedNativeAdView.java:52)

    Caused by android.os.RemoteException: Remote stack trace:

at com.android.server.am.ActivityManagerService.registerReceiver(ActivityManagerService.java:16576)

at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2217)

at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:3326)

at android.os.Binder.execTransactInternal(Binder.java:1021)

at android.os.Binder.execTransact(Binder.java:994)

вторник, 18 августа 2020 г. в 09:44:46 UTC+3, FRIST 008:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Kindly provide the details below (via a private email to mobileads...@gmail.com) so that we can investigate this issue:

• Copy of a sample project (replicating the issue); code snippets are insufficient

• Steps to reproduce the issue

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23KhHZ:ref

[FRIST 008]

I cannot reproduce the problem with Crashlytics...

четверг, 20 августа 2020 г. в 05:31:08 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

I'm afraid that we will be needing a sample project (replicating this issue) in order to proceed with the investigation. Feel free to reach out to us (via a private email) once you are able to acquire one.

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23KhHZ:ref

[FRIST 008]

https://github.com/frist008/nativeadmobtoomanyreceiverstotalof1000  I added this email to the sample repository and sent an email to this email. 

четверг, 20 августа 2020 г. в 12:31:44 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi FRIST 008,

Thank you for sending us the links. I have looked into them. But unfortunately I am unable to access the files as I get a 404 when clicking on the links that you sent to that email address.

Could you kindly resend it so that we can look further into this for you.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q23KhHZ:ref

[FRIST 008]

You must use a GitHub account that is depend to the email you provided above.

понедельник, 24 августа 2020 г. в 19:05:44 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi FRIST 008,

Thank you for the link. I will need to bring this to my team so that we can gain access to the project. Once we gain access we will review this and if needed contact you back and see what we can do to help you.

[fris...@gmail.com]

The bug is still being reproduced.

понедельник, 24 августа 2020 г. в 21:13:50 UTC+3, mobileadssdkforumadvisor:

[jo...@fm-games.com]

Have had the same error as well. The way I solved it was by disabling the mopub adapter for my app. (Apparently the mopub adapter has some issue). 
One of the things I noticed by using the test mediation suite is that if you load an ad from mopub and go back you get a leaked register receiver error on the adb. 
Maybe you can try out your own ad units and check if one of them has a log like that and disable the specific one. 
Unfortunately haven't found a way to fix this (other than totally disable the specific ad unit). 

John

[fris...@gmail.com]

I am not using mopub or other middlemen.

четверг, 19 ноября 2020 г. в 17:18:53 UTC+2, jo...@fm-games.com: