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

Cant send transations since "warning" appeared, yesterday #3376

Closed
Icebergx opened this issue Mar 1, 2018 · 1 comment
Closed

Cant send transations since "warning" appeared, yesterday #3376

Icebergx opened this issue Mar 1, 2018 · 1 comment

Comments

@Icebergx
Copy link

Icebergx commented Mar 1, 2018

Hi,

Yesterday, I mistakenly sent Eth to an old contract address. Luckily this was rejected, and I then managed to send Eth to the correct Eth address straight after. In the MM window, a "warning" message appeared, but I didn't think anything of it, and all my Eth was still in my wallet, as expected.

Today, I tried to send Eth to an ICO twice, with 40gwei, and neither transation went through. In fact, neither transaction is even visible on Etherscan. In my MM widow, they too have "warning" next to them too!
(Please see screenshot)
screen shot 2018-03-01 at 14 27 09

To send the Eth to the ICO, I had to log-in to MEW with my private key... Not ideal.

I tried to log out of MM and restarted my computer and just logged back in. The three "warning" transactions (one from yesterday and two from today) are still there, and when I try to log into IDEX, IDEX says that MetaMask isn't installed.
screen shot 2018-03-01 at 14 55 51

Browser:Chrome
OS: Mac OSX 10.10

Any help would be appreciated.

Rak.

@danfinlay
Copy link
Contributor

Closing as duplicate of #3357. Idex should fix this on their end, but we'll also try to fix it on ours.

github-merge-queue bot pushed a commit that referenced this issue Oct 29, 2024
…7895)

## **Description**

Remove any usage of the global network from transaction simulation.

This requires using the `chainId` from the `TransactionMeta`, and so the
`SimulationDetails` properties have been simplified to accept
`TransactionMeta` directly to minimise the number of tightly coupled
properties.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/27895?quickstart=1)

## **Related issues**

Fixes:
[#3376](MetaMask/MetaMask-planning#3376)

## **Manual testing steps**

Regression of all simulation usages, with specific attention to fiat
value.

- Legacy Confirmations
- Redesigned Confirmations
- Smart Transaction Status

## **Screenshots/Recordings**

### **Before**

### **After**

## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants