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
Lets say you run flutter for web and specify port 7357, and in your auth URL settings you list your primary domain at the top as site url (https://primarydomain.com) and then at the bottom in redirect URLs you list your primary domain and local testing URI: (https://primarydomain.com, http://localhost:7357)
flutter run -d chrome --web-port=7357
While window.location.href == 'http://localhost:7357', signInWithOAuth works perfectly. It navigates to consent screen and then right back to http://localhost:7357:
However for anonymous users, this linkIdentity always redirects to "Site URL" (the primary domain), even if you specify a valid redirectTo URL that is stored in redirect URLs here:
willsmanley
changed the title
linkIdentity always redirects to "Site URL" instead of a valid "redirect URL"
linkIdentity always redirects to "Site URL" instead of a valid "redirect URL" (web)
Jan 23, 2025
Lets say you run flutter for web and specify port 7357, and in your auth URL settings you list your primary domain at the top as site url (https://primarydomain.com) and then at the bottom in redirect URLs you list your primary domain and local testing URI: (https://primarydomain.com, http://localhost:7357)
While
window.location.href == 'http://localhost:7357'
,signInWithOAuth
works perfectly. It navigates to consent screen and then right back to http://localhost:7357:However for anonymous users, this
linkIdentity
always redirects to "Site URL" (the primary domain), even if you specify a valid redirectTo URL that is stored in redirect URLs here:This is a supabase side issue, not specific to google or apple or other oauth provider.
It's also not really a flutter SDK issue, it is a supabase backend issue (I think) but theres not a general place to open an issue as far as I know.
The text was updated successfully, but these errors were encountered: