Hi,
Error code 3, no fill error means that the ad request was successful, but no ad was returned due to lack of ad inventory. Kindly note that the SDK just requests ads to the ad server and does not have any control on the ads it serves. For test ads, you can refer to Enabling test ads.
This is more of an Ad serving concern rather than anything specific to the code implementation of the Mobile Ads SDK. I would recommend that you refer to AdMob Error Codes & Logs for more details about the issue.
If the issue still persists, kindly provide the below information via the reply to author option for further investigation
So that we will review your account and let you know why ads aren’t showing.
![]() |
Mobile Ads SDK Team |
Break down your traffic reports into meaningful segments using app filters such as app name, ad unit and country. This will help you gauge how changes to traffic sources or implementation can affect your ad traffic. You can use Google Analytics to get detailed information about your app visitors, and be on the lookout for any suspicious user behavior. Some questions to ask yourself:
Learn more about how you can use Google Analytics in AdMob and how to implement the Google Analytics SDK for Android and iOS.
Kindly refer Understand your ad traffic and app users and I would recommend reaching out to the Product support team as they are better equipped to address your concern.
Hi,
Please note that our Google sample application was successfully executed using the provided details, resulting in the successful loading of ads. Furthermore, we modified your bundle ID and confirmed the continued display of ads.
It appears that there are certain implementation challenges within your application. Would you kindly share a sample of your application with us so that we may conduct a thorough review and provide an appropriate solution?
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, kindly provide requested information to us via reply to author option or using the steps below:
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.Hi Evgenii,
Thank you for getting back to us.
I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.
Hi,
Thank you for contacting the Mobile Ads SDK Support team.
I ran the Google Sample Project with the app ID and ad unit ID you have provided and was able to load the ads successfully. Could you try once by enabling the Ad Inspector ? and then share the export request and response file generated from the Ad Inspector for further investigation.
Note:You can export the ad response only after you add your test device in the AdMob UI.
For detailed info refer to this AdInspector document. Kindly provide the requested details via Reply privately to author option.
Please check this Getting started with Ad Inspector video to troubleshoot the “no fill” errors.![]() |
Mobile Ads SDK Team |
Hi Evgenii,
Thank you for contacting the Mobile Ads SDK Support team.
Error code 3, no fill error means that the ad request was successful, but no ad was returned due to lack of ad inventory. Kindly note that the SDK just requests ads to the ad server and does not have any control on the ads it serves.
This is more of an Ad serving concern rather than anything specific to the code implementation of the Mobile Ads SDK. I would recommend that you refer to AdMob Error Codes & Logs for more details about the issue.
Could you kindly provide the below information via reply to author option so that we can conduct an investigation and offer a solution.
![]() |
|