Metamask-extension: Can't send transaction in MetaMask 4.5 extension

[ghost]

Since earlier today (I assume since the MM extension got updated), I get a spinning wheel of death when sending transactions through MetaMask on a regular basis.

Expected behaviour

The following transaction is expected to succeed:

Actual behaviour

After pressing the "submit" button, the popup keeps showing the following spinner:

Additionally, Ganache logs show no transaction being committed:

* Actions performed to try to mitigate the issue*

• Switch back and forth between networks
• Reset MM accounts
• Disable and enable MM extension
• Restart Ganache
• Redeploy contracts

Browser version: 65.0.3325.181
MetaMask version: 4.5.0
Operating system: macOS 10.13.3

MetaMask console log

[davewc]

same here. I'm also now seeing:

Failure: error replacement transaction underpriced

[floresmark444]

The same issue here. I can't send anything When do you think the issue will be fixed?

[rhlsthrm]

I'm having the same issues which are really messing up my development.

[jupitermandy]

Same issue, just follow the TutorialToken example to do some transactions, and the MetaMask is spinning and never stop.
I have changed the Ganache setting with different port and networkId, and it still doesn't work.

A new update:
I have uninstalled and reinstalled MetaMask, it works.

[dmill]

Thanks @jupitermandy! Confirmed for me too - I was getting this behavior last night, but after reinstalling things are back in working order. 4.5.1 must've fixed it, so a big thanks to whoever on the team put that patch in with such a quick turnaround.

[Pedro-vk]

I've version 4.5.1, I've removed it and installed again, but the issue is still here.

[ghost]

Upgrading didn't help for me. I've had to manually install 4.3 to be able to keep things working.

[rhlsthrm]

@mananz how do you install an older version?

[kumavis]

@rhlsthrm https://github.com/MetaMask/metamask-extension/releases unzip and drag into the extensions page (chrome)

[kumavis]

v4.5.2 resolves an issues with our validation of chainId on txParams submitted by some apps (mycrypto, mew, ...)

[kumavis]

@danjm old-ui not showing an error here is a problem. I think we can slightly de-escalate the priority now that v4.5.2 is live

[danfinlay]

Closing in favor of #3881