New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AuthUI.getInstance().createSignInIntentBuilder() causing "An internal error has occured. [ Backend Error ]" #212
Comments
Is it possible to have an update on this error? Are there any work arounds? |
@kermitdefroghere are you using the same account (same email address) on each device? I'd like to see if this is an account-specific issue or a device/os/play services specific issue. |
It occurs for different accounts/email addresses on different devices. As of this morning, Smart lock is not allowing me to login at all??? My feeling is that the combination of Smartlock and a Google managed domain is causing the problem. |
I can confirm that disabling smartlock and auto signin at passwords.google.com is a temporary work around for my nexus devices and Pixel C. |
@kermitdefroghere version |
Hi Sam, Unfortunately, this doesn't fix the problem on my Chromebook (Asus Flip). I have both Google and email authentication enabled. When trying to 'Sign in with Email', I enter my google email after which I'm informed that 'You already have an Since I'm running this on the Asus Flip, I can't run in debug mode or If there's any other information you need, please let me know. Derek p.s. Here's the actual method call with setIsSmartLockEnabled = false
[image: Inline image 1] On Aug 23, 2016 4:15 PM, "Sam Stern" notifications@github.com wrote:
|
@kermitdefroghere at this point I am not sure how to proceed without some debug logs from the Chromebook, otherwise I'd just be guessing (and clearly my guessing above didn't work). I will leave this issue open in the hopes that someone else with a Chromebook has some insight. |
Do you have instructions for how I can provide the debug logs from the On Aug 30, 2016 3:08 PM, "Sam Stern" notifications@github.com wrote:
|
Quick update that FirebaseUI 0.5.3 doesn't fix anything. Isn't this a big deal? (To be entirely clear, it's Google managed domains that don't work. 'signing in with email' for a non google managed domain does work) |
@kermitdefroghere thanks for checking |
For what it's worth, I'm seeing that other Android Apps struggle logging in on Chromebooks as well. Should this bug be reported elsewhere? |
I have more info on this problem. Have to use sign in with email. Will be forced to disable 'sign in with google' option until this is resolved. |
@kermitdefroghere have you registered your signed version of the app in the Firebase console? The fact that your app only fails with a different signing configuration (and specifically with Google Sign In) leads me to believe that this is a SHA1 configuration issue. I have this function in my # Usage
# apk_signature my-apk-file.apk
function apk_signature() {
TMP_DIR=$(mktemp -d)
unzip $1 -d $TMP_DIR > /dev/null
keytool -printcert -file $TMP_DIR/META-INF/*.RSA
rm -r $TMP_DIR
} |
You're likely on to something. I have one SHA1 certificate fingerprint setup,... and seeing the helptext I'm not familiar with .bashrc but I'll look into this and get back to you. Thanks for pointing this out Sam. On Mon, Oct 3, 2016 at 12:38 PM, Sam Stern notifications@github.com wrote:
|
You can also get your sha1 keys from Android Studio: http://stackoverflow.com/a/34223470/4548500 |
Ok. I can confirm that adding the SHA1 for the signed apk has fixed my Google Signin issue. For other newbies in the future, it would likely be helpful if activityResult was triggered with with error resultcode instead of not being triggered at all. |
@SUPERCILEX thanks for showing me the fantastic |
@samtstern Your welcome! |
#371 should make it clearer that it was Google Sign In failing. We currently can't tell if it failed because of a config error, or if it was canceled by the user, so we have to stay on the |
Hey all, i fixed it with update Google Play Service to last version... |
Step 2: Describe your environment
classpath 'com.google.gms:google-services:3.0.0'
compile 'com.google.firebase:firebase-storage:9.2.0'
compile 'com.firebaseui:firebase-ui:0.4.2'
Step 3: Describe the problem:
FirebaseUI crashes with error below when attempting to login with code below.
Error is reported silently in Android monitor. App simply reports 'loading' for a number of seconds and goes to blank screen.
onActivityResult is never called.
Same result with either Smartlock or manually entered email/password.
Nexus 5x with Android N works fine.
Problem only exists with my Nexus 5 and Nexus 7.
Observed Results:
07-14 16:43:27.474 28980-28980/ca.tentensolutions.physiotherapy W/AcquireEmailHelper: Error fetching providers for email
com.google.firebase.FirebaseException: An internal error has occured. [ Backend Error ]
at com.google.android.gms.internal.zzafg.zzes(Unknown Source)
at com.google.android.gms.internal.zzafd$zzg.zza(Unknown Source)
at com.google.android.gms.internal.zzafo.zzet(Unknown Source)
at com.google.android.gms.internal.zzafo$zza.onFailure(Unknown Source)
at com.google.android.gms.internal.zzafj$zza.onTransact(Unknown Source)
at android.os.Binder.execTransact(Binder.java:453)
Relevant Code:
The text was updated successfully, but these errors were encountered: