W/Ads: JS: A cookie associated with a resource at http://doubleclick.net/ was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`.

372 views
Skip to first unread message

Tauqeer Niazi

unread,
Jun 11, 2020, 9:09:45 AM6/11/20
to Google Mobile Ads SDK Developers
Hello There,
I have created my AdMob account on 6 June and from the day first after approved my adMod account my app shows ads on testing just as Android Emulator but on real device no ad's are being shown till now. When I run application on real android device its shows this message in debug

W/Ads: JS: A cookie associated with a resource at http://doubleclick.net/ was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032. (https://googleads.g.doubleclick.net/mads/static/mad/sdk/native/production/sdk-core-v40-impl.html:0)
I/chromium: [INFO:CONSOLE(0)] "A cookie associated with a resource at http://doubleclick.net/ was set with `SameSite=None` but without `Secure`. A future release of Chrome will only deliver cookies marked `SameSite=None` if they are also marked `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032.", source: https://googleads.g.doubleclick.net/mads/static/mad/sdk/native/production/sdk-core-v40-impl.html (0)

and at the end it shows this error
I/Ads: Ad failed to load : 3

I don't know what to do know searching all over the internet but failed. 
Please Help I Will Really Appreciate that.

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 11, 2020, 9:53:25 AM6/11/20
to tauqee...@gmail.com, google-adm...@googlegroups.com
Hi there,

Thank you for bringing these errors and warnings with no ads to our attention.

Regarding the cookies messages, I my self see that message all the time and it doesn't affect ad loads.

Regarding "I/Ads: Ad failed to load : 3", this means there's lack of ad inventory for your ad placement as described here - https://support.google.com/admob/thread/3494603?hl=en. This that you see ads in the emulator is because it's automatically a test device as described here - https://developers.google.com/admob/android/test-ads#enable_test_devices so it will give you real looking ads that aren't paid for by traffickers.

From the fact that you see ads in the emulator it appears that you integrated the Mobile Ads SDK into your app correctly. 

Kindly note that ad inventory issues are out of scope of this forum, for we only support integrating the Mobile Ads SDK into apps. The forum that addresses ad inventory is the AdMob Forum. With that  being said, since you mentioned that your account is relatively new, I can offer advice that I've heard that seems to be especially helpful for those who are just starting out with AdMob.
  • account setup - to setup tax info, name and address and phone number in your AdMob Account with verification if applicable
  • to take action when a message shows at the top of your account when you sign in even if there's no hint it will affect ad serving
  • to publish your app on Google PlayStore and set up an app-ads.txt on your apps website - https://support.google.com/admob/answer/9363762?hl=en
  • to fill out as soon as possible whenever you reach a revenue threshold all the payment details you can fill out in your AdMob Account at that revenue threshold - https://support.google.com/admob/answer/2772208, video describing thresholds
  • ​​​​​​​to have in mind what would tempt more advertisers to rent space on your app

I have heard that account setup is crucial for ad serving for new AdMob users, and it's understandable that advertisers would want a safe return on investment just as much as app publishers do.

If you want us to test on our end to replicate what you are seeing, via "Reply privately to author" could you send us your app Id, bundle Id and ad unit Id's affected?

Kind regards,
Aryeh Baker
Mobile Ads SDK Team
​​​​​​​



ref:_00D1U1174p._5004Q20Y41U:ref
Reply all
Reply to author
Forward
0 new messages