Google authentication in macOS app

[CordMemescape]

Hi all,

Has anyone tried Google authentication in a macOS app? I'm using the various authentication setup guides for an app that I'm building for all of Flutter's supported platforms. However, when running as a macOS app, when I click "Sign in with Google" the app becomes non-responsive.

Is Google authentication in a macOS app supported, or am I doing something wrong?

Thanks in advance,
Cord

[CordMemescape]

Adding to this, I've applied the same guidance to the macOS app as suggested for the iOS setup (including - for now - sharing a bundle_id). Details of the setup are here: https://medium.com/serverpod/integrating-google-sign-in-with-serverpod-authentication-part-2-6fade3099baf

Now, both iOS and macOS fire up Safari and provide a Google authentication screen. When completed however, I see the following in the logs:

flutter: serverpod_auth_google: GoogleSignIn
flutter: serverpod_auth_google: Signing out from google
flutter: Failed call: serverpod_auth.google.authenticateWithServerAuthCode
flutter: ServerpodClientException: Internal server error, statusCode = 500
flutter: serverpod_auth_google: ServerpodClientException: Internal server error, statusCode = 500
flutter: #0      ServerpodClient.callServerEndpoint (package:serverpod_client/src/serverpod_client_io.dart:72:9)
<asynchronous suspension>
#1      signInWithGoogle (package:serverpod_auth_google_flutter/src/auth.dart:66:24)
<asynchronous suspension>
#2      SignInWithGoogleButtonState.build.<anonymous closure>.<anonymous closure> (package:serverpod_auth_google_flutter/src/signin_button.dart:93:16)
<asynchronous suspension>
#3      SignInWithGoogleButtonState.build.<anonymous closure>.<anonymous closure> (package:serverpod_auth_google_flutter/src/signin_button.dart:102:25)
<asynchronous suspension>

Any idea why this is not completing correctly?

[CordMemescape]

Looking through the server logs I can see the following:

METHOD CALL: serverpod_auth.google.authenticateWithServerAuthCode duration: 0ms numQueries: 0 authenticatedUser: null
Bad state: The server side Google client secret is not loaded.
#0      GoogleEndpoint.authenticateWithServerAuthCode (package:serverpod_auth_server/src/endpoints/google_endpoint.dart:34:7)
#1      Endpoints.initializeEndpoints.<anonymous closure> (package:serverpod_auth_server/src/generated/endpoints.dart:351:20)
#2      EndpointDispatch.handleUriCall (package:serverpod/src/server/endpoint_dispatch.dart:127:37)
<asynchronous suspension>
#3      Server._handleRequest (package:serverpod/src/server/server.dart:296:18)
<asynchronous suspension>

This aligns with a similar discussion topic that was resolved by placing the google_client_secret.json file in the server/config folder. However, this has already been done and the server was restarted. Is there some other magic that needs doing to get Serverpod to recognise/load the server side client secret to load?

[CordMemescape]

I've tracked down the issue to the following code in
serverpod/modules/serverpod_auth/serverpod_auth_server/lib/src/business/google_auth.dart

/// Contains information about the credentials for the server to access Google's
/// APIs. The secrets are typically loaded from
/// `config/google_client_secret.json`. The file can be downloaded from Google's
/// cloud console.
class GoogleClientSecret {
  ...
  /// List of redirect uris.
  late List<String> redirectUris;

  /// Loads the google client secrets from the provided path.
  GoogleClientSecret._(this._path) {
    ...
    Map web = data['web'];
    clientId = web['client_id'];
    clientSecret = web['client_secret'];
    redirectUris = (web['redirect_uris'] as List).cast<String>();
  }

When creating an OAuth client ID in Google Cloud Console, the Authorised redirect URIs field is optional and can be left blank. However, the code above is expecting to find redirect_uris in the JSON and therefore the GoogleClientSecret fails to load.

redirectUrl, however, is required by SignInWithGoogleButton():

/// Creates a new Sign in with Google button.
  const SignInWithGoogleButton({
    required this.caller,
    this.clientId,
    this.serverClientId,
    ...
    required this.redirectUri,
    super.key,
  });

So it would probably make sense to make redirectUri a required field in GoogleEndpoint.authenticateWithServerAuthCode and safely whatever was passed into GoogleClientSecret.

Future<AuthenticationResponse> authenticateWithServerAuthCode(
    Session session,
    String authenticationCode,
    String? redirectUri,
  )