Lovable Google login not working? Fixing Google sign-in
Last reviewed 21 November 2026
Google sign-in is usually the first thing people tap, so when it fails, they leave. The error message tells you most of what’s wrong, as long as you know which kind of Google setup your app has. Here’s how to read it.
Check whether your app uses Lovable’s managed Google sign-in or your own Google Cloud credentials. With your own, most failures are a redirect address that doesn’t match exactly, or a new custom domain that hasn’t been added. In a mobile app, Google blocks sign-in inside embedded web views, so use the system browser.
Which Google setup do you have?
- Managed by Lovable is the default on Lovable’s built-in backend. Lovable runs the Google connection and needs no setup. Google’s screen shows Lovable as the app asking for access, and Lovable adds its own screen with your project’s name. See Lovable’s Google sign-in guide.
- Your own Google Cloud credentials show your own app name and verified domain, but you set them up and keep them working yourself.
- Your own Supabase project: Google sign-in is set up in Supabase and Google Cloud, following Supabase’s guide.
You can switch between managed and your own credentials at any time, and Lovable says existing user accounts aren’t affected.
Match the error to the fix
| What you see | Usually | Fix |
|---|---|---|
| Error 400: redirect_uri_mismatch | The address Google sends people back to isn’t registered in your Google Cloud client | Make them match exactly: https, domain, path and trailing slash |
| Works in preview, fails on the live site or your domain | The live address is missing from your sign-in settings | Add it to the redirect URLs, and to Google Cloud if you use your own credentials |
| Blocked at Google’s screen, or only some people can sign in | Your Google project is in Testing and the app asks for more than basic sign-in, such as Calendar or Drive access | Add test users, or publish the app in Google Cloud |
| “Google hasn’t verified this app” | The app asks for sensitive permissions before Google has verified it | Ask only for basic sign-in permissions, or complete verification |
| Lovable or a supabase.co address on Google’s screen | Managed sign-in, or your own Supabase project without a custom domain | Managed: switch to your own Google credentials and verify your brand. Own Supabase: set up a custom domain for the Supabase project, such as auth.yourdomain.com, and verify your brand in Google Cloud |
| Error 403: disallowed_useragent | Sign-in opened inside an embedded web view, in a mobile wrapper or an in-app browser | Open sign-in in the system browser (see below) |
Getting redirect addresses right
Google’s rule is strict: the address must match a registered one exactly, including https, capitals and any trailing slash, as its OAuth guide explains.
- With your own credentials in Lovable, create a Google client of type Web application. Lovable says mobile and desktop client types don’t work with its sign-in flow.
- Lovable sends Google one of the redirect addresses you select, so only select ones you’ve also added in Google Cloud.
- When you connect a custom domain, Lovable lists its redirect address but doesn’t select it. Add it in Google Cloud first, then select it, or sign-in breaks with a mismatch. Managed sign-in needs no change.
- With your own Supabase project, add your app’s address under Authorized JavaScript origins in Google Cloud and the Supabase callback address under Authorized redirect URIs, then set the Site URL in Supabase.
Testing, production and “unverified app”
From Google’s help: a project in Testing is limited to 100 listed test users, and their access expires after seven days. These limits don’t apply when the app asks only for name, email address and profile, which is all basic Google sign-in needs. So if your app only signs people in, Testing isn’t why some people are blocked. If it asks for more, such as Calendar or Drive access, add test users or click Publish app. Google may also need to verify your app before it shows your name and logo on the sign-in screen.
Google sign-in inside a mobile app
Google’s policy forbids sign-in inside web views controlled by the app, and shows “disallowed_useragent” when it happens. In a wrapped Lovable app, open sign-in in the system browser sheet and send people back with a custom-scheme link, which Lovable’s redirect settings support. Lovable doesn’t support a separate native Google sign-in client. More in turning a Lovable app into a mobile app.
Questions founders ask
Why does Google say “Lovable wants to access your account”?
Because the app uses Lovable’s managed Google sign-in. To show your own app name, connect your own Google Cloud credentials and complete Google’s brand verification.
Will switching to my own Google credentials log everyone out or lose accounts?
Lovable says you can switch between managed and your own credentials at any time, and existing user accounts aren’t affected.
Why can only some people sign in with Google?
If your app asks for more than basic sign-in, such as Calendar or Drive access, and your Google Cloud project is in Testing, only listed test users can sign in. Publish the app in Google Cloud. For basic sign-in only, look at redirect addresses and your sign-in settings instead.