If you add any Google Drive scope to GoogleBuilder using setScopes() function, login screen shows white screen dialog with progress..

[RohitSurwase]

Welcome to FirebaseUI and thanks for submitting an issue!

Please take a look at open issues, as well as resolved issues, to see if your issue is either already being addressed, or has been solved by someone else.

If not, please feel free to fill in the following info so we can help faster!

Step 1: Are you in the right place?

• For issues or feature requests related to the code in this repository file a GitHub issue.
• For general technical questions, post a question on StackOverflow tagged appropriately.
• For general Firebase discussion, use the firebase-talk google group
• For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel

Step 2: Describe your environment

• Android device: Samsung Galaxy M40
• Android OS version: Android 10
• Google Play Services version: 4.3.4
• Firebase/Play Services SDK version: 26.2.0 (BoM)
• FirebaseUI version: 7.1.1

Step 3: Describe the problem:

Steps to reproduce:

1. Enable Google Drive library for the sample project in Google API console.
2. Add OAuth 2.0 client IDs at Google API console
3. Add "../auth/drive" or any other scope in Scopes for Google Drive APIs
4. Now request drive scope while signing in with Google, login does not work.

Observed Results:

• If I add a scope to GoogleBuilder using .setScopes(listOf(Scopes.DRIVE_FILE)) or any other scope, sign in does not work

Expected Results:

• Sign in should show a screen requesting Google Drive scope access permission.

Relevant Code:

      val googleAuthBuilder = AuthUI.IdpConfig.GoogleBuilder()
          .setScopes(listOf(DriveScopes.DRIVE_READONLY))
          .build()
      val providers = arrayListOf(
          googleAuthBuilder)

      // Create and launch sign-in intent
      startActivityForResult(
          AuthUI.getInstance()
              .createSignInIntentBuilder()
              .setAvailableProviders(providers)
              .build(), RC_FOR_SIGN_IN)

[demolaf]

Hello,

Thank you for taking the time to submit this bug.

This is a great idea and definitely something we can consider for the future. It is not currently prioritized for our immediate new version roadmap, as we are focusing on a new upcoming release.

In the meantime, we will keep this issue open so we can revisit it during a later planning cycle, particularly as we gather more feedback from the community.