Skip to content

Latest commit

 

History

1 Commit

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

supabase-avatars

Profile photos on Supabase Storage. The avatars bucket is public so each photo has a public URL. A user's avatar lives at <user_id>/avatar.png, and the app uploads it with upsert: true so a new photo replaces the old one at that same path.

Run it locally

npm install
supabase start
npm run repro

scripts/repro.mjs signs in as alice@example.com (password password123) and uploads to the same path twice — once as a new photo, once as a replacement.

The problem

The very first upload for a user always works. Replacing an existing avatar fails.


This repository is an intentionally broken fixture. It exists to benchmark how coding agents diagnose Supabase problems. The storage policies in supabase/migrations/ contain a deliberate misconfiguration. Do not copy this configuration into a real project.

About

Eval fixture: Supabase Storage upsert fails when replacing an existing avatar

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages