FirebaseUI Auth picker screen hides buttons

[francos]

Describe your environment

• Android device: Motorola Moto X (2nd Generation)
• Android OS version: 6.0
• Google Play Services version: 14.3.66
• Firebase/Play Services SDK version: 16.0.4
• FirebaseUI version: 4.2.0

Describe the problem:

When opening the auth picker screen with some SVG logo images, some buttons are hidden because there is a lot of empty space inside the scroll view.

Steps to reproduce:

1. Start the auth picker activity like this:

startActivityForResult(authUI.createSignInIntentBuilder()
                             .setAvailableProviders(listOf(GoogleBuilder().build(),
                                                           FacebookBuilder().build(),
                                                           EmailBuilder().build()))
                             .setLogo(R.drawable.ic_play)
                             .setTheme(R.style.AppTheme_NoActionBar)
                             .setIsSmartLockEnabled(false, false)
                             .build(), 1)

This is the SVG image I use as the logo:

<vector xmlns:android="http://schemas.android.com/apk/res/android"
    android:width="50dp"
    android:height="50dp"
    android:viewportWidth="50"
    android:viewportHeight="50">
  <path
      android:pathData="M25,25m-24,0a24,24 0,1 1,48 0a24,24 0,1 1,-48 0"
      android:strokeAlpha="0.5"
      android:strokeWidth="1"
      android:fillColor="#00000000"
      android:strokeColor="#FFFFFF"
      android:fillType="evenOdd"
      android:fillAlpha="0.5"/>
  <path
      android:pathData="M25,25m-21.3333,0a21.3333,21.3333 0,1 1,42.6667 0a21.3333,21.3333 0,1 1,-42.6667 0"
      android:strokeAlpha="0.2"
      android:strokeWidth="1"
      android:fillColor="#FFFFFF"
      android:fillType="evenOdd"
      android:strokeColor="#00000000"
      android:fillAlpha="0.2"/>
  <path
      android:pathData="M31.0013,24.6061C32.0155,25.2661 32.0155,26.3442 31.0013,27.0042L22.8448,32.3062C21.8306,32.9661 21.0001,32.514 21.0001,31.3051L21.0001,20.3051C21.0001,19.0951 21.8306,18.6441 22.8448,19.3041L31.0013,24.6061Z"
      android:strokeWidth="1"
      android:fillColor="#FFFFFF"
      android:fillType="evenOdd"
      android:strokeColor="#00000000"/>
</vector>

Observed Results:

• This happens in version 4.2 and 4.1 of the FirebaseUI SDK, but it doesn't happen on version 4.0.1

• The problem doesn't happen when a logo is not set (also, some logos don't trigger this issue).

• This is what the screen looks like using FirebaseUI SDK 4.2:

Expected Results:

The buttons should be at the top of the scroll view and the margin should be outside the scroll view.

[samtstern]

@FrancoSabadini thanks for reporting this, and apologies for not responding earlier. I have added this to the 4.3.0 milestone for investigation.

Are you using ConstraintLayout in your app and if so, what version of the dependency are you using?

[francos]

Hi @samtstern, thanks for getting back to me about the issue.

I'm using ConstraintLayout version 2.0.0-alpha2.

[samtstern]

We use com.android.support.constraint:constraint-layout:1.1.3 in this project, I suspect this issue comes from the difference. Would it be possible for you to try downgrading and checking the issue?

[francos]

Sure, I'm not working atm but will try it out tomorrow and let you know.

[francos]

Sorry for the delay @samtstern. I tested it with androidx.constraintlayout:constraintlayout:1.1.3 and the issue is still there (notice that I'm using the AndroidX dependency and not the support one you mentioned, although they should be the same).

[robapaul88]

robapaul88@cd293b5

This issues only happens while in portrait, and the fix seems to be adding:
android:layout_width="wrap_content"
android:layout_height="0dp"
to the logo ImageView in fui_auth_method_picker_layout.xml (basically redeclaring same layout_widht and layout_height properties from @style/FirebaseUI.AuthMethodPicker.Logo in the xml).

[samtstern]

I imported the XML that @FrancoSabadini provided and used it as the logo. I was not able to reproduce this on top of the version-4.3.0-dev branch:

If anyone can reproduce this on top of 4.3.0 (try the SNAPSHOT build if you can!) that would be really helpful. As it stands, I have to pint this to 4.3.1 since I can't repro.

[samtstern]

@FrancoSabadini are you still seeing this issue in 4.3.1? Sorry to keep asking but I am having trouble getting it to happen myself which is why I haven't been able to land a fix.