Cant load native ads: "Incorrect native ad response. Click actions were not properly specified"

485 views
Skip to first unread message

邱至民

unread,
Mar 5, 2018, 4:06:21 AM3/5/18
to Google Mobile Ads SDK Developers
Hi, 

I have exactly the same problem as the old one describes.
I was told to create a new thread because the last one is too old to continue discussions.

Here's the problem.
I'm trying to implement NativeAd in my app. Everything worked fine until yesterday, it's now printing these error logs.

I/Ads: WebView loading for native ads.
I/Ads: Javascript has loaded for native ads.
I/Ads: Received log message: <Google:HTML> Incorrect native ad response. Click actions were not properly specified

onAdFailedToLoad errorCode = 0
So I can't show native ads anymore. Here's how I do the requests.

private AdRequest adRequest = new AdRequest.Builder()
            .build();

private NativeAdOptions nativeAdOptions = new NativeAdOptions.Builder()
        .setAdChoicesPlacement(ADCHOICES_TOP_RIGHT)
        .setRequestMultipleImages(false)
        .setReturnUrlsForImageAssets(true)
        // Methods in the NativeAdOptions.Builder class can be
        // used here to specify individual options settings.
        .build();

AdLoader adLoader = new AdLoader.Builder(mContext, adUnitId)
            .forAppInstallAd(new NativeAppInstallAd.OnAppInstallAdLoadedListener() {
                @Override
                public void onAppInstallAdLoaded(NativeAppInstallAd appInstallAd) {
                    refreshAd(appInstallAd);
                }
            })
            .forContentAd(new NativeContentAd.OnContentAdLoadedListener() {
                @Override
                public void onContentAdLoaded(NativeContentAd contentAd) {
                    refreshAd(contentAd);
                }
            })
            .withAdListener(adListener)
            .withNativeAdOptions(nativeAdOptions)
            .build();

adLoader.loadAd(adRequest);
If I comment out forAppInstallAd then the ads can be downloaded again. But the fill rate is very low.

Here is the link of the sample project and a Charles Session File.
It's shared to android-...@google.com.



mobileadssdk-a...@google.com

unread,
Mar 5, 2018, 3:45:24 PM3/5/18
to 邱至民, Google Mobile Ads SDK Developers
Hi there,

Thanks for contacting us. For us to narrow down the issue, can you please confirm whether you were able to load native ads using our sample app with the latest SDK version? Also, please share the Charles log by using "Reply privately to Author" available. The drive link that you have shared is not accessible.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

mobileadssdk-a...@google.com

unread,
Mar 6, 2018, 3:20:53 PM3/6/18
to 邱至民, Google Mobile Ads SDK Developers
Hi there,

Thanks for sending the Charles log. Is there any specific reason for requesting from a local machine? Can you confirm whether this is happening with our sample app? And then send us a Charles recording if you are still able to reproduce and we will have a look. Also, are you using the latest version of the SDK?

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

邱至民

unread,
Mar 6, 2018, 9:44:06 PM3/6/18
to Google Mobile Ads SDK Developers
Hi, 

I'm using Firebase 11.8.0 with Android API 27 but target to API 26 because you have another bug when it's targeting to API 27.
And what did you mean "requesting from a local machine"? Do you mean that you don't know why it's requesting from 172.217.160.98?
This log was captured on a emulator with API 25.
I don't know why it's requesting ads from 172.217.160.98. I even don't know how to change it.
We only use 192.168.x.x local ip addresses.

mobileadssdk-a...@google.com於 2018年3月7日星期三 UTC+8上午4時20分53秒寫道:

mobileadssdk-a...@google.com

unread,
Mar 7, 2018, 3:06:58 PM3/7/18
to 邱至民, Google Mobile Ads SDK Developers
Hi there,

Thanks for sharing the Charles logCan you capture on an actual device and send us logs? We will then share this with the rest of the team.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

mobileadssdk-a...@google.com

unread,
Mar 8, 2018, 3:06:30 PM3/8/18
to 邱至民, Google Mobile Ads SDK Developers
Hi there,

I haven't been able to reproduce this issue with the returned creative from Charles and I was able to load the ad(on a device). Having said that, as the app install ads have the market download urls, and the emulator doesn't have the Play Store, the Google Mobile Ads SDK explicitly checks this case and fails the ad, even if serving returns an app install ad for a request on an emulator. So, if it works on a device, then we can safely assume that everything is working properly.

Let us know if you have any other questions. We will be happy to assist you.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

mobileadssdk-a...@google.com

unread,
Mar 9, 2018, 3:33:58 PM3/9/18
to 邱至民, Google Mobile Ads SDK Developers
Hi there,

Thanks for getting back to us. I don't notice this error'd creative being returned in the Charles log you have provided. The issue also pertains to the device when the ad request is being made and I would advice that you try to reproduce on a device and let us know and we will have a look.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 03/08/18 15:06:03 mobileadssdk-a...@google.com wrote:
Hi there,

I haven't been able to reproduce this issue with the returned creative from Charles and I was able to load the ad(on a device). Having said that, as the app install ads have the market download urls, and the emulator doesn't have the Play Store, the Google Mobile Ads SDK explicitly checks this case and fails the ad, even if serving returns an app install ad for a request on an emulator. So, if it works on a device, then we can safely assume that everything is working properly.

Let us know if you have any other questions. We will be happy to assist you.

Regards,
Deepika Uragayala
Mobile Ads SDK Team
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Reply all
Reply to author
Forward
0 new messages