[Enhancement] Add an offline-capable error state for the `SESSION_EXPIRED` request rejection

[RUKAYAT-CODER]

Overview

The axios request interceptor rejects with code: 'SESSION_EXPIRED' and immediately calls useAppStore.getState().logout() whenever sessionExpiresAt has passed. That check uses local device time and runs before any network attempt, so a device with a skewed clock — or one that has been offline long enough for a token to expire while an OTA-cached session is still valid server-side — logs the user out with no opportunity to recover. SessionExpiredModal exists but the rejection path does not surface it.

Specifications

Features:

• A grace window that attempts a refresh before forcing logout
• Clock-skew tolerance derived from a server Date header rather than device time alone
• SessionExpiredModal shown instead of a silent logout

Tasks:

• Record server-client clock offset from response Date headers and apply it to expiry checks
• Attempt a refresh before logging out when expiry is detected locally
• Route the SESSION_EXPIRED rejection through SessionExpiredModal
• Add tests covering a skewed device clock and an offline expiry

Impacted Files:

• src/services/api/axios.config.ts
• src/components/common/SessionExpiredModal.tsx
• src/services/sessionRestoration.ts
• src/__tests__/services/sessionExpiry.test.ts

Acceptance Criteria

• A skewed device clock does not force a logout
• The user sees an explanation rather than being silently signed out
• A refresh is attempted before the session is discarded

[MaskedTerminal]

Dear Maintainer,

I’d like to work on this issue and would appreciate it if you could assign it to me.

I understand the task involves improving session-expiry handling by accounting for server-client clock skew, adding a grace period with a refresh attempt before logout, and routing SESSION_EXPIRED through the existing SessionExpiredModal instead of silently signing the user out.

I’ll also add tests covering skewed device clocks, offline expiry, refresh attempts, and the updated session restoration flow.

I’m ready to take this up and will follow the project’s existing session and API architecture.

Thank you!

[Peculiarr7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!