google-services icon indicating copy to clipboard operation
google-services copied to clipboard

../auth/drive.metadata.readonly scope not displayed on consent screen

Open ndreisg opened this issue 4 years ago • 2 comments

  • Device: iPhone 6s
  • OS version: iOS 13.3.1
  • SDK version:
    • GoogleSignIn (5.0.2)
    • AppAuth (~> 1.2)
    • GTMAppAuth (~> 1.0)
    • GTMSessionFetcher/Core (~> 1.1)

Step 3: Describe the problem:

When the scope ../auth/drive.metadata.readonly is requested in an iOS app, the scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted. (not sure if this is also reproducible on Android)

Steps to reproduce:

  1. Use the iOS Sample and add ../auth/drive.metadata.readonly scope
  2. Run it
  3. Log in and grant permissions
  4. Log out
  5. Log in again

Observed Results:

../auth/drive.metadata.readonly scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted.

Expected Results:

The scope should always be displayed

ndreisg avatar Apr 22 '20 10:04 ndreisg

Спасибо вам 😉, я сегодня не смогу выполнить, 🍺🛏️

Отправлено из Mail.ru для Android среда, 22 апреля 2020г., 14:04 +04:00 от ndreisg [email protected] :

Device: iPhone 6s

  • OS version: iOS 13.3.1
  • SDK version:
  • GoogleSignIn (5.0.2)
  • AppAuth (~> 1.2)
  • GTMAppAuth (~> 1.0)
  • GTMSessionFetcher/Core (~> 1.1) Step 3: Describe the problem: When the scope ../auth/drive.metadata.readonly is requested in an iOS app, the scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted. (not sure if this is also reproducible on Android) Steps to reproduce:
  • Use the iOS Sample and add ../auth/drive.metadata.readonly scope
  • Run it
  • Log in and grant permissions
  • Log out
  • Log in again Observed Results: ../auth/drive.metadata.readonly scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted. Expected Results: The scope should always be displayed — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or unsubscribe .

Kongreen avatar Apr 22 '20 10:04 Kongreen

я не могу использовать операционную систему iOC я не пользуюсь телефоном или оборудованием iPhone

Отправлено из Mail.ru для Android четверг, 23 апреля 2020г., 15:29 +04:00 от ndreisg [email protected] :

Device: iPhone 6s

  • OS version: iOS 13.3.1
  • SDK version:
  • GoogleSignIn (5.0.2)
  • AppAuth (~> 1.2)
  • GTMAppAuth (~> 1.0)
  • GTMSessionFetcher/Core (~> 1.1) Step 3: Describe the problem: When the scope ../auth/drive.metadata.readonly is requested in an iOS app, the scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted. (not sure if this is also reproducible on Android) Steps to reproduce:
  • Use the iOS Sample and add ../auth/drive.metadata.readonly scope
  • Run it
  • Log in and grant permissions
  • Log out
  • Log in again Observed Results: ../auth/drive.metadata.readonly scope is only displayed on the OAuth consent screen at the first login. At subsequent logins the scope is not displayed on the consent screen but still granted. Expected Results: The scope should always be displayed — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or unsubscribe .

Kongreen avatar Apr 25 '20 08:04 Kongreen