App Open Ads cannot be closed or proceeded after showing

[Vuong Nguyen]

Hello AdMob Support Team,

I’m currently experiencing an issue with App Open Ads in my app. The ad loads and displays successfully, but after it is shown the user cannot proceed — the ad cannot be closed or skipped, and the app does not continue to the next screen. This results in the user being stuck on the ad screen.

This issue happens consistently across multiple devices and Android versions. The problem started recently without any major changes to the ad implementation on my side.

Could you please help check if this is a known issue or provide guidance on how to resolve it?
Thank you for your support.  

[Conrad Cheng]

Hello, we are HK publishers, also suffering the same issue with AOA. Seems iOS and Android have the same outcome

[Abes Yao]

  Same issue here. App Open Ad displays but cannot be closed (loading spinner stays).
No recent SDK updates or integration changes, so it appears to be a platform-side issue.  

On Wednesday, January 7, 2026 at 12:21:59 PM UTC+8 Vuong Nguyen wrote:

[Conrad Cheng]

https://ads.google.com/status/publisher/incidents/TsejQZAyDv4KQQAYypwu

[Artbees Solution]

I’m experiencing the same issue across all of my apps starting today. App Open Ads were working fine yesterday, but now users get stuck on the ad screen and cannot close or proceed.

This is happening consistently on multiple devices.

Please let me know if you find a solution.

[Funprime Testing]

anyone find any solution

[Muhammad Ismail]

Same issue. Would be great to get this issue solved ASAP as user are getting stuck on ad and forced to exit.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for reaching out Mobile Ads SDK Support team.

I tested our Google Sample Project with the test ad unit ID’s but unfortunately we are unable to reproduce the reported issue on our end. Could you confirm whether the mentioned issue is reproducible in our sample project? If yes, please share the following details via reply to author option? for further investigation.

• App ID’s and affected ad unit ID’s for both android and iOS

• SDK versions are being used

• Sample project reproducing the issue 

• Issue screen recording

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001wno18IAA&entry.80707362=00348915

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Thanks,

 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2026-01-07 11:48:02Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01wno18:ref" (ADR-00348915)

[Nomad88]

It looks like the issue has been resolved on Google's side, though some users are still reporting it. the fix seems to be rolling out gradually and may take time to reach all users.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for confirming that the issue has been fixed. Please let us know if you are still facing this issue or if everything is now working as expected.

Thanks,

 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2026-01-07 16:58:55Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01wno18:ref" (ADR-00348915)