Currently I am upgrading MoPub in Android from 4.8.0 to 4.11.0. When I am debugging the app, ads are shown fine. When I generate a signed apk and deploy to a device, no ads are shown. All I did is change the dependency version. What can be the reason for this? Even upgrading it to 4.9.0 doesn't work
(note debugging the apk, ads are shown perfectly fine. When signing it, no ad events are being triggered like onBAnnerLoaded or onBannerFailed).
you can debug in two ways
1) In ADB logcat or console in Android studio , do you see the Ad call being made ? you can use a proxy Fiddler/Charles to see if your app is actually making the Ad call Or you can simply use the console in Android studio to look at the logs.
2) In the logcat look for the debugging information. In my App it looks like this, if there is an issue with loading it tells me Ad failed to load.
23:25:28.738 MoPub D Loading url:
http://ads.mopub.com
23:25:29.453 I Ad failed to load.
OR
23:25:29.453 I Ad loaded successfully.
Note: If you are unable to see the Ad call in the proxy or console then this points to a problem in your implementation.
Related
I'm implementing ads with Unity LevelPlay.
I followed everything in the documentation and installed these adapters:
ironSource 7.2.6
UnityAds 4.3.29.1
When I test on device, I have two different errors in these situations:
If I make a local build and install it immediately using "Build & Run", the game starts, but the call to IronSource.Agent.init(appKey) ends up with INIT_FAILED. Everything else in the game keeps working except for ads.
If I upload the build on Google Play Console for internal testing and install from there, the game doesn't even start and crashes immediately complaining about Google AdMob not being initialized correctly. I don't understand why as I'm not even using AdMob adapter.
You can see both errors in the attached screenshot, unfortunately not being very explicative.
Why could I be getting these errors and what can I try in order to solve them?
Unity Version: 2020.3.42f1;
LevelPlay Version: 7.2.6;
Unity LevelPlay compatible with Unity version 2021.3
I'm creating a project with the newest admob version, and I'm using admob test ids for testing ads:
https://developers.google.com/admob/android/test-ads
App id --- ca-app-pub-3940256099942544~3347511713
Banner --- ca-app-pub-3940256099942544/6300978111
Interstitial --- ca-app-pub-3940256099942544/1033173712
Something isn't work properly, because both formats are giving me error:
onAdFailedToLoad() error code: 3 - No ad config.
onAdFailedToLoad() error code: 3 - No ad config.
How can I display test ads? why the official test ids doesn't works? I'm testing in emulator with android 13 and in real Pixel XL device with android 10. Same problem in both.
Well, I'm not sure if this is a definitive solution or someone will post something better in the future, but I achieved to see test ads signing the apk with release key and using the test ids from google, then installing that signed apk on a real device.
This is extremely frustrating, test ads should be displayed in android studio when simulating...
I have transferred my flutter app project from my old computer over to a new one. Since then I have not been able to load AdMob ads in my app.
This is the error I'm getting:
LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: []))
I have seen similar questions with answers pointing at problems with signing the app. I have the key.properties file, and build.gradle set up as per Google's manual. I'm using my old key file I had previously generated on the old computer (is this the right way to do it??? or do I need a new file?). Still, only test ads are working. When I try using the real AdIDs, I'm getting the above message.
Before the transition to the new computer, everything worked just fine. Has anyone had this problem? Have I missed anything while moving the project?
In case it matters, I moved from a Windows laptop to a MacBook. I'm using the latest Flutter and Android Studio, as well as the latest version of the google_mobile_ads package.
It seems Google has updated the SDK so that read ads are served only to apps signed with the Play Store key. This means they will only appear after the app is published and installed from the Play Store.
What I want?
I have an Android App that I want to upload to Fabric Beta.
How do I want it ?
I want to upload my Android App to Fabric Beta using Fastlane.
What goes wrong ?
After running my fastlane fastlane beta command, I get a nice report that everything is fine and I should see my app on Fabric dashboard:
[16:06:57]: Uploading the build to Crashlytics Beta. Time for some ☕️.
[[16:07:03]: Build successfully uploaded to Crashlytics Beta 🌷
[[16:07:03]: Visit https://fabric.io/_/beta to add release notes and notify testers.
But when I go https://fabric.io/_/beta, my app DOES NOT appear there !
What else did I try?
Tried the official integration doc. Installed the Fabric plugin on Android Studio.Logged in with my credentials,selected my app bundle identifier and always get throwed to credentials screen from the "All Kits" screen.Looks like a bug to me.Didn't find solution for that anywhere.
Did I try to integrate Fabrik SDK by hand and run the app ?
Yes I did, and the app still didn't appear in the Fabric dashboard.Didn't see any related errors in the logcat.
What about uploading using Gradle Plugin?
That one was tricky because I had to fix numerous errors and provide fabric.properties file with my credentials, but eventually got a promising message :
Task :application:crashlyticsUploadDistributionGoogleProdStagingAlpha
Uploading /Users/yanbraslavsky/booking-app/application/build/outputs/apk/googleProd/stagingAlpha/application-google-prod-stagingAlpha.apk to Crashlytics...
BUILD SUCCESSFUL in 6s
And still no app in the Fabric dashboard.
What do I want now?
I have an Android App that I want to upload to Fabric Beta...
Fabric/Firebaser here -
This issue was solved over the Fabric support channel! When attempting to upload a Beta distribution to Fabric, first make sure that the app is onboarded properly (visible on your dashboard at fabric.io). If it isn't, the above can happen where you still get a successful upload result without being able to view the distribution.
If you've included all the Fabric dependencies and are still having trouble seeing the app on your dashboard, try running a clean of the project, then building, waiting some time, and running the app. If you still can't see the app after a few minutes, reach out to the Fabric support address with your package name/bundle ID.
Also make sure that your build.gradle is properly configured if you have multiple build configurations. In this particular app, the issue was in the applicationIdSuffix of one of the build configurations. Finally, check that you've used the correct API key and build secret from the Fabric organization settings - this ensures that you have permission to upload the Beta distribution and puts it in the right place.
Hello I am using appcelerator studio version 7.1.1.GA and am porting an iphone app to android for a client. I tried a bunch of things but am unable to get admob ads to show up in the app and the error message I get is ==>
[WARN] : Ads: Invoke Firebase method getInstance error.
[WARN] : Ads: The Google Mobile Ads SDK will not integrate with Firebase. Admob/Firebase integration requires the latest Firebase SDK jar, but Firebase SDK is either missing or out of date
I am using version 2.2.0 of the 'firebase.core' module, version 4.0.0 of the 'ti.admob' module, version 11.0.40 of ti.playservices (whatever is included with Appcelerator Studio I believe) and version 4.2.0 of the 'ti.map' module. I am also using version 2.0.0 of the ti.googlesignin module. Everything else the map and google signin work fine. I tried a bunch of different things including ti.playservices, not including it and also when I had version 4.1.0 of the 'ti.admob' module installed I was getting dexer linking errors which did not seem right and when I reverted to the 4.0.0 version of 'ti.admob' the linker errors went away.
This is the last thing I need to do to release this app to the Google Play Store I have managed to get everything else is working but it would be a bummer not to have ads in the app. I really don't want to disappoint my client.
I figured out what the issue is. It is real simple I just had to pass the ad unit id in as the publisher id in Admob.createView({ publisherId: 'ad unit id', ... }); Talk about confusing!