Home / RLS / Fix PGRST116: Cannot coerce the result

Supabase RLS · Error fix

Fix PGRST116: Cannot coerce the result to a single JSON object

01 What the error says

response

{
  "code": "PGRST116",
  "message": "Cannot coerce the result to a single JSON object",
  "details": "The result contains 0 rows"
}

.single() asks the Data API for exactly one object. When the query returns 0 rows or more than 1, it answers HTTP 406 with PGRST116. The details line tells you which: 0 rows or 2 rows and so on.

02 "But the row exists": that's RLS

RLS doesn't raise an error for rows you can't see. It filters them out, so the query returns 0 rows and .single() turns that into PGRST116. You see the row in the dashboard because the dashboard bypasses RLS.

03 Find out which one

debug.ts

const { data: { user } } = await supabase.auth.getUser();
console.log('calling as', user?.id ?? 'anon');   // null → cause 1

// same query without .single(): see how many rows come back
const { data } = await supabase.from('profiles').select('*').eq('id', id);
console.log(data.length);   // 0 with a valid id → RLS is hiding it

04 The fix

• Cause 1: make the request carry the user's session. On the server, create the Supabase client from the request cookies so auth.uid() resolves.
• Cause 2: if other users should see this row, add a policy for that case (for example, a public profile field). Don't widen it to using (true) on private data.
• Zero rows is a normal answer (a profile not created yet): use .maybeSingle(). It returns data: null for 0 rows and still errors on more than 1.

profile.ts

const { data: profile, error } = await supabase
  .from('profiles').select('*').eq('id', user.id).maybeSingle();
if (!profile) { /* first visit: create it */ }

FAQ