-
Notifications
You must be signed in to change notification settings - Fork 33
TypeError: Cannot read property 'toNumber' of null when click "Scan" to send transaction from Parity Signer account #361
Comments
I also had this issue, don't think it's related to the webcam. I think it's related to gas/gasPrice somehow not being defined in the values submitted by TxForm. |
Agreed. I was just able to replicate the same issue multiple times just by completing the TxForm page too quickly. i.e. pasting a recipient, entering a value, and pressing the "Scan" button as soon as the scan button appeared |
I've discovered that it's caused when it lets you click "Send" when in the "Transaction Details" section still says "Missing input fields...". |
It appears to be Parity Signer-specific, it seems that when you click "Scan" it tries to go to the paritytech/fether/packages/fether-react/src/Send/TxQrCode/TxQrCode.js, where it calls |
I investigated as well and this is what I got:
This can be reproduced by changing the line with: newGasEstimate = await estimateGas(
allValues,
token,
parityStore.api
).then(x =>
new Promise((resolve,reject) => {
setTimeout(() => {resolve(x)}, 15000);
})
); This only triggers an error for Parity Signer accounts, but for node accounts it means that the gas isn't sent with the transaction, which isn't intended either. |
…gas-calculated fix: Fixes #361. Restrict user from clicking "Scan" to process tx before gas is calculated
I just tried using the latest 'master' branch with
yarn; yarn start
to send a transaction with some ETH from a Parity Signer account that I had imported. When I clicked the "Scan" button it displayed the following error message.And when I restarted Fether I then did the same steps (but ran
yarn; yarn build; yarn start
), when I clicked the "Scan" button it worked and opened the QR page without the error.EDIT:
Regarding the padding around the Electron frame, I think I must have accidentally changed the zoom level of the Electron app, so I just fixed it by going to View > Actual
The text was updated successfully, but these errors were encountered: