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
While implementing the custom /signin page I discovered users weren't redirected to the callbackUrl specified in the URI query and I had to pass it manually to the signIn function.
Is this the expected default behaviour?
To clarify: callbackUrl is present in the URI when users landed on the custom /signin page. It simply isn't caught by the signIn function. Maybe mentioning it in the docs would be great to help developers improve user experience.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
While implementing the custom
/signin
page I discovered users weren't redirected to thecallbackUrl
specified in the URI query and I had to pass it manually to thesignIn
function.Is this the expected default behaviour?
To clarify:
callbackUrl
is present in the URI when users landed on the custom/signin
page. It simply isn't caught by thesignIn
function. Maybe mentioning it in the docs would be great to help developers improve user experience.Beta Was this translation helpful? Give feedback.
All reactions