Received error HTTP response Code: 400

1,978 views
Skip to first unread message

William

unread,
Mar 6, 2017, 8:08:00 PM3/6/17
to Google Mobile Ads SDK Developers
We are trying to display a rewarded video and keep getting the following message:

Received error HTTP response Code: 400
There was a problem getting an ad response. ErrorCode: 0
Failed to load at: 0

This happens on all our devices and there is no email or message our app or dev account as been blocked from showing ads.  Please help :)

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Mar 6, 2017, 10:13:07 PM3/6/17
to Google Mobile Ads SDK Developers
Hi William,

Were the ads successfully displaying on your application(s) before? Would you be able to try your Ad Unit ID(s) on our sample apps and verify if you can still replicate the issue?
Additionally, would you be able to provide us your Ad Unit ID(s), with complete error/warning logs, as well as a sample code snippet on how you are requesting and/or showing the ads?
If you could provide logs from Charles' Proxy with SSL Proxying enabled, it would really be helpful to us in investigating the cause of the issue.

Regards,
Joshua Lagonera
Mobile Ads SDK Team

William

unread,
Mar 7, 2017, 5:23:41 AM3/7/17
to Google Mobile Ads SDK Developers
Hi Joshua / Mobile Ads SDK Team

Same error appears with the sample apps.  I have attached a zip file with logs required...  However we may still had trust certificate issue on our android devices after following the instructions.  We have been stuck on this for several days now and could really need some help.

One thing I need to note is that my devs integrating this is in China, and they are using Astrill VPN on the testing device.

Thanks,
William
LogsArchive.zip

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Mar 7, 2017, 6:24:14 AM3/7/17
to Google Mobile Ads SDK Developers
Hi William,

This may be a network issue on your end since you are still able to replicate the issue on our sample apps. However, it may also be caused by the VPN application/program that you are using.
That said, would you be able to export and provide us the Charles' Proxy Logs session file? Additionally, can you provide us your Ad Unit ID so we may investigate further? Can you, also, try creating a new Ad Unit ID and check if you can still replicate the error using the sample apps?

Regards,
Joshua Lagonera
Mobile Ads SDK Team

William

unread,
Mar 7, 2017, 7:24:26 PM3/7/17
to Google Mobile Ads SDK Developers
Hi Joshua,

The Ad Unit ID is: ca-app-pub-6802708037165821/1422759795

I will get you the charle's proxy session log as well, but it probably won't be informative as it appears not to have established a connection.  Is there a recommended VPN for testing on devices located in countries where Google is blocked?

Best Regards,
William

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Mar 7, 2017, 11:27:18 PM3/7/17
to Google Mobile Ads SDK Developers
Hi William,

Thank you for providing me your Ad Unit ID.
I tried using your Ad Unit ID on the sample app and I can verify that I can receive ads on my end, so this is most likely a network and/or device specific issue on your end.
As for your Charles' Logs, make sure that SSL Proxying is Enabled, and your application trusts the SSL Certificate that Charles' provides, as stated on your screenshot. For your second concern, any VPN should work. However, would you be able to try to request ads without a VPN and verify if you are able to receive ads on your end?

Regards,
Joshua Lagonera
Mobile Ads SDK Team

William

unread,
Mar 8, 2017, 5:56:22 AM3/8/17
to Google Mobile Ads SDK Developers
Hi Joshua,

It appears that the Ad Unit ID changed in the dashboard after adding a network somehow, and my devs weren't using the updated one.... not sure how that's possible but error code 0 went away after updating the Ad Unit ID.

They are now getting a different error code 3.  A quick Google search indicates it's due to "no fill". I have asked them add more networks/adapters and try again, but if you have any other feedback regarding error code 3 please let me know.

Best Regards,
William

Veer Arjun Busani(Mobile Ads SDK Team)

unread,
Mar 8, 2017, 3:03:59 PM3/8/17
to Google Mobile Ads SDK Developers
Hi William,

Error Code 3 - No fills simply means that there were no ads returned from the server. Now, is this: ca-app-pub-6802708037165821/1422759795 the Ad Unit ID that you are testing with? Make sure that you have Chartboost's SDK and Adaptor along with the Mobile Ads framework in your project. You can use our sample app that get things started.

Thanks,
Arjun Busani
Mobile Ads SDK Team

William

unread,
Mar 8, 2017, 9:40:57 PM3/8/17
to Google Mobile Ads SDK Developers
Yes it's the ad unit we are using.  We are still getting error code 3.  We have added Tapjoy now as well now. 
Couple questions:
1. Do we need to create the rewarded video content on the mediated networks?
2. When displaying mediated networks' rewarded videos, do we pay user and get paid through Admob, or through the mediated network?

Best Regards,
William

Veer Arjun Busani(Mobile Ads SDK Team)

unread,
Mar 9, 2017, 1:24:47 PM3/9/17
to Google Mobile Ads SDK Developers
Hi William,

1. Do we need to create the rewarded video content on the mediated networks?

You would have to enable Rewarded Content from your third party mediation networks to be able to load them. But the content itself would be backfills. Are you asking for your own in house based reward video ads to be served or backfills? Currently, you can only serve backfill Reward Video Ads.

2. When displaying mediated networks' rewarded videos, do we pay user and get paid through Admob, or through the mediated network?
 
You would only be paid for the ads served via the AdMob network from your AdMob account. All other earnings will be paid directly from your mediation network.

Thanks,
Arjun Busani
Mobile Ads SDK Team
Reply all
Reply to author
Forward
0 new messages