Crash report: `Error: Invalid token address: 0xc5102fE9359FD9a28f877a67E36B0F050d81a3cc`
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
https://app.uniswap.org/#/swap?chain=mainnet
swap state
{
"INPUT": {
"currencyId": "ETH"
},
"OUTPUT": {
"currencyId": null
},
"independentField": "INPUT",
"typedValue": "",
"recipient": null
}
Error
Error: Invalid token address: 0xc5102fE9359FD9a28f877a67E36B0F050d81a3cc
Stacktrace
Error: Invalid token address: 0xc5102fE9359FD9a28f877a67E36B0F050d81a3cc
at e.get (https://app.uniswap.org/static/js/main.2ce6a487.chunk.js:1:507323)
at https://app.uniswap.org/static/js/main.2ce6a487.chunk.js:1:670613
at Object.Ta [as useMemo] (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2759031)
at t.useMemo (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2668610)
at S (https://app.uniswap.org/static/js/main.2ce6a487.chunk.js:1:670321)
at Oe (https://app.uniswap.org/static/js/main.2ce6a487.chunk.js:1:633351)
at fa (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2754298)
at za (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2763865)
at Yf (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2807589)
at Cs (https://app.uniswap.org/static/js/2.bf7b8f1d.chunk.js:2:2793839)
Device data
{
"ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "102.0.5005.61",
"major": "102"
},
"engine": {
"name": "Blink",
"version": "102.0.5005.61"
},
"os": {
"name": "Mac OS",
"version": "10.15.7"
},
"device": {},
"cpu": {}
}
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
Reproduce the crash at the provided Uniswap swap URL using the recorded swap state, then trace the invalid token address from the minified main.2ce6a487.chunk.js stack trace into the source. Done means the swap page no longer crashes for this state and the invalid address is handled appropriately.
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