I'm trying to set up crashlytics beta app distribution process.
I have two schemes of building develop-variant of our app: rocket:myapp_developDebug and rocket:myapp_developRelease (names slightly changed). I have them both built and located in same output dir.
If I run rocket:crashlyticsUploadDistributionMyapp_developDebug, everything is ok and I see that distribution on Crashlytics Beta page. But for rocket:crashlyticsUploadDistributionMyapp_developRelease it succesfully finishes 'build', but app doesn't get its way to Beta.
From its message Uploading /path/to/project/proj.android-studio/app/build/outputs/apk/rocket-myapp_develop-release.apk to Crashlytics... it's clear that I have that apk; also it is really being uploaded (based on time and network load). The version itself is recognized by Crashlytics (on versions page).
What am I missing?
I am developing an Android game and currently trying to integrate with Google Play Game Services. I got stuck at the sign-on feature.
I use GoogleSignIn, getIntent, startActivityForResult etc. - all as described in Google manual. I think all's setup correctly, because when I build the app, deploy to Google Store (Internal Tests), and then I install it from there, all looks good: onActivityResult is called with result.isSuccess()==true and GoogleSignIn.getLastSignedInAccount returns != null.
The problem is when I try to run the app from Android Studio (or install APK manually). In this case, onActivityResult is called with SIGN_IN_REQUIRED and getLastSignedInAccount is always null. I am pretty sure all's setup fine (APK is signed, Android Studio is configured to sign the APKs etc.).
To ensure it's not about my Android Studio setup, I have installed manually exactly the same APK which I uploaded to Google Store but again - result is the same. When installed from Google Store, it's OK, when installed manually it's not (again: exactly the same APK binary).
Can you please help me? Theoretically I could continue development, but each I'd like to test something I'd need to upload new version to Google Store...
Thank you
Hmmm...its usual DEVELOPER ERROR, what you can do it..add your SHA1 code on firebase console, and it will work, it is showing this behaviour caus your signed key SHA1 is already added, that why it is working on release build and not on debug build, add your systems SHA1
How to get SHA1?
usually right side of android studio have a bar which says gradle click on it, expand it got to app>Tasks>android>signing report double click it...it will give you your SHA1, paste it on firebase console, wait for 1-2 minutes and check. It will work.
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 am using Android Studio 1.5, Fabric Plugin 2.3.1. What possible reasons would Fabric not allow me to login?
The whole process is completely knackered. Any Fabric link I visit including the organization settings link located here directs me to the on-boarding link where all I can do is view instructions on how to download the plugin. I have installed the plugin, login and I see the list of Fabric components for about 2 seconds before it brings me back to the login screen with no message at all.
The credentials are fine (incorrect credentials give me an orange message saying so). I have tried it with 3 different accounts.
So now I am in a situation where I have 3 accounts, all of which only allow me to view instructions on how to download the plugin, and the plugin will not let me get further than the login screen. I could do this manually but cannot access the organization settings screen either. Any ideas?
EDIT: This is the closest similar issue I could find on their forums but it relates to a Mac (I'm on Windows 10, Java version jdk1.7.0_79)
What fixed it for me was adding the authKey to the application block in the main manifest.
NOTE: at the time of this issue, I am using Android Studio 2.0 Beta 6. We believe that there might be an issue with the Fabric plugin and this version.
To see what's happening to the Fabric plugin, I had to open the Console app and view the logs in realtime. Sure enough, it showed that was authenticated with my credentials, AND it passed back the reason I was being sent right back to the login: Missing authkey in the application block.
So I copied an authkey node from a previous project and added it to the manifest and bingo - it took me to the screen to install Crashlytics.
The thing is, I could have sworn that the Plugin was supposed to GIVE me the authkey after it installed Crashlytics, so I was a bit puzzled as to why this worked. But it did.
Again, this is with Android Studio 2.0 Beta6 so it might be only related to that. But using the Console to diagnose the issue with the Fabric Plugin is the take away here.
Download the fabric plugin for android studio via jetbrains.com using your prefered browser(i.e mozilla,chrome etc).
after your file get downloaded(not via andriod studio), open your AndroiStudio, goto --file>>settings>>plugin>>install plugin from disk, give the .jar file which you have downloaded, then restart studio
We have followed the instructions at http://developer.android.com/google/play/billing/billing_testing.html#billing-testing-real to introduce in-app billing to our application, and now want to add our live product IDs.
As per the instructions, we build our APK with the necessary permissions and sign the APK. Once the upload is complete, we get the following error :
"This configuration cannot be published for the following reasons : All devices that might receive version 3001 would receive version 3002."
We do NOT want to publish this APK, but only upload it as a Draft APK, in order to complete testing of IAP.
Does anyone have a workaround to this?
I was able to work around this problem by switching back to the old version of the Developer Console and then deactivating my one older version, after which I deleted that older version and saved the app. Upon returning the the new version of the Console, the problem was resolved.
However, I believe the old version of the console will soon become unavailable, so this approach may not be available much longer.
Deactivate the old version first and then you should be able to publish the new version of the app.
Switch to the old version and update the new apk...
It works for me.
Thanks Carl