You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just trying to run a transaction against my bot using npm run tx, but there was a cryptic error being thrown (ERROR: TypeError: Cannot read properties of null (reading 'blockNumber')). this was due to the fact that the transaction was on Polygon, but by default the CLI points to Ethereum mainnet. since the transaction hash didn't exist on Eth mainnet, it would throw the error. it took me some time to figure out that I needed to change my jsonRpcUrl config to point to Polygon. would have been nice if the CLI pointed this out for me by looking at the chainIds declared in package.json and warning me if there is a mismatch with the network of jsonRpcUrl. another improvement would be to check whether the fetched transaction receipt is null before using it in runHandlersOnTransaction
The text was updated successfully, but these errors were encountered:
I was just trying to run a transaction against my bot using
npm run tx
, but there was a cryptic error being thrown (ERROR: TypeError: Cannot read properties of null (reading 'blockNumber')
). this was due to the fact that the transaction was on Polygon, but by default the CLI points to Ethereum mainnet. since the transaction hash didn't exist on Eth mainnet, it would throw the error. it took me some time to figure out that I needed to change myjsonRpcUrl
config to point to Polygon. would have been nice if the CLI pointed this out for me by looking at thechainIds
declared in package.json and warning me if there is a mismatch with the network ofjsonRpcUrl
. another improvement would be to check whether the fetched transaction receipt is null before using it inrunHandlersOnTransaction
The text was updated successfully, but these errors were encountered: