Lovable
Lovable app login not working on mobile? How to fix sign-in
November 17, 2026 · 6 min read

If sign-in works in your Lovable web app but fails in the Android or iOS version, the cause is almost always one of four things: Google blocking embedded sign-in, wrong redirect URLs, email links opening the browser, or sessions not being saved.
All four come from the same root. In a mobile app, sign-in can move between your app, the phone's browser and your email app, and each hand-over can fail. Below, each problem has its symptom and its fix, so you can match what you see. Most fixes are settings; some need a prompt to Lovable or help from a developer.
Why login breaks in the app
Most Lovable apps use Supabase for sign-in. On the web, the whole sign-in happens in one browser tab. In a mobile app it can pass through your app, the phone's browser and your email app, and if one hand-over fails, the user ends up stuck or signed out.
Which hand-over fails depends on the type of app you built:
- Android TWA: your app runs in Chrome. Login usually works like on the web. Problems are mostly redirect URLs.
- WebView wrapper (most iOS apps): your app runs in an embedded view. Google blocks its sign-in there, and links may open outside the app.
If you are not sure which type you have, read Trusted Web Activity vs WebView.
Problem 1: Google says "This browser or app may not be secure"
You may also see the error "disallowed_useragent". Google does not allow its sign-in page inside embedded web views. This is a Google security rule, not a bug in your app.
Fix: open Google sign-in in the phone's real browser, then send the user back to the app. In a Capacitor app, a browser plugin and a deep link usually do this; a native Google sign-in plugin is another option. Ask Lovable or a developer to set it up, then test it on a real iPhone.
Once Google sign-in works on iPhone, remember that Apple usually expects Sign in with Apple next to it. See Sign in with Apple for web apps.
Problem 2: Sign-in lands on the website, not the app
In this case, after login the user lands on your website in the browser, while the app still shows the sign-in screen.
Fix: check the Redirect URLs in your Supabase Auth settings, because Supabase only sends users back to addresses on that list. For a TWA, the address is your normal website. For a wrapper app, it is usually a deep link with a custom app scheme, so your app must also be set up to open that link. Our guide on deep links in Android and iOS apps covers the setup.
Problem 3: Email links open in the browser
Magic links, sign-up confirmations and password resets all arrive by email. When the user taps one, the phone opens the browser instead of your app, so they are signed in there but not in the app.
Fix: use links the phone can open in your app: verified App Links on Android and Universal Links on iPhone. Alternatively, send a one-time code by email instead of a link. The user types the code into the app, so no hand-over is needed at all.
Problem 4: Users are signed out after closing the app
Here the user signs in, closes the app, and later has to sign in again.
Fix: first check that your Supabase client keeps the session, with persistent sessions and token refresh turned on. In a wrapper app, saving the session in the app's native storage is more reliable than browser storage. In a TWA the session lives in Chrome, so clearing Chrome data signs users out. Our article on session persistence in TWAs goes deeper.
A test plan for sign-in
- Sign up with email on a real phone, and confirm the email.
- Sign in with every provider you offer.
- Reset your password from the email link.
- Close the app fully, wait, and open it again.
- Sign out, then sign in as a different user.
- Repeat on both Android and iPhone.
Where PWAtoApp fits
PWAtoApp builds your Lovable app into Android and iOS apps for €49.99 once, with unlimited builds, so you can rebuild after each fix. The fixes themselves happen in your Lovable project and Supabase, because that is where sign-in lives. For the full path, start with converting your Lovable product to Android and iOS.
FAQ
Do I need to change my Lovable app to fix this?
Sometimes. Redirect URL fixes happen in Supabase settings. Google sign-in on iPhone and email links usually need changes in the Lovable project as well.
Why does login work on Android but not on iPhone?
Android apps built as a TWA run in Chrome, which Google trusts. iOS wrapper apps use an embedded web view, which Google blocks for its sign-in page.
Is email and password login easier?
Yes. Plain email and password sign-in happens fully inside your app, so it rarely breaks. It is a good fallback while you fix social logins.
Ready to build for Android and iOS?
€49.99 once includes unlimited Android APK and AAB plus iOS IPA builds, all from one dashboard.
Build my app