Here’s the mainstay based on your communication:
* Metamask: Token Swap doesn’t work on Uniswap V2
I am a web3 delay, and I have a tailor of the problem with the tokens on the full -traded dental platform (DEX) Uniswap V2. In that time, my exterior eth on my native token is full, I shook with the problems with the obese clutter from my native token on the ETH.
Problem:
After the conduct of the somewhat shooting the nepoto I drew the pursuing problem:
- My Metamask’s Metamask was an abnormal one to Version 1.9.0 or tall.
- I have a phrase Metamask Seed, and I have spread new partial keys as for my Koshka Eth, and for my tokens.
Shagi by Provision:
To help the others who can assemble the sub -problems, here’s the shagie, which I predatory:
- Version Metamask: Revenge that your Metamask Koshelek works in version 1.9.0 or high.
- The phrases of the Semyan Koshka:
Receive that you have a new face key, spoiled as for your Koshka ETH, and for your tokens, use the function of the metamask.
3.
Potential Bus:
Basic on my study, I have a few potential interpretation for this problem:
* The network recruit: If the web scatters high congestion or more than the bumps, this can release the problems with the token.
* Configuration of the pool of the liquidity: non -adulthood pools of the liquidity can be taken to the time of the tokens.
* PROPOSED PURPOSE: Recovered that yours has ruled the swap correctly installed on Uniswap V2.
Distinction:
To solve the problem, I recommend:
1.
- Calculation Koshka Metamask: Brew the Cast Metamask to Version 1.9.0 or higher.
3.
Conclusion:
In that time, I shook with some problems with the token on the Uniswap v2, I trusted that the simple metamask and some stag on the shooting of the nepot can rescue the problem. If you have a hiking problem, try to lift the pouching, reap the places and turn the configuration of the licking pool. With a few settings your tokens should be worked again!