Problem
I have just created an update for one of my Xamarin.Forms apps and now I have the problem that the Firebase sign-in workflow is suddenly broken after uploading the new .aab to Google Play. It has been working fine until now.
When I attempt to sign-in, the following error message appears in the device log after selecting the Google user account:
Time Device Name Type PID Tag Message
11-18 16:49:57.295 Samsung SM-S901B Verbose 5646 mono-stdout com.google.firebase.FirebaseException: An internal error has occurred. [ Instantiation of JsonResponse failed! class com.google.android.gms.internal.firebase-auth-api.zzaac ]
at com.google.android.gms.internal.firebase-auth-api.zzwe.zza(com.google.firebase:firebase-auth##21.0.8:4)
at com.google.android.gms.internal.firebase-auth-api.zzxc.zza(com.google.firebase:firebase-auth##21.0.8:9)
at com.google.android.gms.internal.firebase-auth-api.zzxd.zzl(com.google.firebase:firebase-auth##21.0.8:1)
at com.google.android.gms.internal.firebase-auth-api.zzxa.zzh(com.google.firebase:firebase-auth##21.0.8:25)
at com.google.android.gms.internal.firebase-auth-api.zzwc.zzh(com.google.firebase:firebase-auth##21.0.8:1)
at com.google.android.gms.internal.firebase-auth-api.zzua.zza(com.google.firebase:firebase-auth##21.0.8:2)
at com.google.android.gms.internal.firebase-auth-api.zzxl.zzb(com.google.firebase:firebase-auth##21.0.8:13)
at com.google.android.gms.internal.firebase-auth-api.zzxl.zza(com.google.firebase:firebase-auth##21.0.8:14)
at com.google.android.gms.internal.firebase-auth-api.zzwr.zzq(com.google.firebase:firebase-auth##21.0.8:4)
at com.google.android.gms.internal.firebase-auth-api.zzuh.zzA(com.google.firebase:firebase-auth##21.0.8:4)
at com.google.android.gms.internal.firebase-auth-api.zzwd.zzu(com.google.firebase:firebase-auth##21.0.8:5)
at com.google.android.gms.internal.firebase-auth-api.zzvj.zzc(com.google.firebase:firebase-auth##21.0.8:1)
at com.google.android.gms.internal.firebase-auth-api.zzxe.run(com.google.firebase:firebase-auth##21.0.8:1)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
This only affects the Release build which is signed by Google Play and therefore, I cannot replicate this in the debugger. When running the debug version, everything works as expected.
Additional Info
Android Version: 13.0
Android Target API: 33
NuGet Packages (only seemingly relevant ones shown):
Xamarin.Forms 5.0.0.2515
Google.Apis 1.57.0
Google.Apis.Auth 1.57.0
Xamarin.Firebase.Auth 121.0.8
Xamarin.Firebase.Common 120.1.2
Xamarin.GooglePlayServices.Auth 120.3.0
I am using the Google Sign-In button in my Android activity and I am not using the Web Authenticator (yet).
I use Android App Bundles (.aab) for publishing instead of uploading .apk files.
What I've tried so far
I have checked all SHA certificate fingerprints (for Debug and Release builds as well as the signing certificate in my keystore and the one used by Google Play to sign the release) against the ones in the Firebase Console, google-services.json, Google Cloud Console and also the application restrictions for my Android API key.
Debugging does not yield the same outcome, so I've only managed to use the device log to get to the exception shown above.
Apart from that, I have upgraded to the latest versions of the Google and Firebase Auth libraries for Xamarin.Forms.
I'm a bit at a loss now. Does anyone have any suggestions on how to narrow this further down or has anyone experienced this problem before?
It works again.
The issue was unrelated to the signing certificates (which is usually the first go-to for these kind of problems) and the libraries that are being used.
This problem was actually caused by a small optimization which was causing the code shrinker to remove some Firebase related code. Disabling the code shrinker (temporarily) solved the issue.
My Problem:
I'm still receiving the INSTALL_PARSE_FAILED_NO_CERTIFICATES error after creating the necessary keystore, key and signing my application. This error initially occurred after updating the minSdkVersion version to 24 for needed functionality, but it still occurs after completing the resolution. I'm not sure why exactly.
What I have done:
I have followed the wizard procedures (see links below) for creating a signed release of my app currently in development, creating the keystore, key, password, signing the app, etc, etc. I've read a number of posts here but nothing appears to address my issue specifically - that I have found so far. Only how resolve the initial reason for the error -- not having a signed app.
What haven't I done is the Google Play app signing. I didn't think this was necessary until I'm ready to move the app there and I may not actually ever offer it there.
Any thoughts or help would be appreciated as my app development is now dead in the water until I resolve this issue.
I followed all the steps here:
https://developer.android.com/studio/publish/app-signing - Steps 1 and 2 specific to signing your app.
https://www.jetbrains.com/help/idea/extracting-a-signed-android-package.html
I solved my problem. My emulator device version was not compatible. Once I setup a new emulator device meeting the minimum version, the app began to install successfully. So increasing the minSdkVersion caused my emulator device to be incompatible.
I am trying to purchase using a beta tester but i am getting this error.
This is an error that shows in google play window, after passing initial validations and after the user press subscribe button, so i guess it is not an code or configuration error.
Anyway i checked this link https://stackoverflow.com/a/22469253/2700303 and also downloaded the app from the store.
I check the "Learn more" link that comes with the error but nothing on that troubleshooting page helped.
The account used as a valid and active pay method.
I am running on a simulator, but google play comes with it for a reason, so i discard that also.
The rest of the suggestions say to use other device. My simulator is running API 28 so should be good enough.
In-app purchase must be tested with production build on real device.
Steps
Generate release build from Android studio.
Uninstall debug app from your device, or use adb uninstall.
adb uninstall {yourdomain}.{yourpackagename}
Install your release version to your device.
adb install app-release.apk
Update:
Check this answer for more details.
Update 2 :Please read more about Test Google Play Billing
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