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
If I am logged out but have navigated to the /wallet page and attempt to Withdraw, the message shown will be:
Error: Cannot read property 'id' of null
This gives the user the impression the withdrawal issue is with the Stacker.News website, when it is actually user error.
This occurred, in my instance, on my Android where I switched to my LN wallet (WoS) to get the invoice for my withdrawal to pay. When I switched back to SN, my browser session did not persist, so I was essentially no longer logged in.. This can occur with incognito mode / Private browsing when switching back and forth between the browser and other apps.
This request is to have SN respond with a better error message when a user attempts to withdraw when not logged in. It may even be good to display a warning message when providing a response for GET on /wallet and the user is not logged in / not authenticated.
The text was updated successfully, but these errors were encountered:
If I am logged out but have navigated to the /wallet page and attempt to Withdraw, the message shown will be:
This gives the user the impression the withdrawal issue is with the Stacker.News website, when it is actually user error.
This occurred, in my instance, on my Android where I switched to my LN wallet (WoS) to get the invoice for my withdrawal to pay. When I switched back to SN, my browser session did not persist, so I was essentially no longer logged in.. This can occur with incognito mode / Private browsing when switching back and forth between the browser and other apps.
This request is to have SN respond with a better error message when a user attempts to withdraw when not logged in. It may even be good to display a warning message when providing a response for GET on /wallet and the user is not logged in / not authenticated.
The text was updated successfully, but these errors were encountered: