"[app] wants additional access to your Google Account" on re-sign-in on iOS.

[gjbadros]

Using 12.2.0 (i.e., not using the sponsor-only version though I am a sponsor), on iOS I see this message from Google when re-signing in to a previously signed-out account. It's new as of a month or so ago, and it's confusing because it doesn't explain what additional scopes are being requested by the app:

Ideas?

Expected Behavior

Just a regular accept sign-in dialog from Google

Actual Behavior

See the screenshot.

Environment

• react-native version: 0.74.1
• @react-native-google-signin/google-signin version: 12.2.0
• version of iOS (if applicable): 17.4.1

Just passing the webClientId and iosClientId to the .configure call.

[vonovak]

Hello and thanks for reporting,
firstly, do you have steps that consistently reproduce the issue? That allows others to replicate it.
My feeling is that this is an issue with Google after they redesigned the experience. In that case you could report it in https://github.com/google/GoogleSignIn-iOS/issues - but again, the repro steps are crucial.
Thank you 🙂

[Stas-Buzunko]

GoogleSignin.configure({
  webClientId: GOOGLE_AUTH_CLIENT_ID
})
export const authGoogleSignin = async () => {
  try {
    // Check if your device supports Google Play
    await GoogleSignin.hasPlayServices({ showPlayServicesUpdateDialog: true })
    // Get the users ID token
    const { idToken, user } = await GoogleSignin.signIn()
    // ...
  } catch (error) {
    // ....
  }
}

turned out we use v9.1.0

[Stas-Buzunko]

it looks like this has nothing to do with this library as we get the same issue using v9.1.0

[jeremyplt]

Same issue here. using signInSilently (https://react-native-google-signin.github.io/docs/original#signinsilently) is the only workaround I found

[vsk-pvr]

Same here. Is this something related to this?: google/GoogleSignIn-iOS#407

[vonovak]

update: I opened an issue in the official google sign in SDK repository, please go there and upvote it, thank you!

google/GoogleSignIn-iOS#457

The issue originates in Google's implementation, not in this package.
Thank you 🙂