Supabase
Published reports for this stack, with severity, affected version, and a direct path into each diagnostic.
The Supabase documentation example for assigning role custom claims with Firebase Admin SDK incorrectly references `userRecord.id`, which does not exist on Firebase UserRecord objects. The correct property is `userRecord.uid`. Following the example as written causes a runtime error when calling `setCustomUserClaims` with `undefined` as the user identifier.
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.
The SSL Configuration documentation page lacks clear navigation to find SSL settings in the dashboard, causing user confusion.
Studio's default-privileges state query uses an inner join to pg_roles, excluding PUBLIC grants (grantee OID 0) from aclexplode, causing grants TO PUBLIC to be invisible and grant_count to be 0.
When both [local_smtp].enabled and [auth.email.smtp].enabled are true in config.toml, the Supabase CLI configures the auth service to use the real SMTP server instead of the local test SMTP server.
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.
Supabase dashboard prevents users on the free plan from creating a second project in an organization that already has one active project, despite the free tier historically allowing two active projects. The UI does not display any project limit or quota error, leaving the user unable to determine whether the block is intentional.
The reported Supabase project restore remains stuck indefinitely. Given the sparse issue details, the most probable root cause is a restore transaction blocked by long-running queries or lock contention, with no configured timeout or progress tracking.