module com.google.android.gms.piccard.dynamite not found - android

I'm using Google Play Services ads-lite v.9.2.1.
When requesting Admob ads, the following is written to logcat:
W/DynamiteLoaderImpl(): Failed to load module version: module com.google.android.gms.piccard.dynamite not found
D/GmsModuleFndr(): Staging file APK's and updating chimera config...
D/GmsModuleFndr(): Staging file APKs completed
W/DynamiteLoaderImpl(): Failed to load module version after staging: module com.google.android.gms.piccard.dynamite not found
W/DynamiteModule(): Local module descriptor class for com.google.android.gms.piccard.dynamite not found.
I/DynamiteModule(): Considering local module com.google.android.gms.piccard.dynamite:0 and remote module com.google.android.gms.piccard.dynamite:0
E/AppStreamingHelper(): No acceptable module found. Local version is 0 and remote version is 0.
Test ads load and display fine.
Is that module com.google.android.gms.piccard.dynamite needed for live ads?

It is against AdMob policy to click on your own live ads. During development and testing, use test ads. If you do need to render live ads before launch, avoid clicking on them. If you click on live ads, your AdMob account may be suspended. For more information, review the AdMob policies and learn more about invalid activity.
Google treats invalid activity very seriously, analyzing all clicks and impressions to determine whether they fit a pattern of use that might artificially drive up an advertiser's costs or a publisher's earnings. If we determine that an AdMob account might pose a risk to our advertisers, we may disable that account to protect our advertisers' interests.
Publishers disabled for invalid activity or violating our policies may not be allowed any further participation in other Google publisher monetization solutions.

Related

Android: Providerinstaller module and updating security provider

I am checking id the security provider is installed by calling
ProviderInstaller.installIfNeededAsync
I wanted to test the case where update fails. So I had the device offline so that it will not be able to update the security provider. But I see these logs
com.xxx.debug W/ProviderInstaller: Failed to load providerinstaller
module: No acceptable module found. Local version is 0 and remote
version is 0.
2020-07-15 16:11:07.244 10334-10435/com.xxx.debug
I/ProviderInstaller: Installed default security provider
GmsCore_OpenSSL
What does these logs mean.
I see these logs every time installIfNeededAsync is called, which makes me think that there is no actual install happening.
I see that onProviderInstalled callback is getting called which means the services is updated. But then why should these logs come every time?
Is there a way to test the scenario where the provider is outdated.

Admob telling me show test ads on release build

