MetaMask / MetaMask/metamask-mobile
Error: Invalid hex ID length. Expected 64 characters, got 16
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
Sentry Issue: [METAMASK-MOBILE-4GZ1](https://metamask.sentry.io/issues/6920201771/?referrer=github_integration)
```
Error: Invalid hex ID length. Expected 64 characters, got 16
at isSamplingMetaMetricsUser (app/core/Engine/controllers/network-controller/utils.ts:139:45)
at shouldCreateRpcServiceEvents (app/core/Engine/controllers/network-controller/utils.ts:118:30)
at trackRpcEndpointEvent (app/core/Engine/controllers/network-controller/messenger-action-handlers.ts:141:34)
at onRpcEndpointDegraded (app/core/Engine/controllers/network-controller/messenger-action-handlers.ts:95:24)
at ?anon_0_ (app/core/Engine/Engine.ts:458:30)
...
(8 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start in app/core/Engine/controllers/network-controller/utils.ts at isSamplingMetaMetricsUser around line 139, then trace its callers in shouldCreateRpcServiceEvents and messenger-action-handlers.ts. Reproduce the Sentry error and inspect how the 16-character value reaches the hex ID check. Done means the invalid-length case is handled without the reported error, with coverage for the affected flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100