[iOS Ad Inspector] Not loading ad unit list

[caro...@gmail.com]

I'm trying to test my UMP integration with test ads, but the ad inspector had been behaving weirdly. 

Only the first launch from XCode seems to load the app's ad unit list successfully.

If I force stop and relaunch the app (as standard workflow to enable "single ad source mode" from the ad inspector), the ad unit list disappears, and AdMob would not respond to ad requests at all (no completion callbacks).

The app DID receive the AdMob SDK init completion callback, with correct mediation adapters setup status, which also showed up in the ad inspector. Logs showed no helpful information; it feels like AdMob-related domains are blocked when ad requests are made.

I had enabled Apple's ATT tracking with the app when the above-mentioned behavior happened.

If I disable Apple's ATT tracking for the app, ads again start to load and show correctly. However, I cannot activate the ad inspector by gesture. This is really confusing. 

Used pods (COCOAPODS: 1.14.3)

- Google-Mobile-Ads-SDK

- GoogleMobileAdsMediationUnity

- FirebaseAnalytics

- FirebaseCrashlytics

Tests were done with both XCode 14.3.1 and XCode 15.1.

Physical iPhone SE 2 with iOS 16.1.2.

Region GDPR applies: NO

Please let me know if this is intended behavior, or if there are settings I can enable to produce more helpful logs. Thanks!

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

By reviewing your concern, I understand that you are facing issues with your Ad ID (UMP) integration and the Ad Inspector while testing your app's ad units with AdMob. 

Please follow the below steps:

• Check your app permissions

• Double-check your AdMob account configuration, ad units, and mediation settings. Ensure that everything is set up correctly on the AdMob dashboard.

• Check your UMP integration to ensure that you have correctly implemented it in your app. Verify that you're handling consent requests and user tracking transparency correctly.

• Check the logs for any error messages or warnings that might provide insight into the issue.

• Ensure that you are using the latest version of the AdMob SDK, UMP, and any mediation adapters. Sometimes, issues are resolved in newer releases.

If the issue still persists, kindly provide the sample project reproducing the issue, so we could have full visibility of your implementation. 

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02r2ZPq:ref"

Thanks,
 

Mobile Ads SDK Team

[caro...@gmail.com]

Thanks for the reply. It seems that the ad inspector was silently blocked by my test iOS device's "Screen Time" -> "Content & Privacy Restrictions".

It'd be great if AdMob's logs would show some hints on timeout / service unreachable reasons.