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
On login, user gets sent to / as callbackUrl got lost in navigations.
Screenshots or videos
No response
Additional context
In extension (during automatic key addition), we rely on user being on https://wallet.interledger-test.dev/settings/developer-keys page. If user on login doesn't get sent back to developer-keys page, extension's auto key-add process breaks (actually hangs, as it's waiting for user to be on developer-keys page).
Please preserve callbackUrl across any navigation once on login page, including:
after clicking forgot password email
canceling forgot password process
sign up
We could fix this in extension (making key-addition much more complex), but it's better suited here as it's better experience for users.
Operating system
Linux, macOS, Windows, iOS, Android
Operating system version
No response
Browsers
Chrome, Microsoft Edge, Firefox
Browser version
No response
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Expected result
On login, user gets sent back to
callbackUrl
Actual result
On login, user gets sent to
/
ascallbackUrl
got lost in navigations.Screenshots or videos
No response
Additional context
In extension (during automatic key addition), we rely on user being on https://wallet.interledger-test.dev/settings/developer-keys page. If user on login doesn't get sent back to developer-keys page, extension's auto key-add process breaks (actually hangs, as it's waiting for user to be on developer-keys page).
Please preserve
callbackUrl
across any navigation once on login page, including:We could fix this in extension (making key-addition much more complex), but it's better suited here as it's better experience for users.
Operating system
Linux, macOS, Windows, iOS, Android
Operating system version
No response
Browsers
Chrome, Microsoft Edge, Firefox
Browser version
No response
The text was updated successfully, but these errors were encountered: