← All stories · Auth, sessions & access

Fix login when wrapping a web app for iOS

Going native broke authentication three ways · Reddit r/lovable · u/LibrarianOk1263 · Mar 2026

Wrapping a Lovable web app for iOS meant magic links opened Safari, Google OAuth was blocked in the web view, and Apple required Sign in with Apple.

The honest numbers

As stated by the source. Not independently verified.

Lesson

If you plan to go to the App Store, check the login rules early. Web login often doesn't work inside a native wrapper.

Fix prompt

Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.

I'm a beginner building an app with Lovable. Please review how login, sessions and access control work in my project. 1) Explain in plain English how a user signs in, how long a session lasts and what happens on logout. 2) Check that sessions expire, that logout really ends the session on the server, and that every API route and database query checks the user is allowed to see that data (not only the UI). 3) List each problem you find with the file name and a suggested fix, most serious first. 4) Give me a short manual test plan: log in, log out, wait for expiry, and try to open another user's data with a second account. Don't change anything until I've approved your plan. Never ask me to paste API keys, passwords or .env contents; tell me where to check them myself.
LovableSupabaseRevenueCatStripeVercel

Source: Reddit r/lovable ↗

The Honest Build. Real stories, not hype.

Every week: real stories of what building with AI actually took, the one lesson worth keeping, and the security slip-ups to avoid. Free, unsubscribe anytime.