Hello XT,
Thank you for reaching out to us.
For us to further investigate this, could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com? Kindly inform us on this thread if you sent it directly to the email provided.
As a side note, if you're having trouble receiving private replies from us, please check your Spam folder. Additionally, please add the 'From address' on that email to your contact list to ensure we aren't flagged as Spam in future messages. If you don't see a message from us in your Spam folder, please email us directly at mobileads-...@google.com referring to this forum thread.
Regards,
|
||||||
Hello,
Michael here from Mobile Ads SDK support team. Thank you for reaching out to us.
Would you be able to confirm if you have followed this guide in adding your test device? Asking this as I am seeing a bit of differences with the implementation. If the issue persist while following the guide, kindly provide to us the below information so we can further check on our end:
You may send the requested details privately via "Reply to Author" button or with the below process.
If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:
1. Navigate to
2. Fill out all fields, and attach your file(s).
3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.
Regards,
|
||||||
Hello,
Thank you for your response.
I was asking if you have followed the guide as it appears that the same issue is not reproducible using our sample apps. Would you be able to confirm if you were able to replicate the issue in our sample apps as well?
Additionally, kindly provide the below information so we can further investigate on our end:
You may send the requested details privately via "Reply To Author" button.
Regards,
|
||||||
Hi,
We are seeing real ads on some emulators too, when we shouldn’t.
They do not have the TEST AD indication and we are seeing some impressions on the AdMob Reports too.
It seems to happen only in API 33.
The same app when run on an emulator with API 31 shows the ads, but the TEST AD indicator is shown as expected.
Please, correct this as soon as possible, as we shouldn’t worry about showing ads (with the possibility of our accounts being disabled) when testing on emulators.
We are using Android Studio Dolphin (2021.3.1 Patch 1) and the Android Emulator version is 31.3.13.
|
||||||
Hi Joshua,
Yes, real ads are shown every time in our app when we run it on an emulator with API 33.
I’ve added some logging to the code:
Log.d("AdsManager", "isTestDevice? ${ adRequest.isTestDevice(context) }")
And in API 31 the result is always true, while in API 33 it is always false.
Regarding the Charles log, I’ve used Mitmproxy to get the request results.
On API 31 the “adtest=on” is present, while in API 33 it is not.
In our case, we are not using mediation.
Below is a screenshot of a banner ad in our app with API 31 and API 33.
As you can see in API 31 the Test Ad text is present, while in API 33 it isn't.
--
---
You received this message because you are subscribed to a topic in the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-admob-ads-sdk/Kk0kDDYVbX0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/o5D_N000000000000000000000000000000000000000000000RMX96S00R_VAPu4cTO2oXGRFW2glSw%40sfdc.net.