The route guard counted an admin as signed in only while the hour-long access token was valid, so any fresh load after that went to the password page even though the refresh token was still good. On a phone, where Android reloads an installed app whenever it comes back, that meant signing in again nearly every time (reported on the forum, t/232).
The guard now also accepts a stored refresh token (hasSession()). The first request renews the access token through apiFetch, and a refused renewal ends the session as before.
The route guard counted an admin as signed in only while the hour-long access token was valid, so any fresh load after that went to the password page even though the refresh token was still good. On a phone, where Android reloads an installed app whenever it comes back, that meant signing in again nearly every time (reported on the forum, t/232).
The guard now also accepts a stored refresh token (`hasSession()`). The first request renews the access token through `apiFetch`, and a refused renewal ends the session as before.
Fixes #214
The route guard counted an admin as signed in only while the hour-long
access token was valid, so any fresh load after that went to the
password page even though the refresh token behind it was still good.
On a phone, where Android reloads an installed app when it comes back,
that meant signing in again nearly every time.
The guard now also accepts a stored refresh token. The first request
renews the access token, and a refused renewal ends the session as
before.
Fixes#214
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.
The route guard counted an admin as signed in only while the hour-long access token was valid, so any fresh load after that went to the password page even though the refresh token was still good. On a phone, where Android reloads an installed app whenever it comes back, that meant signing in again nearly every time (reported on the forum, t/232).
The guard now also accepts a stored refresh token (
hasSession()). The first request renews the access token throughapiFetch, and a refused renewal ends the session as before.Fixes #214