Each step of signing in or out pushed a history entry: startAuthFlow, endSession and signOut. In the installed app, Back from the dashboard went to the server's sign-in page (already used, so it failed with a state mismatch) and then to /login, which started another sign-in, so Back never left the app (forum t/232).
Those steps now use location.replace / navigate(..., { replace: true }), and /login reached with a session in hand goes on into the console. The server's sign-in page needs the same change (inbuxa/inbuxa-server#403); with both, the sign-in collapses into the dashboard's entry and Back from there leaves the app.
Each step of signing in or out pushed a history entry: `startAuthFlow`, `endSession` and `signOut`. In the installed app, Back from the dashboard went to the server's sign-in page (already used, so it failed with a state mismatch) and then to /login, which started another sign-in, so Back never left the app (forum t/232).
Those steps now use `location.replace` / `navigate(..., { replace: true })`, and /login reached with a session in hand goes on into the console. The server's sign-in page needs the same change (inbuxa/inbuxa-server#403); with both, the sign-in collapses into the dashboard's entry and Back from there leaves the app.
Fixes #215
Each step of signing in or out pushed a history entry: the console's
start of sign-in, the end of a session, and signing out. In the
installed app, Back from the dashboard then went to the server's
sign-in page (already used, so it failed) and to /login, which started
another sign-in, so Back never left the app.
Those steps now replace the current page. /login reached with a
session in hand goes on into the console. With the server's sign-in
page doing the same (inbuxa-server #403), the whole sign-in collapses
into the dashboard's entry, and Back from there leaves the app.
Fixes#215
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Each step of signing in or out pushed a history entry:
startAuthFlow,endSessionandsignOut. In the installed app, Back from the dashboard went to the server's sign-in page (already used, so it failed with a state mismatch) and then to /login, which started another sign-in, so Back never left the app (forum t/232).Those steps now use
location.replace/navigate(..., { replace: true }), and /login reached with a session in hand goes on into the console. The server's sign-in page needs the same change (inbuxa/inbuxa-server#403); with both, the sign-in collapses into the dashboard's entry and Back from there leaves the app.Fixes #215