GADNativeContentAd: Error Domain=com.google.ads Code=13 "Request Error: Received invalid response."

[ma...@rome2rio.com]

Hi,

After following the instructions on https://developers.google.com/admob/ios/native-advanced I am having issues getting GADNativeContentAd to show in my app.

Using our production Admob App ID, the supplied Test ID from Google (ca-app-pub-3940256099942544/3986624511) for GADRequests, and adTypes: [GADAdLoaderAdType.nativeContent], I receive the following error message:

Error Domain=com.google.ads Code=13 "Request Error: Received invalid response." UserInfo={NSLocalizedDescription=Request Error: Received invalid response., NSLocalizedFailureReason=Request Error: Received invalid response.}

The bigger problem is that sometimes I DO receive GADNativeContentAd but the request works sporadically, leaning on the side of not working more often than working.

Note: The exact code works with GADAdLoaderAdType.nativeAppInstall & GADAdLoaderAdType.unifiedNative

Interestingly, when using unifedNative, the majority of the time appInstall ads are served.

I was able to easily replicate this by modifying the google sample project (attached)

Why am I seeing this error message and what does it mean?  Invalid Response implies that the GoogleMobileAds can't parse the response it's given.  I'm using the latest. (afma-sdk-i-v7.28.0)

Cheers,
Mark

[ma...@rome2rio.com]

Charles doesn't really give any useful information either.  The error message doesn't even appear in any response I can find.  Attached the data from Charles + screenshot showing which requests I was looking it

[mobileadssdk-a...@google.com]

Hi Mark, 

Thank you for sharing this information. Our team is aware of this issue and are currently investigating this. I will update this thread if I have any new information to share.

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/1349ef2a-cde3-429d-9f0f-72cdc5dc24b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mobileadssdk-a...@google.com]

Hello Mark, 

Thank you for your patience. Our team has fixed this issue. Can you try loading the Native Content Ads with our sample apps and see if you're still seeing the issue? If yes, please share us the device logs. 

Let me know how it goes. 

Regards,

Bharani Cherukuri

Mobile Ads SDK Team

[ma...@rome2rio.com]

Hi Bharani,

Still getting error message:

2018-03-02 11:34:04.633661+1100 NativeAdvancedExample[43452:22620027] <Google:HTML> undefined is not an object (evaluating 'a.tracking_urls_and_actions')

<GADAdLoader: 0x6000002a1500> failed with error: Request Error: Received invalid response.

Note: I'm using the sample projects with the lastest SDK (afma-sdk-i-v7.29.0) - refactoring NativeUnifedAds to be NativeContentAds

Cheers,

Mark

[ma...@rome2rio.com]

So only changing the line

    adLoader = GADAdLoader(adUnitID: adUnitID, rootViewController: self,

                           adTypes: [ .nativeContent ], options: nil)

And implementing GADNativeAppInstallAdLoaderDelegate and GADNativeContentAdLoaderDelegate I was able to reproduce the error for native content ads.  App Install and Unified Ads work perfectly.

Cheers,

Mark

[mobileadssdk-a...@google.com]

Hi Mark, 

I was able to modify the sample project to the changes that you made and load Native Content ads without any issues. Could you share your project so I can take a look?

Thanks,

Bharani Cherukuri

Mobile Ads SDK Team

[ma...@rome2rio.com]

Hi Bharani,

Thanks for the ongoing help in this.  I've attached the project.

It's strange, if you can get it working on your end but I cannot at mine, could it be an IP Address related issue?  Does Google throttle requests or anything?

Cheers,

Mark

[mobileadssdk-a...@google.com]

Hello Mark, 

Apologize for the back and forth. Since we are not able to reproduce the issue on our end, could you share us the Charles Proxy logs with SSL Proxy enabled? This will help us track the network traffic and other server parameters.

Thanks,

Bharani Cherukuri

Mobile Ads SDK Team

[ma...@rome2rio.com]

Hi Bharani

Do these Charles session logs help?

Cheers,

Mark

[mobileadssdk-a...@google.com]

Hi there,

Thank you for providing the Charles' Proxy logs. It is interesting to note that the Ad Response is returning an empty JSON response which leads me to believe that it should be a No Fill Error instead of an Invalid Response. Regardless, our Test Ad Unit IDs should be expected to serve ads. I was also able to replicate the issue on my end using our sample apps.

