Framework
Reports that share this framework, grouped in one feed.
Clearing a Storage policy's USING or WITH CHECK expression in the Studio dashboard shows a success toast but does not persist the change because the payload omits undefined fields, leaving the old expression active and potentially causing security misconfigurations.
Supabase Studio's database password inputs (Reset database password and new project database password) only set autoComplete="off", which password managers like LastPass ignore. This allows the user's Supabase account password to be autofilled into the database password field, creating a credential reuse vulnerability and potential accidental database password exposure.
updateTable compares primary key column names in display order with the backend's primary_keys array (which comes back in key order). A rename or an out-of-order composite primary key like (b, a) is falsely detected as a PK change, causing Studio to drop and re-add the constraint in separate transactions. This fails when a foreign key references the primary key, blocking unrelated edits, or silently rebuilds the constraint and reorders columns when no FK exists.
In Supabase Dashboard Authentication > Users, the user details drawer cannot be closed using the top-right close/collapse control. The panel remains open until navigating away; no JavaScript errors are logged.
After #50516, legacy JWT API keys are masked in ConnectSheet, but reveal/copy actions incorrectly call the secret key reveal API which fails on Supabase-managed projects, preventing users from accessing their service_role key.
On Android Chrome, the Authentication → Users filter form has no visible submit button, and pressing the keyboard's enter/go key does not trigger the filter. The form does not submit on mobile or desktop versions, but the issue is most severe on mobile where no button exists.
In the SQL Editor AI, clicking 'Accept Changes' sets a loading state and then returns early if the diff editor is not yet mounted, leaving the button in a perpetual loading state until the page is refreshed.
Supabase Studio Table Editor's updateTable compares primary key column names in display order with the server's key order, causing false positives for renaming or composite PK ordering, leading to unnecessary PK drop/re-add and failures when foreign keys depend on the PK.