Hi there,
Thank you for reporting this to us. For me to check this on my end, could you share your App ID with me using Reply privately to author option?
Regards,
Mark Albios
Mobile Ads SDK Team
Hi there,
Thank you for sharing your App Id in private. I tried using your App Id on our sample app and I was able to proceed with the Ad request and successfully load an ad. You may refer to this getting started guide for your reference. Also, since you've mentioned that you're able to recreate the issue using our sample app, could you also share it with me privately for me to take a further look on the issue?
Regards,
Mark Albios
Mobile Ads SDK Team
Hi there,
Thank you for getting back to me. See my responses on your questions below:
Is there any way to solve these two issues?
1. Check MaioAdaptor is added correctly - As per the documentation, when importing the maio SDK and its adapter using CocoaPods, no additional coding is required as its already integrated on your project.
2. Check advertisement is successfully shown by using my testing advertisement Id - When using our Test Ad Unit Ids, you should be able to load test ads on your app.
I've integrated Maio mediation on our sample app using the steps on this documentation and I was able to load an ad without any error. It's odd that you encountered an error on your end. It would be very helpful if you could provide me the test project (with your Ad Unit Id) where you encounter the error for me to further investigate on my end.
As an aside, could you confirm if you've properly configured your billing account as this also affects the serving of ads?
Regards,
Mark Albios
Mobile Ads SDK
Hi there,
Thank you for sharing your sample project with me in private. I've tried running the test project; however, I wasn't able to load an ad due to an error. The error could be due to any of the following reasons: AdMob account approval, Incomplete Account setup, Billing and Payment, etc. Please see your AdMob account if any of the reasons is applicable to you.
In addition, I can see from your project file that the log's state (see below) is Ready on my end.
(key: "GADMobileAds", value: <GADAdapterStatus: 0x283d60000; state = Ready>)
Also, in addition to my answer to your previous inquiry on how to check mediation adapters properly, you may want to use the Mediation Test Suite to see if you've correctly configured your application and ad units to be able to display ads from third-party networks via AdMob mediation.
Please let me know if you any questions related to the Mobile Ads SDK. I'll be happy to assist you.
Regards,
Mark Albios
Mobile Ads SDK Team
"GADMobileAds": <GADAdapterStatus: 0x600003cfce80; state = Not Ready;Could not retrieve application configuration data.>
Hi All,
Thank you for reporting this to us. I will raise this to our Engineering Team and update this thread once I receive any updates from them.
@Pat, thank you for sharing your App Id in private.
Regards,
Mark Albios
Mobile Ads SDK Team
Hi,
We have observed this in a provided App ID and our team is investigating. If you also are seeing this issue please reply privately to author with your AdMob App ID to assist with our investigations.
Regards
Sam
Hi Brandon,
Yes please do send through your app ID in a private reply.
Hi,
Sorry for delayed response.
Based on the feedback I've seen, this appears to be a temporary issue for most people.
Please update if this is an ongoing issue.
GADMobileAds.sharedInstance().start { (status) in
print(status.adapterStatusesByClassName)
}
["GADMobileAds": <GADAdapterStatus: 0x7b0c001f1dc0; state = Not Ready;Could not retrieve application configuration data.>]