Hello Experts,
We are facing a persistent issue where test ads fail 100% of the time, but live ads serve perfectly. We have exhausted all standard troubleshooting and are seeking expert guidance.
The Core ProblemTest Ads Fail: All formats return Error Code 3 (No Fill). This happens with both Google's sample ad units and our own units with a registered test device.
Live Ads Work: The exact same code implementation successfully loads and displays live ads when the test configuration is removed.
The Critical Clue: For every failed test ad, loadAdError.getResponseInfo() returns null. We get no Response ID or any diagnostic auction data, which is highly unusual for a standard "No Fill" error.
Mediation: Our setup is 100% pure AdMob. All third-party mediation SDKs and dependencies have been completely removed.
UMP/GDPR: Our User Messaging Platform SDK is correctly integrated and the consent flow completes successfully before any ad requests are made.
Basic Setup: Live ads are working, which confirms our core SDK initialization, ad lifecycle management, and UI code are correct.
Client-Side Cache: We have performed aggressive cleaning, including:
Deleting all build and .catch folders.
Manually verifying all libs folders are empty.
Clearing the cache and storage for both our app and Google Play Services on the device.
Resetting the device's Advertising ID.
Account Issues: Our AdMob account is 3+ years old and has no policy violations.
What further steps can we take, or what specific information can we capture, to diagnose why test ad requests are being treated (No Fill) and result in a completely empty response?
Hi,
Thank you for contacting the Mobile Ads SDK Support team.
I will check with the wider team and get back to you. In the meantime, your patience is appreciated.
![]() |
Mobile Ads SDK Team |
[2025-10-13 19:26:07Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vQeSx:ref" (ADR-00335330)
Hi,
The issue has been resolved. Kindly check and confirm the results.
![]() |
Mobile Ads SDK Team |
[2025-12-02 06:22:27Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vQeSx:ref" (ADR-00335330)