A remote bridge session that hits an expired token now refreshes and retries once.
What's wrong with this entry?
A remote bridge session that gets a 401 during startup now refreshes the OAuth token and tries again, instead of failing. The refresh runs at most once per access token, and if it lands on the final attempt an extra call is made with the fresh token.
- Reports
bridge_repl_v2_init_401_refreshwith a flag saying whether a token was actually refreshed or no refresh was available. - Disconnect reasons "untrusted_device" and "session_stale_relogin" are now classified as auth problems rather than terminal failures, so they take the recoverable path.
bridge_repl_v2_init_401_refresh
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.