Greptile Summary

This PR suppresses Sentry noise by distinguishing expected UnauthorizedError failures during token refresh (expired/revoked/scope-mismatched tokens) from unexpected failures. The change mirrors the pattern already established in fetchCreatorStatus in auth-context.tsx.

• lib/request.ts: Wraps the existing Sentry.captureException call with an UnauthorizedError guard; the UnauthorizedError path logs via console.warn and still proceeds to logout(), while any other non-keychain error continues to capture to Sentry.
• tests/lib/use-api-request.test.tsx: Adds one new test verifying that logout is invoked and Sentry.captureException is not when the refresh endpoint returns 401.

Confidence Score: 5/5

Safe to merge — the change is a targeted two-branch addition to an existing error handler with no effect on the happy path or the KeychainUnavailableError path.

The diff is four lines in the production code and a single new test. The three distinct refresh-failure paths are each individually tested, and the new UnauthorizedError branch correctly falls through to logout() just as the pre-existing catch-all did. The pattern is consistent with how fetchCreatorStatus in auth-context.tsx already handles the same case.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[requestAPI returns 401] --> B{UnauthorizedError?}
    B -- No --> C[throw error]
    B -- Yes --> D[refreshToken]
    D -- success --> E[retry requestAPI with new token]
    D -->|KeychainUnavailableError| F[throw original error - no logout, no Sentry]
    D -->|UnauthorizedError| G[console.warn then logout then throw original error]
    D -->|other error| H[Sentry.captureException then logout then throw original error]

_{Reviews (1): Last reviewed commit: "Skip Sentry capture when token refresh f..." | Re-trigger Greptile}

Assigning @nyomanjyotisa per Gianfranco.