I am trying to release a new version of my app.
The older version can still display ads, but my newer version (release build, not debug)
cannot show ads. I am getting the following error:
2020-03-03 01:54:42.351 7098-7098/? I/Ads: Use RequestConfiguration.Builder().setTestDeviceIds(Arrays.asList("457B729F085881806B918663EF07468C") to get test ads on this device.
2020-03-03 01:54:42.442 3275-7238/? W/Ads: App does not have the required permissions to get location
2020-03-03 01:54:42.517 3275-7485/? I/Ads: SDK version: afma-sdk-a-v20088999.19649000.1
2020-03-03 01:54:43.174 7098-7098/? I/Ads: Ad failed to load : 3
Any way to tell the Admob SDK that the current build is a release build?
one more step you can do,
as you see in your log this code Use RequestConfiguration.Builder().setTestDeviceIds(Arrays.asList("457B729F085881806B918663EF07468C") to get test ads on this device.
with your device id is: 457B729F085881806B918663EF07468C
now before intilization you can add the following:
RequestConfiguration configuration = new RequestConfiguration.Builder().setTestDeviceIds(Arrays.asList("457B729F085881806B918663EF07468C")).build();
MobileAds.setRequestConfiguration(configuration);
any body else reading this solution should change the device ID.
reference here
Short answer: just wait for some hours till people start downloading and using the app.
Actually the log messages don't mean that I had to run test ads. It seems admob was not just showing ads until some people downloaded my app and started using it.
Once I published the update, I had to wait for 6-7 hours after which ads started showing.

Firebase Analytics events don't show up (Android)

I have an issue with Firebase Analytics. It basically boils down to the fact that nothing is registered; I have no data in my analytics page in the console.
I noticed today that when I want to send a push notification and I set a filter for the version number of my app, it shows "No versions available for this app". However, my iOS version of the app IS showing a version number in the dropdown list.
Does anyone have an idea what the issue is?
Some other issues I'm still experiencing:
"Firebase API initialization failure." IncompatibleClassChangeError ContextCompat.getNoBackupFilesDir() -> InvocationTargetException
Failed to load module descriptor class: Didn't find class "com.google.android.gms.dynamite.descriptors.com.google.firebase.auth.ModuleDescriptor"
Many thanks in advance.
the failed to load is not the problem, i have it too when using firebase-invites and i found this (Failed to load module descriptor class: Didn't find class "com.google.android.gms.dynamite.descriptors.com.google.firebase.auth.ModuleDescriptor")
the "Firebase API initialization failure." IncompatibleClassChangeError ContextCompat.getNoBackupFilesDir() -> InvocationTargetException
was fixed by updating the google services in the device

Add Facebook Audience Network Mediation to application

I am using Eclipse and I try to show ads via the Facebook Audience Network. I have added the "AudienceNetwork.jar" from the official Facebook SDK, and the "FacebookAdapter.jar" from the AdMob Mediation Networks.
I should mention that I monetize via the AdMob and do not use proguard.
My problem is that when I try to load ads, I get the following error:
02-19 20:07:35.315: I/Ads(23957): Instantiating mediation adapter: com.google.ads.mediation.facebook.FacebookAdapter
02-19 20:07:35.316: I/dalvikvm(23957): Failed resolving Lcom/google/ads/mediation/facebook/FacebookAdapter; interface 1798 'Lcom/google/android/gms/ads/mediation/MediationInterstitialAdapter;'
02-19 20:07:35.316: W/dalvikvm(23957): Link of class 'Lcom/google/ads/mediation/facebook/FacebookAdapter;' failed
02-19 20:07:35.316: W/Ads(23957): Could not instantiate mediation adapter: com.google.ads.mediation.facebook.FacebookAdapter. com.google.ads.mediation.facebook.FacebookAdapter
According to this and this post, this should happen only if I used proguard, which I don't.
Does anyone has a suggestion on why this happens?
And why doesn't the Facebook itself have any documentation on how to integrate the Audience Network via AdMob, since the first is supported by the latter one? :-)
It doesn't look like com/google/ads/mediation/facebook/FacebookAdapter is contained within your APK. Check your APK, your build process, how you have added the FacebookAdapter library and the contents of the FacebookAdapter library itself.
I tried with a banner ad. Wanted to load ads from Facebook Audience Networrk through Admob mediation when I ended up with the same error.
Please make sure you added the Google Play Services Lib to your build path and check if your version of the Google Play Services Lib contains the MediationInterstitialAdapter.class and the MediationNativeAdapter.class. Mine did not (still working with eclipse) and so the FacebookAdapter was searching for a class that was not there.
After updating to a newer version (links here: How to download older google play services?) the mediation now works fine for me. :)

Android failing to download obb file using unity

I have a unity project for android which is larger than 50MB and so must be split. I have had working apt splitting for a couple months now. Starting a few days ago I mad a couple changes which were purely aesthetic. I uploaded the new build and now(days after the api and obb files were uploaded) I receive an error at the download point on the device "Download failed because the resources could not be found."
I manually added the obb file to the device and it worked, I have tried re uploading the apk and bob files with minor changes and still after a day of waiting see the same errors.
viewing with logcat I see these errors when i try to download
I/LicenseChecker(20270): Binding to licensing service.
W/ContextImpl(20270): Implicit intents with startService are not safe: Intent { act=com.android.vending.licensing.ILicensingService } android.content.ContextWrapper.bindService:517 com.unity3d.plugin.downloader.c.j.a:-1 com.unity3d.plugin.downloader.b.s.run:-1
I/LicenseChecker(20270): Calling checkLicense on service for [my project com]
I/LicenseChecker(20270): Start monitoring timeout.
W/GLSUser (26959): GoogleAccountDataService.getToken()
I/qtaguid (18936): Failed write_ctrl(u 53) res=-1 errno=22
I/qtaguid (18936): Untagging socket 53 failed errno=-22
W/NetworkManagementSocketTagger(18936): untagSocket(53) failed with errno -22
I/ElegantRequestDirector(18936): I/O exception (org.apache.http.NoHttpResponseException) caught when processing request: The target server failed to respond
I/ElegantRequestDirector(18936): Retrying request
I/LicenseChecker(20270): Received response.
I/LicenseChecker(20270): Clearing timeout.
Its not obvious to me what I did to make obb downloading stop working. I don't know enough about the error messages to pick anything out of it.
What can I do to make it download the bob files again?
In case anyone else runs into this here was my solution. It looks like Google made a policy change.
"To test your application's implementation of the manual download procedure, you can publish it to the alpha or beta channel, so it will only be available to authorized testers. If everything works as expected, your application should begin downloading the expansion files as soon as the main activity starts.
Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported; instead, you must publish it to the alpha or beta distribution channel. For more information, see Draft Apps are No Longer Supported."
so now you need to publish your alpha/beta builds before you can download the files.

Categories

Resources