Framework
Reports that share this framework, grouped in one feed.
Setting a database password containing extended ASCII characters (e.g., è, Ö, Æ) is accepted by the Supabase UI, but subsequent dashboard connections to the PostgreSQL database fail with authentication errors, making the database inaccessible through the dashboard.
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.
Importing a CSV file with a geometry column where individual rows have a large number of points (over approximately 1000) causes the Supabase dashboard import process to hang. This prevents data import for such rows and requires manual splitting or exclusion.
Creating or deleting a Send Email hook in the Supabase dashboard silently nullifies all custom SMTP fields and resets rate_limit_email_sent to default, leading to complete silent auth email failure when the hook is later disabled.
updateTable compares PK column names in display order with primary_keys from the database (key order), causing a name change or an out-of-order composite PK to be treated as a PK change. Studio then drops and re-adds the PK in separate transactions, which fails when foreign keys reference it or silently reorders the PK.
When filtering objects in the Storage explorer using the search box, deleting one or more of the filtered objects causes the file list to reset and display the full unfiltered bucket contents, while the search input still shows the filter text. This leaves the UI in an inconsistent state and may mislead users into thinking matching items still exist.
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.
useGitHubAuthorizationQuery makes redundant retries (3x by default) for 404 responses because retry: false specified in a FIXME was not implemented.
The AI rename feature in the Supabase Dashboard SQL Editor fetches a valid title and description from the AI endpoint, but the Name field in the Rename dialog remains unchanged after the loading state finishes.
The React pattern in examples/prompts/use-realtime.md contains a syntax error due to using await inside a synchronous useEffect callback, preventing users from copying the example. The fix wraps the asynchronous setup in an inner async function and returns a proper cleanup function.