Get Supabase RLS right for a mobile app
8 months and 2 App Store rejections, with Supabase RLS as the big hurdle · Reddit r/replit · u/According-Sky8561 · Sep 2025
Two near-beginners shipped a mobile app built on Replit. The steepest learning curve was getting row-level security policies right.
The honest numbers
- Says 8 months of building
- Says 2 App Store rejections before going live
As stated by the source. Not independently verified.
Lesson
Write down who can read and write each table before you build, then test RLS with a second account.
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 Replit. 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.
Source: Reddit r/replit ↗