[Android] I can't login with Google Workspace email

[huyphamsupercoder]

I have searched open and closed issues for this issue.

• I have searched open and closed issues.

This is not a bug report for DEVELOPER_ERROR. If it is, read the troubleshooting guide.

• This is not a bug report for DEVELOPER_ERROR.

Minimal reproducible example

You can try to login with any Workspace email, it just cancelled the login modal

What platform(s) does this occur on?

Android

Summary

When I try to login with Workpsace email from Google, the modal show up and just cancelled

Your computer environment

System:
  OS: macOS 15.1
  CPU: (12) arm64 Apple M3 Pro
  Memory: 105.33 MB / 18.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.20.4
    path: /opt/homebrew/opt/node@18/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.7.0
    path: /opt/homebrew/opt/node@18/bin/npm
  Watchman:
    version: 2024.10.14.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.19072.14.2412.12360217
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

[rybaier]

Don't know If this is related to my issue but it might be where it was canceling out for an unHandled sign-error. the structure of the signIn result has changed the idToken and user objects are now housed within the data object

new response structure

{
type: "success",
data:{ "scopes":, "serverAuthCode":, "idToken":, "user": {userInfoObject} } 
 }

what I had originally

const handleGoogleSignIn = async () => {
  try {
    const { idToken, user } = await GoogleSignin.signIn();
    await signInWithGoogleCredential(idToken as string, user as googleUser);
  } catch (error) {
    handleSignInError(error);
  }
};

what solved it

const handleGoogleSignIn = async () => {
  try {
    const signInResult = await GoogleSignin.signIn();
  //  log.debug("SIGN IN RESULT", JSON.stringify(signInResult));
    const {idToken, user} = signInResult.data || {}
    await signInWithGoogleCredential(idToken as string, user as GoogleUser);
  } catch (error) {
    handleSignInError(error);
  }
};

[ahmadtech199]

Check if "Google Play App Signing" is enabled for your app in the console. If it is enabled, you need to take the following steps:

In Google Play Console, navigate to: -> Release section (in the left sidebar) -> Setup -> App Signing.
Under the "App signing key certificate" and also "Upload key certificate", take note of SHA-1 certificate fingerprint. That's a total of two or more fingerprints (Play Store sometimes has more than one "App signing key certificate"!).