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.
Related
I have an app that I developed wow like 8 to 10 years ago, but I have been updating it constantly at least once a year or so.
I'm actually in the process of completely redoing the app from scratch, and it's working great when I run it on my Android from my computer, but when I build it with a signing key on PhoneGap Build, I get the error message "App Not Installed." when I try to install the apk.
I've read through several other posts on the topic and I can attest:
I have plenty of storage space on the phone.
The new version number is larger than the old version number.
The signing key is the same as the original version.
I do not have any version of the app currently installed on my phone.
Any other ideas on what may be causing this?
I've removed all my plugins to take that out of the equation, but I still get the same error.
The original app was build with OnsenUI and Cordova.
The new app is build in Ionic 5.4.16, Cordova 9.0.0, and Android 8.1.0.
Something else I have noticed is that if I change the app id (com.company.appname) to anything else (i.e. com.company.appnamedev), it installs. I feel like this is very indicative of the issue, but I don't know what to do with it.
Very much appreciate any guidance to finding the problem.
Unfortunately this isn't going to be the answer many of you solution seekers are hoping for, but I got it to work. Based on Mike N.'s suggestion, I attempted to sign it locally and push it to my device with adb. In doing that, I was having trouble with remnants of two older plugins (onesignal and admob) that I had already removed from my config.xml file.
I'm really not sure why, but after I got rid of those old pieces in my package.json, I attempt to push it to phonegap build again and it was able to install. So, I guess the solution would be to make sure you have fully removed any plugins that may be causing problems.
Now the big trick - adding these pieces of functionality back in. But, the app compiles on PhoneGap Build and the signed file installs on my device now.
UPDATE: So, it turns out this is directly related to the one signal plugin I'm using. Still figuring out why, but when I added it back in, it works great locally, but when I attempt to build with PhoneGap Build and load it to my phone, I get the error "App Not Installed." At least I know what's causing it now.
I finally figured out the root of all my issues. As it turns out, I had another half baked app I started and had on my phone under a different name and app identifier, but I had temporarily dropped the same google-services.json and GoogleService-Info.plist files into that other app that I use for the one in question here.
After employing Mike N's suggestion, I got the error:
adb: failed to install mynewapp.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.company.new attempting to redeclare permission com.company.new.permission.RECEIVE_ADM_MESSAGE already owned by com.company.old]
I uninstalled the old app that should not have had those files to begin with and everything installs and works great now. Hopefully this helps someone else out who encounters the same bizarre situation.
You can use My APK application and installing an apk using My APK Installer (MAI).
If there is an error, it will show the detail (like duplicate permission, provider, mismatch signature,...)
I am a little new to Android development.
I have a hybrid app which uses Apache cordova plugins.
I am using eclipse to generate the APK.
But when I publish the APK, the Google play store rejects it saying:
APP UPDATE REJECTED
Your APK has been rejected for containing security vulnerabilities, which violates the Malicious Behavior policy. The Alerts page has more information about how to resolve the issue. If you submitted an update, the previous version of your app is still live on Google Play.
And, when I click on the alerts page the following error shows up:
Security alert :
Your app is using a version of Apache Cordova containing one or more security vulnerabilities. Please see this Google Help Center article for details, including the deadline for fixing the app.
I have already tried the followings:
Update the android platform (cordova platform update android), but no positive results.
I could not update all the cordova plugins as I am getting errors. (wanted to know can this be the issue)
I am building this APK using the Eclipse IDE and I went through this ADT plugin release note https://developer.android.com/studio/tools/sdk/eclipse-adt.html which says: The Eclipse ADT plugin is no longer supported
Eventually I will be importing my project to Android studio but I want an app update immediately thats why still using Eclipse.
If Eclipse is the reason then I immediately need to import my app to Android studio.
I want to figure out that which one of the last two point is responsible for my app rejection.
Also, if none of these are responsible then what could be the possible reason for my app rejection.
Thanks in advance.
An APK is an APK, regardless of where you developed the code. You can write the code in Eclipse, Android Studio, or you can write the code in your favorite plain text editor. The end APK will be indistinguishable regardless of which editor you use.
The error in this case seems to be pretty clear- your version of Cordova has known vulnerabilities and you need to update that.
Run cordova platform version android to check your version. The error message you are receiving will show for anything less than 4.1.1.
The best path would probably be to upgrade to 5.x, as detailed here.
I've found the following error when running my android application in android studio. app couldn't get installed on my device because of this error. Didn't find the solution :(
please help
Auth: [GoogleAccountDataServiceImpl] getToken() failed.
Status BAD_AUTHENTICATION,
Account: ,
App:com.android.vending,
Service: androidmarket com.google.android.gms.auth.be.account.b.d: Long live credential not
available.
I had the same issue what helped me was that I had wrong credentials in my google-services.json file and after getting a new file my problem was fixed.
in the process of resolving this issue I also updated my google play services but I do not think this is necessary .
I got this error when tried to install app directly from Android Studio.
It was due to certificate mismatch, since I used release certificate for setting up the app in Play Console, while Android Studio signs the app with debug certificate by default.
Installing app via adb resolved the error.
https://developers.google.com/games/services/android/quickstart#step_4_test_your_game
Make sure to run an APK that you exported and signed with a
certificate that matches one of the certificates you used during the
application setup in Google Play Console.
I have the same problem some days ago. I just compile my whole code in a new project and Problem Solved!!.
Don't know what was the real problem. There is an issue filed here, with no solution.
There are several reasons you can get that message:
The account you are trying to log on with needs to be re-authenticated on the phone (try a different account)
The gms:play-services version is out of date (needs to be 15+ as of Jan 2021)
Your app fingerprint is not the right one. You need one for dev builds, different one for prod -- which is different based on how you sign (do you have the final publish key, or does Play store re-sign with the final publish key?)
Follow the Google tutorial and get their stand-alone project, it should take 20 min, and check your setup there. If you are running it with all the right accounts it should work. Then go back to your app.
https://developers.google.com/identity/sign-in/android/start
I updated Google Play Services on my phone and stopped receiving the same error. I am importing com.google.android.gms:play-services-cast:9.6.1 and analytics:9.6.1. Not sure if the version running on the device was too low but problem is now resolved but not sure how to prevent this error for users running older versions of Google Play Services.
Tested the other solutions but nothing worked. Rebooted the device and error was gone.
If you using firebase server, As per the firebase updation if you give phone number authentication put your country code before contact number it is mendetory.
example - +91 9999998888
This happened to me, auth errors in ADB, among them:
android Warn Auth [GoogleAuthUtil] GoogleAuthUtil
Because, like mentioned above, I had a debug build running on phone previously. So I fully uninstalled the app on my phone, and the next [Build and Run] ran successfully.
Please try the App with new google credentials or even try creating the whole peoject on console og google play services if you have used it .
In my case it was a dependency version problem. I had to update the auth dependency for firebase to the latest one:
implementation 'com.google.firebase:firebase-auth:17.0.0'
Here is my take towards this problem:
You may be using a single email to try and log in to google. It may be possible you might have changed the password of the particular email in the recent past. Make sure u remove your google-email from your phone/emulator. When u re-run your application, you will be asked to enter both email and password credentials.
Check if your credentials.json is still valid. Sometimes its possible that your client ID might be removed/corrupted if you have not used your android application for a long time. Make a new one and dont forget to copy-paste it in app folder of Android Project view.
PS: I am new to Android Studio and writing answers on stackoverflow in general. If you are reading this comment please let me know what improvements i can make while answering questions in the future.
I copied and ran the code in a different project that had priorly worked on simple DB operations of Firebase. Probably it already had the authentication files in place so launching the app was solved there
Mostly your token has gone bad. And needs a new one.
Go to project database > settings > General > download Json file and replace it with the one in the local project directory.
I fixed this problem with updating fingerprints (sha1 or sha256)
My problem was with Microsoft App Center.
We recently set our pipelines to send aab files to App Center, instead of apk files.
It seems that our bundle was resigned by App Center with some generated keystore. That's how App Center distributed apk files, even though our pipeline uploaded aab files.
In other words: even though our pipeline is using our own keystore to sign the aab bundle, in order to distribute through the App Center, after sending the aab to App Center, the App Center is creating universal apks with another generated keystore.
After rolling back our pipeline to send apk instead of aab, Google SignIn on our react-native app with firebase was working again.
"When you distribute Android Application Bundle (AAB), App Center generates a universal APK, signs it with a generated signing key, and distributes it to a device."
Source: https://learn.microsoft.com/en-us/appcenter/distribution/uploading
I published yesterday a Cordova application on the Android market (aka Google Play Store) and I noticed a weird bug that I can't reproduce in dev environment.
In fact, all the HTTP requests seem to be blocked by the application (The Ads won't show, the inline images in the articles won't show, the video won't load, etc).
I properly set the access origin to "*" in my config.xml file and when I take a look at the app permissions I see it can receive information from the Internet. Of course the application works properly when I build/install it from my computer.
Also I don't see how I could fix this or even start debugging it.
Have you got any idea how I could debug this ?
Thanks
NB: The apps works great on iOS devices (dev and prod)
I solved my issue.
The problem was that I removed the plugin jsHybugger (before building and signing the app) with the following command
cordova plugin rm org.jshybugger.cordova
and did not regenerate the android platform afterward.
So I just did
cordova platform rm android
cordova platform add android
and all went fine.
Apparently Cordova keeps some files of plugins even after they're removed from the project. I guess those jsHybugger calls where making something crash on my app (because the plugin wasn't there anymore)...
NB: To debug the production version of my app, I simply installed the corresponding apk (found in platforms/android/bin/MY_PROD_APP.apk) on my phone (the one I sent to Google Play Store)
I'm using unity android, and I'm trying to upload my app.
It's a 80Mo app, so I had to split it.
Here is how I set up the Other Settings in player prefs (unity3d):
Bundle identifier: com.CompanyName.APKName (that's an example obviously )
Bundle Version: 1.0
Bundle Version Code: 1
Minimum API: (lowest) 2.0.1
Device filter: Armv7 only
Install Location: Prefer Extern
Graphics Level: OpenGL ES 2.0
Internet: Auto
Write Access: Internal only
API: .NET 2.0 subs
The product name is different than the APK name.
My files are named:
- APK: APKName
- Expansion file: main.1.com.CompanyName.APKName
In the build settings, nothing is changed (Development Build is still False).
(I'm not using a patch file).
My problem is that when I upload the APK Expansion file, it gets stuck on "processing". Apparently it's an internal error that occurs, and google play is failing the upload but doesn't display anything on the screen. I've been trying to upload that for days now and I can't find anything that helps online.
EDIT: On chrome I get stuck to processing and with firefox, I get stuck to 99%...
I've see theses post StackOveflow post 1 StackOverflow post2 but nothing changes for me.
I'm following this tutorial: tutorial unity to google play
EDIT: I can't access my app through the old console... I get the following message:"Failed to load application list. Try again later."
Thanks for the help
Boris
Ok I did it!!!
I had to create another version of my app with a higher version number. Then I went to the old console, as my app wasn't accessible through the old console I had to upload again my first APK by clicking on upload apk. Once uploaded the old console shows an error saying that there is already an app with that package name. After closing the error message the app is accessible through the old console and therefore from there I was able to upload my version 2 (the new one) APK + main OBB. After that, from the old console, I deactivated the old version and deleted it. I went back to the new console design and this is it !!!!
Sorry for posting with a second account I'll delete the first one.
if you keep example work in you application package name you cannot upload apk into google play..