Hi YongGil,
Thank you for contacting the Mobile Ads SDK support team.
It's always recommended to use the recent version which is shown in the release notes to avoid conflicts. As you mentioned, the issue is also occurring in the older version of your app. To investigate this further, we would need the following details:
Kindly share above details via reply to the author option to do further investigation.
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:
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.
![]() |
Mobile Ads SDK Team |
[2025-10-15 04:41:57Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vQq8L:ref" (ADR-00335534)
Hi again,
I wanted to provide an update.
After factory-resetting my device and reinstalling apps directly from the Play Store, the same behavior still occurs — not only in our app, but also in many other apps that use AdMob.
This suggests the issue is unlikely to be caused by third-party apps or device settings, and may instead be related to AdMob itself or specific ad creatives being served.
Please let me know if you’d like me to capture additional logs or information from this clean environment.