MetaMask / MetaMask/metamask-mobile
[Sentry] RefreshTokenHttpError: Failed to refresh JWT token (HTTP 401)
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
Sentry Issue: [METAMASK-MOBILE-5K92](https://metamask.sentry.io/issues/7320925153/?referrer=github_integration)
```
SeedlessOnboardingControllerError: SeedlessOnboardingController - Invalid refresh token
at tryCallOne (app:///main.jsbundle:1:1181)
at anonymous (app:///main.jsbundle:1:1875)
...
(5 additional frame(s) were not displayed)
RefreshTokenHttpError: Failed to refresh JWT token (HTTP 401)
at RefreshTokenHttpError (app/core/OAuthService/AuthTokenHandler.ts:23:5)
at ?anon_0_ (app/core/OAuthService/AuthTokenHandler.ts:75:38)
at tryCallOne (app:///main.jsbundle:1:1181)
at anonymous (app:///main.jsbundle:1:1875)
...
(8 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start by reading app/core/OAuthService/AuthTokenHandler.ts at lines 23 and 75, then correlate the Sentry trace with the refresh-token flow. Trace the HTTP 401 path; done means the refresh-token failure is resolved and the reported error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- authentication, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100