Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No conversion rate for ETH #6421

Closed
bdresser opened this issue Apr 8, 2019 · 5 comments · Fixed by #6444
Closed

No conversion rate for ETH #6421

bdresser opened this issue Apr 8, 2019 · 5 comments · Fixed by #6444
Labels

Comments

@bdresser
Copy link
Contributor

bdresser commented Apr 8, 2019

Seeing intermittent issues with missing ETH conversion rates.

No background or UI console errors. Response from Infura's ETH conversion endpoint returns accurately.

MM v6.3.1

@bdresser
Copy link
Contributor Author

bdresser commented May 6, 2019

@omnat is still seeing this on 6.4.1

ETH is set to primary

looks like the request to Infura is failing

image

@scotthelmreich
Copy link

Hi,
I was just trying to send some ETH with Metamask and it is stuck in a loading screen:
image
I am thinking it might be similar to above, but I have already input the gas price, which was a "Average/Normal" speed. It has been loading (searching for gas?) now for about 20 minutes. I have restarted my browser, restarted my computer-- which caused me to have to log back into Metamask, and after log-in it went straight back to the loading screen. Do you have any advice? I don't mind paying a little extra gas to get this transaction pushed through.
Best Regards,
Scott

@scotthelmreich
Copy link

I've got it figured out, please disregard.
-Scott

@KaiserTom
Copy link

A bit of a necro of this issue but I had much similar issues which were instantly resolved by switching to a testnet and then back to the mainnet in the Metamask window.

Restarting the browser didn't work which was odd. Maybe a PC restart would have rectified it but I didn't test that.

@tmashuang
Copy link
Contributor

Archiving issue. If the issue has persisted for anyone else please open a new issue with screenshot as the one above and network logs if possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants