GMASDK 8.0.0 on iOS : Could not retrieve application configuration data.

296 views
Skip to first unread message

Raytheon@TVB

unread,
Feb 15, 2021, 9:54:17 PM2/15/21
to Google Mobile Ads SDK Developers
Dear all,

Our iOS developers are having trouble calling banner ads after upgrade GMASDK to 8.0.0

When the following is called
[[GADMobileAds sharedInstance] startWithCompletionHandler:^(GADInitializationStatus *status) {
}];

The following Error returns
GADMobileAds = "<GADAdapterStatus: 0x283629080; state = Not Ready;Could not retrieve application configuration data.>";

Also when checking the charles log, we can see HTTP Error 400 has been returned when calling the following API:

Would you please help?

Thank you!

Best Regards,
Ray

Mobile Ads SDK Forum Advisor Prod

unread,
Feb 16, 2021, 1:32:56 AM2/16/21
to raythe...@tvb.com, google-adm...@googlegroups.com

Hi Ray,

Thank you for reaching out to us.

Does this issue also occur if you use your ad unit ID/s with our sample app? If so, could you then kindly provide the details below (via Reply to author, or a direct, private reply to this email) so that I can further investigate the issue?

 

Google Logo
Ziv Yves Sanchez
Mobile Ads SDK Team
 


ref:_00D1U1174p._5004Q2CRJbS:ref

Raytheon@TVB

unread,
Feb 16, 2021, 1:52:00 AM2/16/21
to Google Mobile Ads SDK Developers
Hi Ziv,

I have replied you the details via email since I have no permission to reply to author.
Please check.

Thank you!

Best Regards,
Ray

Mobile Ads SDK Forum Advisor Prod

unread,
Feb 16, 2021, 4:44:24 AM2/16/21
to raythe...@tvb.com, google-adm...@googlegroups.com

Hi Ray,

Thank you for providing the requested details.

I tried out your ad unit ID with our sample app, and can confirm that I was also getting same message on my end; additionally, I was not able to receive a banner ad as well. That being said, the message only appears when you have no mediation configurations for your ad units, and thus you may safely ignore it for this particular scenario. It seems that the issue exists elsewhere.

With this in mind, could you kindly provide the details below (via a direct, private reply to this email) so that I can further investigate the issue?

  • Charles log capturing the issue (i.e. the actual .chls file)

Raytheon@TVB

unread,
Feb 16, 2021, 10:25:24 PM2/16/21
to Google Mobile Ads SDK Developers
Dear Ziv,

Thank you for your reply!

What have been bothering is that we are not able to receive banners even from Direct I/O when an older build without the update to 8.0.0 can receive the banner ad from the same ad unit.
Do you think the 2 issues are related?

Since I don't have the new build on hand at this moment. I will share you the Charles Log later.

Thank you!

Best Regards,
Ray

Mobile Ads SDK Forum Advisor Prod

unread,
Feb 17, 2021, 1:51:29 AM2/17/21
to raythe...@tvb.com, google-adm...@googlegroups.com

Hi Ray,

I'm afraid that I do not have sufficient details on hand at the moment to suggest an educated guess here, although version updates do tend to cause these errors from time to time. We will be waiting for the requested Charles log so that we can continue our investigation on this.
 

Raytheon@TVB

unread,
Feb 17, 2021, 2:36:52 AM2/17/21
to Google Mobile Ads SDK Developers
Hello Ziv,

We have been trying to capture the ad calls from the new build but we found out that the ad calls to pubads.g.doubleclick.net aren't fired.

Would you suggest a domain for us to focus on when we are capturing the charles log?

Thank you!

Best Regards,
Ray

Mobile Ads SDK Forum Advisor Prod

unread,
Feb 17, 2021, 4:23:21 AM2/17/21
to raythe...@tvb.com, google-adm...@googlegroups.com

Hi Ray,

You may also try looking for the domain googleads.g.doubleclick.net if possible. Barring even that, you may simply send to us any Charles log that attempted to capture the issue (via Reply to author, or a direct, private reply to email), and we'll see what we can investigate on our end.
 

Reply all
Reply to author
Forward
0 new messages