Can we access your project?
Current Behavior
After selecting a Google account in the sign-in flow, the app does not proceed. No error is shown to the user. Confirmed via adb logcat that the underlying google_sign_in package internally treats this as a cancelled sign-in (GoogleSignIn.signIn.isCanceled), even though the user completed account selection normally without cancelling.
Reproduced identically on BOTH a BlueStacks Android 11 emulator AND a real Android phone with a different Google account — ruling out emulator-specific limitations.
Firebase Authentication console confirms no new user record is created after this flow.
Environment:
- Package name: com.wangsc.selfhealingapp
- google_sign_in version (per Project Dependencies > FlutterFlow Pub Dependencies): 6.3.0
- OAuth consent screen status: In production (not testing)
- SHA-1 and SHA-256 fingerprints (from Google Play App Signing key) are correctly registered in Firebase Console, confirmed matching.
- Google Cloud auto-generated a matching Android OAuth 2.0 Client ID after fingerprints were added.
Key logcat excerpt:
08-09 20:23:21.452 W Auth.Api.SignIn: You are using the deprecated legacy Google Sign-In APIs from play-services-auth SDK. Please migrate to the Credential Manager APIs, see https://goo.gle/gsi-migration.
08-09 20:23:25.416 W SignIn: [Activity,SignInChimeraActivity] Failed to record the consent.
08-09 20:23:25.826 E flutter: #3 GoogleSignIn.signIn.isCanceled (package:google_sign_in/google_sign_in.dart:436)
What we've already ruled out:
- SHA-1 fingerprint mismatch (added and confirmed matching)
- SHA-256 fingerprint mismatch (added and confirmed matching)
- Stale Firebase config (regenerated config files in FlutterFlow, redeployed to Google Play Internal Testing twice)
- OAuth consent screen test-user restriction (screen is in Production status)
- Emulator-specific Google Play Services limitation (reproduced on real device)
This blocks Google Sign-In for all Android users, not just our test account, and is currently blocking our production launch on Google Play.
Expected Behavior
After selecting an account, the app should proceed with sign-in, create/update the Firebase Authentication user record, and continue the app's post-login flow (as it does correctly on iOS).
Steps to Reproduce
- Open the app on Android (tested on both a BlueStacks Android 11 emulator and a real Android phone).
- Complete the in-app onboarding/quiz flow until the "Continue with Google" button appears.
- Tap "Continue with Google".
- System account picker appears normally — select any Google account.
- Observe: the app returns to the same screen. No error message is shown, and no new user record is created in Firebase Authentication.
Reproducible from Blank
Bug Report Code (Required)
IT4ChfHl8ZJgoeVc7arAacFvryQsKUg4RYIV0dYbGQ8aJ5POD7AQP8nRP1dUOcO5TVVUfE2kmXwX/MrLjoXLEvAqZUmtY61x1ZBLFjmWWl+iRIyyDoS3b3xPGd5hFUyb15mN2yV4CMZqLn9nwV2MDOmQcHLtNYzSIFUzBOaoXdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
- FlutterFlow version: (please check via Help menu > About, or leave blank if unsure)
- Platform: Android
- Package name: com.wangsc.selfhealingapp
- Tested devices: BlueStacks App Player 1 (Android 11 emulator) AND a real Android phone
- google_sign_in package version: 6.3.0 (per FlutterFlow Pub Dependencies)
Additional Information
This bug currently blocks all Android users from completing Google Sign-In in our app, which is a required step before accessing gated content (subscription features behind a paywall). We are close to submitting our app to Google Play for review, and this is the single remaining blocker preventing a safe launch. We've done extensive troubleshooting (SHA-1/SHA-256 fingerprints, OAuth consent screen status, config regeneration, testing on both emulator and real device) and are confident this is a platform-level issue with the deprecated google_sign_in 6.3.0 package used internally by FlutterFlow, not a project misconfiguration on our end.
Can we access your project?
Current Behavior
After selecting a Google account in the sign-in flow, the app does not proceed. No error is shown to the user. Confirmed via adb logcat that the underlying google_sign_in package internally treats this as a cancelled sign-in (GoogleSignIn.signIn.isCanceled), even though the user completed account selection normally without cancelling.
Reproduced identically on BOTH a BlueStacks Android 11 emulator AND a real Android phone with a different Google account — ruling out emulator-specific limitations.
Firebase Authentication console confirms no new user record is created after this flow.
Environment:
Key logcat excerpt:
08-09 20:23:21.452 W Auth.Api.SignIn: You are using the deprecated legacy Google Sign-In APIs from play-services-auth SDK. Please migrate to the Credential Manager APIs, see https://goo.gle/gsi-migration.
08-09 20:23:25.416 W SignIn: [Activity,SignInChimeraActivity] Failed to record the consent.
08-09 20:23:25.826 E flutter: #3 GoogleSignIn.signIn.isCanceled (package:google_sign_in/google_sign_in.dart:436)
What we've already ruled out:
This blocks Google Sign-In for all Android users, not just our test account, and is currently blocking our production launch on Google Play.
Expected Behavior
After selecting an account, the app should proceed with sign-in, create/update the Firebase Authentication user record, and continue the app's post-login flow (as it does correctly on iOS).
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT4ChfHl8ZJgoeVc7arAacFvryQsKUg4RYIV0dYbGQ8aJ5POD7AQP8nRP1dUOcO5TVVUfE2kmXwX/MrLjoXLEvAqZUmtY61x1ZBLFjmWWl+iRIyyDoS3b3xPGd5hFUyb15mN2yV4CMZqLn9nwV2MDOmQcHLtNYzSIFUzBOaoXdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
Additional Information
This bug currently blocks all Android users from completing Google Sign-In in our app, which is a required step before accessing gated content (subscription features behind a paywall). We are close to submitting our app to Google Play for review, and this is the single remaining blocker preventing a safe launch. We've done extensive troubleshooting (SHA-1/SHA-256 fingerprints, OAuth consent screen status, config regeneration, testing on both emulator and real device) and are confident this is a platform-level issue with the deprecated google_sign_in 6.3.0 package used internally by FlutterFlow, not a project misconfiguration on our end.