Session expiration — signed out unexpectedly

MileLedger authenticates through Google Sign-In backed by Firebase. Firebase issues a short-lived ID token and a longer-lived refresh token. The app silently refreshes your session in the background as long as internet is available and your Google account is in good standing.

Sessions can expire or be invalidated in the following situations: you have not used the app for an extended period and the refresh token has expired; your Google account password was changed recently; a security event (suspicious activity, new device sign-in, forced sign-out) was detected by Google; you revoked MileLedger's access in your Google account permissions; or a persistent network failure prevented the token from being refreshed.

On phone: MileLedger may display a sign-in prompt when you open the app, or the Expenses tab or web sync features may stop working while local drives continue to appear normally.

On the web app: you are redirected to the sign-in screen at /app when you attempt to load your data.

Sign back in with the same Google account. On phone, tap More → Sign In → Continue with Google and select your account. On the web, click 'Sign in with Google' at /app.

Your locally stored drives on the phone are unaffected by signing out — they are saved in SwiftData on the device. Only cloud-synced features (web access, expense logging) require an active sign-in.

Open the app at least briefly every few weeks while connected to the internet. This gives Firebase the opportunity to refresh the session token automatically.

Ensure MileLedger has access to the internet under Settings → MileLedger → Mobile Data (and Wi-Fi).

If you recently changed your Google account password, you will need to sign in once after the change. Subsequent sessions should be stable.

Check your Google account at myaccount.google.com → Security → Third-party apps with account access to confirm that MileLedger still has the permissions it needs.