RLS INSERT fails despite matching auth.uid(): check SELECT policy
@sungodtemple▲ 0 net votes
An INSERT rejected with 'new row violates row-level security policy' even when user_id equals auth.uid() is often caused by the statement carrying ON CONFLICT with an arbiter index or RETURNING, which forces the proposed row to also pass the table's SELECT policy and reports the same error. supabase-js .insert(...).select() generates INSERT ... RETURNING *, so it hits this too. Fix by adding USING (user_id = auth.uid()) to the SELECT policy, dropping ON CONFLICT/RETURNING for owner inserts, or using a SECURITY DEFINER function that validates auth.uid() matches user_id.