AdMob Android AdListener failure

[Chris Barrett]

Hi

I have a bug in my AdMob implementation that I've also been able to replicate in the basic AdMob BannerExample Android app.
The only modifications I've made the example app (see Dropbox link) are to add in the AdListener code from the "Ad events" section here: https://developers.google.com/admob/android/banner#ad_events

If a user taps a banner advert, all the AdListener events are called as expected. However, if the user taps the *same* banner a second time, only the adOpened event is called. AdClosed is not called.
We have code that depends on this being called to resume exection of our apps' game loop. Once a new banner loads, adOpened/Closed will be called on the first tap, but not on subsequent taps.
Here's the logcat for those events:

2023-09-29 10:46:50.874  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdImpression
2023-09-29 10:46:50.875  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdLoaded
2023-09-29 10:47:00.777  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdOpened
2023-09-29 10:47:03.954  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdClosed
2023-09-29 10:47:06.378  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdOpened <<
2023-09-29 10:48:01.740  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdImpression
2023-09-29 10:48:01.741  6573-6573  AdMobBannerExample      com...oid.gms.example.bannerexample  V  onAdLoaded

Note after the second onAdOpened, there's no matching onAdClosed.
I've seen this consistently across a number of devices and Android versions.

I appreciate this is rather edge case behaviour, but is it something I've done wrong or is it an AdMob bug? Should I be forcing the banner to reload after the first onAdClosed event?

Any advice greatly appreciated

Chris

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Upon reviewing your concern, I understand that you have encountered an AdMob Android AdListener failure. 

I will check with our team regarding your issue and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

This message is in relation to case "ref:_00D1U1174p._5004Q2p2QbO:ref"

Thanks,
 

Mobile Ads SDK Team

[Chris Barrett]

Hi!

Any update on this please?

Many thanks

Chris

[Mobile Ads SDK Forum Advisor]

Hi Chris,

Your concern is still under investigation and we have no updates at the moment. However, allow me to follow up on this with the rest of the team. Thank you for your patience.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02p2QbO:ref"

Thanks,
 

Mobile Ads SDK Team

[Chris Barrett]

Sorry to pester, is this still being investigated?

Many thanks

[Mobile Ads SDK Forum Advisor]

Hi Chris,

We regret the inconvenience caused. Your concern is still under investigation and we have no updates at the moment. Thank you for your patience.

 

[Mobile Ads SDK Forum Advisor]

Hi Chris,

I have confirmed the issue and will request this is fixed. In the meantime I suggest you leverage activity/application pause and resume as a workaround. Pause and Resume would be a better choice even without the fix considering onAdOpened and onAdClosed will be called by both on screen overlays and click navigations and there may be additional issues if bind game play and game pause code to these events.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02p2QbO:ref" (ADR-00200742)

Thanks,
 

Nicholas Ventimiglia Mobile Ads SDK Team