A dropped connection no longer signs you out
A weak signal, a slow server, a restart on our end — none of those are supposed to cost you your session, and now none of them do.
Only a rejected token signs you out now
Staying signed in runs on two tokens: a short-lived one that rides along with every request, and a longer one that is used only to fetch a new short one when it expires. Until now, anything that went wrong while fetching that new token — no network, a timeout, a server answering mid-restart — was treated the same as the long-lived token itself being no good, and cleared it. The long-lived token is good for sixty days; a bad moment on the network should not spend it.
The rule is narrower now. The only thing that signs you out is Ridgeback saying, in so many words, that your token is invalid. A dropped connection, a timeout, a server error, or a reply that doesn't parse all leave you signed in, and whatever you were doing just tries again. iPhone, Android and the desktop all follow the same rule.
Two requests, one token
A second gap only showed up under load: two requests hitting an expired token at the same moment would each reach for the long-lived token on their own, and whichever one went second was handed a token the first had already used up — which used to read as invalid and sign you out, for something that was never actually wrong. Requests that need a fresh token now take a shared turn instead of asking twice, on every platform.
Get the build
iPhone builds arrive through TestFlight. Android, macOS and Linux downloads are on the home page.