Safe-react: Transaction never shows up in transaction list

[tschubotz]

• Create new Safe on Rinkeby (2/2)
• Send 0.3 ETH to Safe
• Create tx for 0.1 DATAcoin to Safe itself, sign with Metamask
• Create tx for 0.001 ETH to Safe itself, sign with Metamask
  -> None of both txs show up in the tx list.

Env:

• https://rinkeby.gnosis-safe.io
• Brave browser (Owner 2 is on Firefox, there they also dont show up.
• Metamask
• Safe addresss: 0x764F23f66227eBE27d2F4A9A6aA2fa6bdE8811c1

[germartinez]

They are shown in the tx list, but not right after the "Transaction pending: More confirmations required to execute" notification. Following the document where we have listed all the notifications, this notification is shown when "m-oo-n transaction is submitted" (not executed). You have to wait the MM notification and check the tx list again.

There isn't a notification for executed m-oo-n transactions without all the confirmations, only when they have all the confirmations the app would show "Transaction pending" and "Transaction confirmed on the blockchain"

No need to refresh the tx-list page. Should be updated automatically.

If it's not working, can you share the console?
Thanks!

[tschubotz]

This is my console output:

[tschubotz]

It didn't run out of gas though. This is the chain tx: https://rinkeby.etherscan.io/tx/0x151386613ba0373875ab4a461c670e826d752f6031b37595b7db338525cd6392

[tschubotz]

Seems like this is only reproducible if I send an "imposible tx" (failing?) before:

- Create Safe
- Send 0.3 ETH to Safe
- Send 0.001ETH
- Submit tx with Metamask
-> Does show up in tx list
- Add DATAcoin (balance 0)
- Send Datacoin (0.123) <--- "Impossible tx"
- Submit tx with Metamask
-> Doesn’t show up in tx list
- Send 0.001ETH
- Submit tx with Metamask
-> Doesn't show up in tx list

[mikheevm]

@tschubotz The reason for this bug is that we can't read data from DATACoin contract at rinkeby. I don't know why. Thus why we can't decode a transaction data and it doesn't show up. How do we want to handle it @lukasschor ? Should we just show something like "Unknown transaction" in case something like this happens?
@Uxio0 @germartinez do you know why it's not possible to read the data? Does it make sense to remove this token maybe?

[lukasschor]

@tschubotz The reason for this bug is that we can't read data from DATACoin contract at rinkeby. I don't know why. Thus why we can't decode a transaction data and it doesn't show up. How do we want to handle it @lukasschor ? Should we just show something like "Unknown transaction" in case something like this happens?
@Uxio0 @germartinez do you know why it's not possible to read the data? Does it make sense to remove this token maybe?

If we can't decode a transaction I would just show it as a "Custom Transaction".

[Uxio0]

@mikheevm I think we have the wrong contract for DATACoin. It's 0x0Cf0Ee63788A0849fE5297F3407f701E122cC023 but it should be 0x9048cDeD33a26F288EA047cD53b81c459Deda184. I will modify it in the relay service (rinkeby)

[mikheevm]

@tschubotz @lukasschor this should be fixed after an update in the relay service on rinkeby. Could you . please test it?