You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating a signup link using auth.admin.generateLink({ type: "signup" }), a database error results in a misleading message: "Database error finding user". This error message implies a problem with user lookup when the actual issue could be database configuration or connectivity.
In our case, the actual issue was a schema configuration problem with a Foreign Data Wrapper, but the error message led us to spend hours debugging user authentication flows instead.
Steps to Reproduce
Have any database configuration issue (in our case, incorrect schema reference)
Since this is a signup flow, the error message should:
Not imply we're looking for an existing user
Be more specific about the database error
Potentially include the actual database error (safely) in development mode
Actual Behavior
The error message suggests a problem with user lookup, which is misleading since:
This is a signup flow - we don't expect to find the user
The actual database error is obscured
The message leads developers to debug auth flows instead of database configuration
Suggested Improvements
More descriptive error message: "Database error during signup link generation"
In development, include the actual database error (sanitized if needed)
Consider adding a debug mode that provides more detailed error information
Environment
Supabase Auth version: (latest)
Running in: Docker/local development
Database: Postgres with Foreign Data Wrapper
Additional Context
The code in GoTrue shows that user lookup is part of the flow to handle different types of links, but the error messaging doesn't reflect this implementation detail, leading to confusion during debugging.
The text was updated successfully, but these errors were encountered:
Issue Description
When generating a signup link using
auth.admin.generateLink({ type: "signup" })
, a database error results in a misleading message: "Database error finding user". This error message implies a problem with user lookup when the actual issue could be database configuration or connectivity.In our case, the actual issue was a schema configuration problem with a Foreign Data Wrapper, but the error message led us to spend hours debugging user authentication flows instead.
Steps to Reproduce
generateLink
with type "signup":Expected Behavior
Since this is a signup flow, the error message should:
Actual Behavior
The error message suggests a problem with user lookup, which is misleading since:
Suggested Improvements
Environment
Additional Context
The code in GoTrue shows that user lookup is part of the flow to handle different types of links, but the error messaging doesn't reflect this implementation detail, leading to confusion during debugging.
The text was updated successfully, but these errors were encountered: