|
||||||
|
||||||
|
||||||
|
||||||
Also, the Sample apps work with the new SDK just by updating the "implementation"to
implementation 'com.google.android.gms:play-services-ads:19.5.0'
There's no need to upgrade gradle - it should run out of the box. If you did upgrade gradle, you can always delete entire project and redownload our Sample apps. To test different SDK versions you can change version number, sync and run.
Charles logs can work with the emulator. Since certain steps depend on the type of device being emulated I can give a general, unsupported outline of how I get an emulator to work with Charles on a Mac. Most of the steps you already know, but it is useful to have this outline for others in the forum.
<?xml version="1.0" encoding="utf-8"?> <network-security-config> <debug-overrides> <trust-anchors> <!-- Trust user added CAs while debuggable only --> <certificates src="user" /> </trust-anchors> </debug-overrides> </network-security-config>
I then added to AndroidManifest.xml before the ">" of "application" this line:
android:networkSecurityConfig="@xml/network_security_config"
This worked to get our Sample apps and Guide s working with Charles.
Let me address some of your concerns mentioned in your last post:
- Obsolete samples that won't work with latest gradle plugin.
You want out of the box use of latest gradle plugin. I will raise this request to the rest of my team. You may monitor our Releases for an update.
- Ads not showing in same conditions for original/sampled app.
Could you elaborate on what you are refering to? No ads showing insample with your Id? Different ads showing with your Id?
- Ads reporting no fill or no config without any explanations or solution anywhere.
This request for an explanation of why ads don't serve will be raised with the rest of the team. You may monitor our Blog for an update.
- Charles log not configurable on real device.
I hope that the example I gave for getting Charles to work on an emulator should be helpful for getting it to work on device. Since there are too many variables to consider we will only be able to suggest solutions. Feel free to ask but we may not be able to help. You can try StackOverflow though.
- Emulator with Play Services blocking internet.
You may want to request help for this from the Play Sevices Forum as we can only support integrating the Mobile Ads SDK into apps.
- Adult content showing in ads where all adult categories are blocked (reported by few users, not just one).
Ad serving issues are supported by the AdMob Forum.
- Firebase library keeps trying to run even if disabled.
Are there any performance issues that are occurring because of this? We would like to address any crashes or performance degradations when using our SDK.
- dynamite analytics crashing after every ads (reported in another conversations).
Please give us a reliably reproducible method for causing this crash so we can address it.
- no issue tracker for AdMob, as if there was no single issue lol
Could you elaborate on how and why you would like support to be configured? Are you referring to Github Issue Tracker?
Feel free to reach out to us. We would like to see a Charles log of the misbehaving ad sent to us by "Reply to author"
Regards,
|
||||||
|
||||||
|
||||||
Hi,
Your issue has been escalated to the Mobile Ads SDK engineering support team.
We understand your concern here and as you have pointed out it does seem that certain ads are causing more than expected CPU usage when the app is in the background. The screenshot you provided of the Ali Express promotion seems a relevant example.
As you no doubt are aware this is a confluence of factors including AdMob, webview and certain ad creatives so capturing the relevant variables that lead to the issue reproducing is the most effective way to resolve the issue. An effective way to identify a specific ad is via the response ID - https://developers.google.com/admob/android/response-info. If you were able to capture the response ID of a specific ad that reproduces that may be enough to assist us in isolating the issue. A charles log capturing the response would also be helpful. Finally it would be helpful to know the version of webview running on the device.
I'm sorry we aren't able to resolve this issue more expediently but the more information we have the quicker we should be able to isolate and reproduce the issue. I have created an internal issue for this (b/173473357) to follow up with the SDK engineering team. It appears to be similar in nature to this webview issue - https://bugs.chromium.org/p/chromium/issues/detail?id=900557 which has been resolved, however I imagine this is a new occurrence.
Regards
Sam
Mobile Ads SDK support team