bonaminandClaude Opus 5.5
cae5d75005
AuthRehydrator called logout() on ANY failure of /api/auth/me, including a network error. So opening the app while WiFi was flaky, while the server was restarting, or right after its IP changed silently threw the waiter back to the login screen and offline mode could not survive an app restart. Now a network error keeps the token and retries every 5s; a real server answer (401 and other errors) still ends the session as before. Verified on the Android emulator: cold start with the backend stopped keeps the token; starting the backend brings the app to /tables on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The file is empty.