Google or Social Login Not Working in Base44 App
You have enabled Google login (or another social OAuth provider) in your Base44 app, but clicking the social login button results in an error. Users may see a Google error page, a "redirect_uri_mismatch" message, or get redirected back to the login page without being authenticated.
This issue is particularly frustrating because social login often works perfectly in the Base44 editor preview but breaks in the published version of the app. The OAuth flow requires precise URL matching that can easily go wrong between environments.
Error Messages You Might See
Common Causes
- The OAuth redirect URI configured in your Google/social provider console doesn't match the published app's URL
- Client ID or client secret was copied incorrectly or contains extra whitespace
- The OAuth consent screen has not been published or is still in testing mode with limited test users
- The app's published domain changed (e.g., custom domain added) but the OAuth provider wasn't updated
How to Fix It
Double-check the redirect URI in your OAuth provider's console (e.g., Google Cloud Console). It must exactly match the URL Base44 uses for the callback, including the protocol (https) and any path segments.
If using Google, make sure your OAuth consent screen is configured for production use, not just testing. In testing mode, only explicitly listed test users can log in.
OAuth configuration involves multiple systems and precise URL matching. If you've verified the basics and the issue persists, a developer experienced with OAuth flows can quickly identify the mismatch.
Real developers can help you.
Rudra Bhikadiya
I build and fix web apps across Next.js, Node.js, and DBs.
Comfortable jumping into messy code, broken APIs, and mysterious bugs.
If your project works in theory but not in reality, I help close that gap.
Jared Hasson
Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever
Dor Yaloz
SW engineer with 6+ years of experience,
I worked with React/Node/Python
did projects with React+Capacitor.js for ios
Supabase expert
prajwalfullstack
Hi Im a full stack developer, a vibe coded MVP to Market ready product, I'm here to help
Richard McSorley
Full-Stack Software Engineer with 8+ years building high-performance applications for enterprise clients. Shipped production systems at Walmart (4,000+ stores), Cigna (20M+ users), and Arkansas Blue Cross. 5 patents in retail/supply chain tech. Currently focused on AI integrations, automation tools, and TypeScript-first architectures.
Krishna Sai Kuncha
Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : )
legrab
I'll fill this later
Jaime Orts-Caroff
I'm a Senior Android developer, open to work in various fields
Tejas Chokhawala
Full-stack engineer with 5 years experience building production web apps using React, Next.js and TypeScript.
Focused on performance, clean architecture and shipping fast.
Experienced with Supabase/Postgres backends, Stripe billing, and building AI-assisted developer tools.
Nam Tran
10 years as fullstack developer
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
Why does Google login fail in my published Base44 app but work in preview?
The published app uses a different URL than the editor preview. You need to add your published app's URL as an authorized redirect URI in the Google Cloud Console.
How do I fix redirect_uri_mismatch in Base44?
Go to your OAuth provider's console and add the exact callback URL your published Base44 app uses. The URL must match exactly, including https and the full path.