AuthUI.getInstance().createSignInIntentBuilder() causing "An internal error has occured. [ Backend Error ]"

[kermitdefroghere]

Step 2: Describe your environment

• Android device: Nexus 5__and Nexus 7___
• Android OS version: 6.0.1___
• Google Play Services version: _____
  classpath 'com.google.gms:google-services:3.0.0'
• Firebase/Play Services SDK version: _____
  compile 'com.google.firebase:firebase-storage:9.2.0'
• FirebaseUI version: ____
  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:

                startActivityForResult(
                        // Get an instance of AuthUI based on the default app
                        AuthUI.getInstance().createSignInIntentBuilder().build(),
                        RC_SIGN_IN);

[kermitdefroghere]

Is it possible to have an update on this error?
This still occurs with Firebase UI 4.3.

Are there any work arounds?

[samtstern]

@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.

[kermitdefroghere]

It occurs for different accounts/email addresses on different devices.
My domain (for testing) is managed by google and there are different results if Google sign-in method is enabled or not.

As of this morning, Smart lock is not allowing me to login at all???
StartActivityForResult reveals a 'Google Smart Lock' notification box in bottom left,... and screen just goes blank. OnActivityResult is never triggered.
At this point, I'm not even presented with the option to select signin with Google or email.

My feeling is that the combination of Smartlock and a Google managed domain is causing the problem.

[kermitdefroghere]

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.
However, it is not a workaround for running my android app on Chromebook Flip.
Upon selecting 'Sign in with Google' from the FirebaseUI login screen and choosing the desired account, it simply returns back to the FirebaseUI login screen. This process can be repeated indefinitely across different accounts... so no change there.

[samtstern]

@kermitdefroghere version 0.5.1 has a new option on the intent builder to disable SmartLock for Passwords. Could you try that and see if it solves your problem?

[kermitdefroghere]

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 Google', I'm presented with my google account to select and then I'm brought right back to the
firebaseUI screen (below).

When trying to 'Sign in with Email', I enter my google email after which I'm informed that 'You already have an
account. Sign in with Google to continue'. After I click the 'sign in'
button, I receive the Toast message "Error signing in" and I'm back at the
firebase UI screen (below).

Since I'm running this on the Asus Flip, I can't run in debug mode or
capture any logs.

If there's any other information you need, please let me know.

Derek

p.s. Here's the actual method call with setIsSmartLockEnabled = false

        startActivityForResult(
                AuthUI.getInstance()
                        .createSignInIntentBuilder()
                        .setProviders(
                                AuthUI.EMAIL_PROVIDER,
                                AuthUI.GOOGLE_PROVIDER)
                        .setTheme(R.style.AppTheme)
                        .setLogo(R.mipmap.ic_launcher)
                        .setIsSmartLockEnabled(false)
                        .build(),
                RC_SIGN_IN);

[image: Inline image 1]

On Aug 23, 2016 4:15 PM, "Sam Stern" notifications@github.com wrote:

@kermitdefroghere https://github.com/kermitdefroghere version 0.5.1 has
a new option on the intent builder to disable SmartLock for Passwords.
Could you try that and see if it solved your problem>

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#212 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQPs6T0RBCmtkIpiDTB-9aOzaWMe-vKlks5qi2LegaJpZM4JM4-7
.

[samtstern]

@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.

[kermitdefroghere]

Do you have instructions for how I can provide the debug logs from the
Chromebook?
I'd be more than happy to provide that.

On Aug 30, 2016 3:08 PM, "Sam Stern" notifications@github.com wrote:

@kermitdefroghere https://github.com/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.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#212 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQPs6e-LzidNwYVke1JEB3E3xY1uEtwRks5qlGcUgaJpZM4JM4-7
.

[kermitdefroghere]

Quick update that FirebaseUI 0.5.3 doesn't fix anything.
Repeat: Apps that use FirebaseUI/auth do not currently work on Chromebooks because google users can't login!!!

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)

[samtstern]

@kermitdefroghere thanks for checking 0.5.3 and following up. I agree this is not a good experience, but we can only guess what's causing it without proper debug logs from a Chromebook. If you do figure out how to capture those, let me know.

[kermitdefroghere]

For what it's worth, I'm seeing that other Android Apps struggle logging in on Chromebooks as well.
Feedly for example simply loops when trying to 'Sign in with Google' as well.

Should this bug be reported elsewhere?
If so, where?