[Android] feature request for ANR reduction

[Igor]

Hi.

  We are using AdMob for ads mediation and we used to have hight ANR level. A month ago we've updated our Ads SDKs for the latest and ANR level jumped above the threshold. For some reason downgrading SDKs doesn't help enough. We suspect that broken creative can be the reason, since a lot of ANR callstacks in crashlytics (and crashlytics logs) look like we experience issues during the ad load.

  Is it possible you add an additional callback to your SDK which will let us know which ad network/creative id is going to be loaded and which is called just before the actual ad loading process is started?

  This will help us to identify faulty ad networks and broken ad creatives as well. We need this for android only.

[Mobile Ads SDK Forum Advisor]

Hi Igor,

Thanks for reaching out.

You can use these guides to check which ad network adapter class loaded the ad. Additionally, these callbacks are available for you to use:

• Banner: https://developers.google.com/admob/android/banner#ad_events
• Interstitial: https://developers.google.com/admob/android/interstitial#set_the_fullscreencontentcallback
• Rewarded: https://developers.google.com/admob/android/rewarded#set_the_fullscreencontentcallback

Regards,

Chris

ref:_00D1U1174p._5004Q2aQK3G:ref

[Igor]

Hi Chris.

  we need a way to get this information before the ad is loaded, not after. We need this to be able to log the ad data to crashlytics before ANR happens, so that we see it in ANR report.

[Mobile Ads SDK Forum Advisor]

Hi Igor,

 

Currently we do not support getting the creative information before the ad is loaded. You can use the `getResponseID()` API to retrieve the ad response ID (after the ad is loaded), then identify the creative in the Ads Review Center with that ID.

Regards,

Chris

 

ref:_00D1U1174p._5004Q2aQK3G:ref

[Igor Lobanchikov]

Hi Chris.

  I understand that you don't have this functionality. That's why this thread is called "feature request for ANR reduction". We  need to trace ANR reasons in the Crashlytics console. There are high chances that quite a few ANRs happen during the ad loading process. In order to be able to prove/disprove this we need ad load start/end events. In order to identify a broken ad we need the ad id for load start event. It's not enough to have only the ad finish event: if ANR happens Crashlytics sends a log with events registered _before_ ANR happens.

  Please, note that AdMob introduces an unacceptably high amount of ANRs into our project. If we won't be able to trace them down in a few weeks and go below the threshold, our management wants us to switch to the more developer-friendly solutions which are used on our other projects. We are also considering removing AdMob completely from all waterfalls. It is absolutely unacceptable that AdMob ruins our application. I know that you guys didn't move a finger to address this issue -- lots of reports were, lots of complaints all over the internet -- for more than two years already and even made things worse every few months, so, please, just add minor helpers to allow us to fix at least some of the issues ourselves.

Regards,

Igor.

[Mobile Ads SDK Forum Advisor]

Hi Igor,


Thank you for the clarification.

There will be a new Android release with the ANR fix coming in ~2 weeks.

In the meantime, we will certainly look at your request.