Metamask-extension: transaction history is empty instead of showing two tx

Created on 15 Mar 2017  Â·  11Comments  Â·  Source: MetaMask/metamask-extension

I can't see my tx on 0x2955081796064C70e3f9227752e89862f8967bC8 with metamask 3.4.0 version but these tx are shown in any explorers.
screenshot 2017-03-15_00-13-18

T00-bug

All 11 comments

@NicolasMassart we dont currently import history - this just includes txs sent while metamask is installed

we will add history import in the future

But they were sent while metamask was installed as I created this account with metamask then moved some eth from another account and interracted with ENS using metamask. So both tx should be visible, don't you think ?

did you send the transactions from this installation of metamask or on another computer / reused the key on another device?

@NicolasMassart sorry for all the questions, people create a lot of issues that turn out to not be related to metamask - but this may be a genuine metamask bug

Yes it was created with this metamask install. I have only one.

Le mer. 15 mars 2017 01:34, kumavis notifications@github.com a écrit :

sorry for all the questions, people create a lot of issues that turn out
to not be related to metamask - but this may be a genuine metamask bug

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MetaMask/metamask-plugin/issues/1210#issuecomment-286605338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEdfwJbu7l7buGlaLZ99JCNM0SHjBScJks5rlzIKgaJpZM4MdRnE
.

>

=========================================================== I welcome VSRE

emails. Learn more at http://vsre.info/

Also, note that I switched from live main network to test network and back. So as my address on main net has no tx on testnet, when I came back to main net perhaps this had an impact.

@NicolasMassart could you possibly give me a state dump for the UI?
Instructions on how to do that:
right click on the extension
click Inspect popup in the menu
in the console type logState()
that should spit out the UI state

Here, I'll give you one, Kovan is experiencing the same issues of txs disappearing.
https://kovan.etherscan.io/address/0xbc01b6a30c80d3bee56064d07de02ecdee4e762e
You can see one outgoing tx here, but...

{
  "metamask": {
    "isInitialized": true,
    "isUnlocked": true,
    "rpcTarget": "https://rawtestrpc.metamask.io/",
    "identities": {
      "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e": {
        "address": "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e",
        "name": "Account 1"
      },
      "0x1f330aece2961f534401959019fed850f8e797f0": {
        "address": "0x1f330aece2961f534401959019fed850f8e797f0",
        "name": "Account 2"
      }
    },
    "unapprovedTxs": {},
    "noActiveNotices": true,
    "frequentRpcList": [],
    "addressBook": [],
    "network": "42",
    "accounts": {
      "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e": {
        "code": "0x",
        "nonce": "0x1",
        "balance": "0x37a4e3c42e82c000",
        "address": "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e"
      },
      "0x1f330aece2961f534401959019fed850f8e797f0": {
        "code": "0x",
        "balance": "0xdbbb1c458d4c000",
        "nonce": "0x1",
        "address": "0x1f330aece2961f534401959019fed850f8e797f0"
      }
    },
    "transactions": {},
    "currentBlockNumber": 420907,
    "currentBlockHash": "0x5ee99bc195d383cb9e32eeed20caa33ce26577946cc9d361c8e2fb995a7fe4f5",
    "selectedAddressTxList": [],
    "unapprovedMsgs": {},
    "unapprovedMsgCount": 0,
    "unapprovedPersonalMsgs": {},
    "unapprovedPersonalMsgCount": 0,
    "keyringTypes": [
      "Simple Key Pair",
      "HD Key Tree"
    ],
    "keyrings": [
      {
        "type": "HD Key Tree",
        "accounts": [
          "bc01b6a30c80d3bee56064d07de02ecdee4e762e",
          "1f330aece2961f534401959019fed850f8e797f0"
        ]
      }
    ],
    "selectedAddress": "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e",
    "currentCurrency": "USD",
    "conversionRate": 41.39706851,
    "conversionDate": 1490279401,
    "provider": {
      "type": "kovan"
    },
    "shapeShiftTxList": [],
    "lostAccounts": []
  },
  "appState": {
    "menuOpen": false,
    "currentView": {
      "name": "accountDetail",
      "detailView": null,
      "context": "0xbc01b6a30c80d3bee56064d07de02ecdee4e762e"
    },
    "accountDetail": {
      "subview": "transactions"
    },
    "transForward": true,
    "isLoading": false,
    "warning": null
  },
  "identities": {}
}

@NicolasMassart I am able to reproduce your issue as such:
1) Submit a tx on any network, Network A we'll call it.
2) Switch to any other network, Network B.
3) Submit a tx on Network B.
4) Navigate back to Network A: the transaction is gone.

This behavior happens as soon as you "send" a transaction. There is no need to approve it. This can even be triggered when dapps request a transaction.

There is something with our transaction creation logic that is messing up our transaction histories on other networks.

Yes that's​ it, exactly what i did. Sorry i had no time to investigate and
give you the dump...

Le jeu. 23 mars 2017 15:42, Kevin Serrano notifications@github.com a
écrit :

@NicolasMassart https://github.com/NicolasMassart I am able to
reproduce your issue as such:

  1. Submit a tx on any network, Network A we'll call it.
  2. Switch to any other network, Network B.
  3. Submit a tx on Network B.
  4. Navigate back to Network A: the transaction is gone.

This behavior happens as soon as you "send" a transaction. There is no
need to approve it. This can even be triggered when dapps request a
transaction.

There is something with our transaction creation logic that is messing up
our transaction histories on other networks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MetaMask/metamask-plugin/issues/1210#issuecomment-288740780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEdfwGZIV3dSI9mvoPuT3Rs7SSFc44Y8ks5rooS4gaJpZM4MdRnE
.

>

=========================================================== I welcome VSRE

emails. Learn more at http://vsre.info/

@NicolasMassart got it fixed! Thanks for the help! ^_^

Was this page helpful?
0 / 5 - 0 ratings

Related issues

estebanmino picture estebanmino  Â·  3Comments

MarkOSullivan94 picture MarkOSullivan94  Â·  3Comments

dpazdan picture dpazdan  Â·  3Comments

kumavis picture kumavis  Â·  3Comments

glitch003 picture glitch003  Â·  3Comments