Crash report: `Error: Missing four byte sig`
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
URL
Error
Error: Missing four byte sig
Stacktrace
Error: Missing four byte sig
at https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:16511
at Array.map (<anonymous>)
at https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:16398
at Array.map (<anonymous>)
at https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:15838
at Object._i [as useMemo] (https://app.uniswap.org/static/js/3.10dd3680.chunk.js:2:3038095)
at t.useMemo (https://app.uniswap.org/static/js/3.10dd3680.chunk.js:2:2942127)
at ae (https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:15561)
at re (https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:17548)
at Pt (https://app.uniswap.org/static/js/10.5b6f2871.chunk.js:1:52679)
Device data
{
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "100.0.4896.127",
"major": "100"
},
"engine": {
"name": "Blink",
"version": "100.0.4896.127"
},
"os": {
"name": "Windows",
"version": "10"
},
"device": {},
"cpu": {
"architecture": "amd64"
}
}
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 by reproducing the crash at the provided Uniswap swap and vote URL using the reported Chrome and Windows environment, then inspect the source corresponding to the minified stack trace. The issue does not identify a source file or test; done means the vote page no longer crashes with “Missing four byte sig” and a regression check covers the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100