Invoices vanish after saving

Your invoices are saved. The app just isn’t allowed to read them back. Supabase checks a safety rule for every action (row level security), and the rule that lets people see their own invoices is missing. So the list always comes back empty, and nothing shows an error.

Editing and deleting are hit by the same missing rule.

1. Log in as a test user.
2. Create an invoice. The app says “Saved!”.
3. The list still says “No invoices yet.”
4. In Supabase › Table Editor › invoices, the new row is there.

With row level security on, a table needs one rule per action: read, create, edit and delete. A later migration (0003_policies_update.sql) dropped the read rule on invoices. Without it, Supabase hides every row and answers the app’s request with an empty list instead of an error, so the app shows its “no invoices” screen.

One short SQL change in Supabase. The app’s code stays the same.

1. In Supabase › SQL Editor, add the read rule back, for each user’s own invoices only:

   create policy "Users can view their own invoices"
     on public.invoices for select to authenticated
     using ((select auth.uid()) = user_id);

2. Don’t turn row level security off, and don’t use using (true). Both “fix” the list by showing every user’s invoices to everyone.
3. Add the same rule to your migrations, so the next database change doesn’t drop it again.

• Refresh: your invoices are listed again.
• Edit and delete one: both stick after a refresh.
• Log in as a second test user: they see only their own invoices.