That said, let me forward this information to the rest of the team and get back to you once I have their insights.

Regards,

Joshua Lagonera

Mobile Ads SDK Team

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/73b9de5a-440e-424f-a8c6-a2eae9fc98d5%40googlegroups.com.

[dev....@gmail.com]

Hello,

I am experiencing the same issue. Is there any update?

King Regards

[mobileadssdk-a...@google.com]

Hi there,

I'm afraid we still do not have updates with regards to this issue. Let me request a gentle follow-up from the rest of the team and get back to this thread once I have any updates to share.

Regards,

Joshua Lagonera

Mobile Ads SDK Team

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To post to this group, send email to google-admob-ads-sdk@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/4a73aea0-05f4-42d4-b453-dd32afb8c84c%40googlegroups.com.

[ma...@rome2rio.com]

Hi Joshua,

I've been off for a few weeks, is there any update to this?  We'd like to release our app soon with the new Google Native Ads.

Cheers,

Mark

[mobileadssdk-a...@google.com]

Hi Mark,

Thank you for your patience. I'm responding on behalf of Joshua because he is out of office.

I'm afraid there are still no updates with regards to this issue. That said, I will send another followup and get back to you for any official feedback.

Regards,

Ivan Bautista

Mobile Ads SDK Team

[ma...@rome2rio.com]

Hi Ivan,

Is there any feedback?

Cheers,

Mark

[mobileadssdk-a...@google.com]

Hi Mark,

Thank you for following up on this. The team is still actively working on this.

Do you only get the Invalid Response Error or Error Code: 13 when loading test ads via our sample Ad Unit Id or you can also reproduce the same error when loading live ads using your Native Advanced Ad Unit Id?

[ma...@rome2rio.com]

Hey Guys,

So for everyone that comes across this problem in the future, using a production adUnitID and adding 

request.testDevices = [ kGADSimulatorID , <Your_iPhone_UUID etc.> ]

Will get test ads to return all the time.

Using the Google provided adUnitID still does not work, so avoid doing that until it's fixed.

Will still monitor this thread to see any updates on the Google provided adUnitID filling ads.

Cheers,

Mark

On Friday, February 16, 2018 at 10:06:52 AM UTC+11, ma...@rome2rio.com wrote:

[mobileadssdk-a...@google.com]

Hi Mark,

Thank you for sharing your findings. 

The team is still actively working on this. Rest assured that we will get back on this thread for any official update.

[mobileadssdk-a...@google.com]

Hi Romain,

I deleted your post as it contains a Charles session of when you tried to load your DFP Ad Unit Id. Please note that Ad Unit Ids are considered confidential information and should not be posted in public forums.

That said, below is a copy of your original post.

Hi,

I'm experiencing the same problem with custom templates (native and appInstall works fine). 
Is there any update about this?

Regards,

Romain

[mobileadssdk-a...@google.com]

Hi Romain,

I'm afraid there is still no updates with regards to the Invalid Response error encountered when loading test Native Content Ads using the sample Native Advanced Ad Unit Id. I will update this thread once we get an official feedback on this.

On the other hand, I tried loading your DFP Ad Unit Id (captured in your Charles logs) in our DFPCustomRenderingExample app and I kept on getting No fills but not Invalid Response. Are there any custom targeting set for your Ad Unit Id that I need to add in my AdRequest?

That said, your issue seems to be different from the issue reported for this thread because the Charles logs you provided returned a non-blank response and the Ad request was sent for your live DFP Ad Unit Id. On the other hand, the Charles logs captured for the bug reported for this thread returned a blank JSON response and it was loaded using the sample Native Advanced Ad Unit Id.

To help us narrow down the root cause of the Invalid Response error encountered on your end, could you confirm the following?

• Could you check if you can replicate the Invalid Response if you load a test custom template ad using the sample Custom Rendering Ad Unit Id?
• Could you confirm if you can only replicate the Invalid Response error with the Ad creative (or Ad response) captured in the Charles logs provided?

However, given that the Invalid Response error encountered on your end seems to be different from the one reported on this thread, could you create a new thread and share your new findings there and we'll continue the investigation from there.