minstrel

At launch the stored session cookie loads from the Keystore off the main
thread. A request sent before that finished went out without it, typically
the library sync that fires as soon as the server answers. The server then
answered 401, and the interceptor cleared the store on any 401, which also
stopped the load from restoring the cookie and wrote null over the stored
one. The user had to sign in on every launch. A session lost mid-use also
left them on Home with every request failing, because the app only routes
to sign-in when it starts.

- The interceptor waits for the stored cookie to load before attaching it,
  bounded by the existing hydration deadline.
- A 401 signs out only when the request carried the current cookie
  (compare-and-clear). A request sent without one, or with a cookie a newer
  sign-in has replaced, leaves the login alone.
- When the server refuses the session mid-use, the app opens the sign-in
  screen. A sign-out from Settings does not trigger this.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-06 10:22:59 -05:00

.idea

refactor(android): unify offline detection into NetworkStatusController

2026-06-05 12:06:22 -04:00

app

fix(android): the app stops signing itself out at launch (#6911 )

2026-11-06 10:22:59 -05:00

config

chore(android): extend detekt TooManyFunctions exception to @Database

2026-05-22 16:45:47 -04:00

gradle

docs: Android comments say what the app does, not how it came to be (#6277 )