firebase authentication google sign in not working when I run my flutter web app in wasm mode, it is working fine in html and canvas kit renderer

[vrajkishore]

I am listening to authstate changes using the listenToUserChanges() function and performing google sign in using the createGoogleAuthCustomer() function, in normal rendered I am able to listen to the FirebaseAuth.instance.authStateChanges() when I perform the google sign in a popup, in wasm even though I continue with google sign in the popup not able to listen to the FirebaseAuth.instance.authStateChanges() and also not able to find the error

import 'package:firebase_auth/firebase_auth.dart';

Stream<User?> listenToUserChanges() async* {
await for (var user in FirebaseAuth.instance.authStateChanges()) {
yield user;
}
}

Future createGoogleAuthCustomer() async {
try {
GoogleAuthProvider googleProvider = GoogleAuthProvider();
// googleProvider
// .addScope('https://www.googleapis.com/auth/contacts.readonly');
// googleProvider.setCustomParameters({'login_hint': 'user@example.com'});
return await FirebaseAuth.instance.signInWithPopup(googleProvider);

} catch (e) {
  throw CustomException(AuthDataRepository, "Authentication failed",
      displayMessage: "Failed to authenticate with Google.");
}

}

Flutter Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.29.0, on macOS 15.3.1 24D70 darwin-x64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.97.2)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

pubspec.yaml

firebase_core: ^3.12.1
firebase_auth: ^5.5.1

[MichaelVerdon]

Hi there, I tested out google sign in on our example authentication app in wasm mode and it worked perfectly fine and successfully checked persisted user data. I would suggest checking out how we implemented it here as maybe there is an issue with your implementation: https://github.com/firebase/flutterfire/tree/main/packages/firebase_auth/firebase_auth/example

[vrajkishore]

Hi, i have implemented google sign in as mentioned in the firebase_auth example, below is my function

Future signInWithGoogle() async {
try {
// Trigger the authentication flow
final googleUser = await GoogleSignIn().signIn();

  // Obtain the auth details from the request
  final googleAuth = await googleUser?.authentication;

  if (googleAuth != null) {
    // Create a new credential
    final credential = GoogleAuthProvider.credential(
      accessToken: googleAuth.accessToken,
      idToken: googleAuth.idToken,
    );
    // Once signed in, return the UserCredential
    return await FirebaseAuth.instance.signInWithCredential(credential);
  } else {
    throw CustomException(AuthDataRepository, "Authentication failed",
        displayMessage: "Failed to authenticate with Google.");
  }
} catch (e) {
  throw CustomException(AuthDataRepository, "Authentication failed",
      displayMessage: "Failed to authenticate with Google.");
}

}

It is working perfectly fine even in wasm build but i am getting the below warning messages in console

[GSI_LOGGER]: Evaluating FedCM mode support.
[GSI_LOGGER]: FedCM mode supported.
[GSI_LOGGER-TOKEN_CLIENT]: Instantiated.
The signIn method is discouraged on the web because it can't reliably provide an idToken.
Use signInSilently and renderButton to authenticate your users instead.
Read more: https://pub.dev/packages/google_sign_in_web
The google_sign_in plugin signIn method is deprecated on the web, and will be removed in Q2 2024. Please use renderButton instead. See: https://pub.dev/packages/google_sign_in_web#migrating-to-v011-and-v012-google-identity-services
[GSI_LOGGER-TOKEN_CLIENT]: Starting popup flow.
[GSI_LOGGER-OAUTH2_CLIENT]: Starting popup timer.
10
[GSI_LOGGER-OAUTH2_CLIENT]: Checking popup closed.
[GSI_LOGGER-OAUTH2_CLIENT]: Popup window closed.
[google_sign_in_web] Error on TokenResponse: popup_closed
Application finished.

I am not able to find any renderbutton examples, should i ignore the warning ? will the google_sign_in package be updated before signIn method is removed ?

[MichaelVerdon]

Unfortunately I am unable to give you an example however I would encourage you to keep using it and if you run into any issues you can open another ticket and it could be a feature request. I will mark this as resolved.