Google Single Sign On error for first time users

We currently have a lot of users signed in using Google Sign on. Any new users receive the following error when signing in for the first time using google:
{ "message": "Assert failed: (or (every? u/is-email? recipients) (log/error \"recipients contains an invalid email:\" recipients))", "stacktrace": ["email$send_message_BANG_.invokeStatic(email.clj:49)", "email$send_message_BANG_.doInvoke(email.clj:49)", "email.messages$send_user_joined_admin_notification_email_BANG_.invokeStatic(messages.clj:83)", "email.messages$send_user_joined_admin_notification_email_BANG_.doInvoke(messages.clj:78)", "models.user$create_new_google_auth_user_BANG_.invokeStatic(user.clj:142)", "models.user$create_new_google_auth_user_BANG_.invoke(user.clj:131)", "api.session$google_auth_create_new_user_BANG_.invokeStatic(session.clj:179)", "api.session$google_auth_create_new_user_BANG_.invoke(session.clj:175)", "api.session$google_auth_fetch_or_create_user_BANG_.invokeStatic(session.clj:183)", "api.session$google_auth_fetch_or_create_user_BANG_.invoke(session.clj:181)", "api.session$fn__34005$fn__34008.invoke(session.clj:194)", "api.common.internal$do_with_caught_api_exceptions.invokeStatic(internal.clj:229)", "api.common.internal$do_with_caught_api_exceptions.invoke(internal.clj:224)", "api.session$fn__34005.invokeStatic(session.clj:186)", "api.session$fn__34005.invoke(session.clj:186)", "api.routes$fn__34738.invokeStatic(routes.clj:72)", "api.routes$fn__34738.invoke(routes.clj:72)", "routes$fn__40306$fn__40307.doInvoke(routes.clj:53)", "routes$fn__40306.invokeStatic(routes.clj:49)", "routes$fn__40306.invoke(routes.clj:49)", "middleware$log_api_call$fn__34681$fn__34683.invoke(middleware.clj:331)", "middleware$log_api_call$fn__34681.invoke(middleware.clj:330)", "middleware$add_security_headers$fn__34631.invoke(middleware.clj:245)", "middleware$bind_current_user$fn__34586.invoke(middleware.clj:139)", "middleware$maybe_set_site_url$fn__34635.invoke(middleware.clj:268)"] }

Does anyone know what the issue is? We’re using 0.23.1.

Would changing the client id help? If so what is the effect on existing users?

nevermind figured out it was an error in setting the admin email. However the documentation on this could be improved.
When a new user signs in for the first time and user is created in Metabase, this fires an email without checking if the SMTP is setup or not. so it does validation on admin email field even when there’s no SMTP or emails being configured for the instance.