Hi,
Thank you for contacting the Mobile Ads SDK Support team.
Kindly note that I have removed your response from the forums as it contains the PII information.
After a thorough review of the account we have found that your app hasn’t been reviewed yet. To have it reviewed, make sure your app has been verified. You must also link your app to a supported app store in AdMob to trigger the review.
Please find below your previous response with redacted information.
One of our iOS apps is connected to the latest version of admob sdk, appid, unitid app-ads has been configured, using the official dedicated test ad unit ID: ***********************************. The current problem is that the advertisement cannot be requested, and the prompt message is No ad to show -> using test /app ID for interstitial, the application ID is ***********************************, please help to check the reason, thank you.
![]() |
Mobile Ads SDK Team |
Thank you for your response. We have followed the steps to set up app-ads.txt as required. (https://support.google.com/admob/answer/9363762?sjid=13461643796723623949-AP#step3)We have successfully completed steps one through three:
However, we have not been able to complete steps four and five:
AdMob has not crawled and verified this file, and we are unsure where the issue lies. The publisher ID in the app-ads.txt file was copied from the app-ads.txt under the AdMob application. The website link is https://alphamotech.com/app-ads.txt. This step is also set (Apple App Store: add your developer website in the marketing URL field of the product details).
Could you please assist us in identifying the problem?
Thank you for your help.
Best regards,
Kathy
Hi Kathy,
Thank you for providing more information.
It is good to hear that you have completed the first 3 steps. Step 4 is from AdMob's side and be informed that it can take up to 24 hours for AdMob to crawl and verify your app-ads.txt files. Once step 4 is completed, then step 5 is from your side to verify your app-ads.txt file.
To investigate whether you published your file correctly, check that you successfully see your file's content when you access the app-ads.txt URL in your web browser. If you can see the file in your web browser, it is likely that crawlers will successfully find it. View the details about AdMob's attempts to crawl your app-ads.txt file in your AdMob account.
Thank you for your reply.
Regarding the first three steps mentioned in the email, we completed them on May 16th. The current issue is that we have been waiting for AdMob to crawl our app-ads.txt file on our website. We have been waiting for over 24 hours, and our progress is stuck at step four, preventing us from moving on to step five. As a result, we are unable to enable ads.
Please help us determine the cause. Is there an issue with the app-ads.txt file we submitted on our website, or has our app been restricted or banned (ca-app-pub-1665036043476340~6913737915)? Please assist us in investigating this issue.
Thank you for your help.
Kathy
Hi,
I would like to provide additional details to facilitate your investigation. The app ID is: ca-app-pub-1665036043476340~6913737915,the website link is https://alphamotech.com/app-ads.txt. Attached, you will find the relevant information about the app, as well as screenshots showing that no ads were displayed during testing.
Thank you for your assistance.
KahtyHi,
After testing, we still cannot retrieve test ads in both real device and simulator environments.
The steps we took to modify the project for testing are as follows:
Used the official InterstitialExample project
Updated the library with Pod update.
Replaced the app bundle ID with com.alphatech.manl
Replaced GADApplicationIdentifier with ca-app-pub-1665036043476340~6913737915
Loading the ad failed with the message “Request Error: No ad to show.”
Attached is the test project after we completed the above steps. It can be run directly.
Hi,
Thank you for sharing the details
We ran the application and this issue is related to your specific package name, we can confirm this is not an SDK integration issue. I would recommend checking a few additional resources to make sure all configurations are correct: