MetaMask / MetaMask/metamask-mobile
TypeError: E.flushQueue is not a function. (In 'E.flushQueue()', 'E.flushQueue' is undefined)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
Sentry Issue: [METAMASK-MOBILE-2WMS](https://metamask.sentry.io/issues/5971573130/?referrer=github_integration)
```
TypeError: E.flushQueue is not a function. (In 'E.flushQueue()', 'E.flushQueue' is undefined)
at API.disableQueue (node_modules/react-native/Libraries/Animated/NativeAnimatedHelper.js:141:11)
at API.unsetWaitingForIdentifier (node_modules/react-native/Libraries/Animated/NativeAnimatedHelper.js:130:11)
at .value (node_modules/react-native/Libraries/Animated/animations/Animation.js:83:32)
at start (node_modules/react-native/Libraries/Animated/animations/TimingAnimation.js:124:16)
at .value (node_modules/react-native/Libraries/Animated/animations/TimingAnimation.js:136:7)
...
(21 additional frame(s) were not displayed)
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Sentry report and inspect NativeAnimatedHelper.js, Animation.js, and TimingAnimation.js at the stack-trace locations. Trace the disableQueue and unsetWaitingForIdentifier calls to determine the relevant failure path; done means the reported TypeError is prevented or resolved and the affected animation behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100