Remember when I talked about “Sign in with Google?” That works really well on the web, but: Once you’re wrapping your web app into a native mobile app, things turn very ugly very soon. In a hosted WebView, Google won’t let you render the sign in button to begin with – unless you override the WebView’s user agent string. After that, you’re still screwed if you rely on the default sign in workflow as this would open a popup window from which the user then can’t navigate back into your app.
So, how to proceed? You could switch to the redirect-based sign in flow, but: Then Google calls back to your server (rather than the client) after sign in is complete. Hence, you have to rework your authentication logic and you can’t easily test this locally.
But Capacitor ( https://capacitorjs.com/) offers social sign in plugins, no?
👉 In my experience: most don’t work reliably out of the box.
👉 If you need rock-solid auth: go native for Android/iOS.
🔐 What did I do instead? Disabled "Sign in with Google" in the Android app -- for now -- in favor of my own "Continue with email..." implementation 😅