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

ETH Receipt errors in 1.0.0-beta.38 #2252

Closed
poserr opened this issue Jan 28, 2019 · 3 comments
Closed

ETH Receipt errors in 1.0.0-beta.38 #2252

poserr opened this issue Jan 28, 2019 · 3 comments

Comments

@poserr
Copy link

poserr commented Jan 28, 2019

I am (was) using this code to send signed transactions to external node and get the receipt:

                                return this.web3.eth
                                .sendSignedTransaction(rawSigned)
                                .once('transactionHash', console.log)
                                .once('receipt', console.log)
                                .on('error', err => {
                                    reject(err);
                                });

After updating to 1.0.0-beta.38 I started to get this error:

web3-core-helpers.umd.js:88 Uncaught (in promise) TypeError: Cannot read property 'blockNumber' of null
    at Object.outputTransactionFormatter (web3-core-helpers.umd.js:88)
    at GetTransactionReceiptMethod.afterExecution (web3-core-method.umd.js:491)
    at GetTransactionReceiptMethod._callee$ (web3-core-method.umd.js:449)
    at tryCatch (runtime.js:62)
    at Generator.invoke [as _invoke] (runtime.js:288)
    at Generator.prototype.(:8080/anonymous function) [as next] (webpack-internal:///./node_modules/@babel/runtime/node_modules/regenerator-runtime/runtime.js:114:21)
    at asyncGeneratorStep (asyncToGenerator.js:3)
    at _next (asyncToGenerator.js:25)

somehow outputTransactionFormatter is being called immediately after transactionHash event with empty "receipt" object.

@poserr
Copy link
Author

poserr commented Jan 28, 2019

I have to add that transaction itself is created and pushed to ropsten network successfully.

transactionHash event is also immediately fired.

@poserr
Copy link
Author

poserr commented Jan 28, 2019

It looks similar to #2246 and I am using WebSocket provider.

The error is thrown immediately after sendSignedTransaction method call, right after transactionHash event

@nivida
Copy link
Contributor

nivida commented Jan 28, 2019

got already fixed in PR: #2248 I will prepare a release now and publish it.

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