Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

web3.currentProvider.sendAsync is undefined #1119

Closed

Description

@lightninglu10

Hey guys, getting a weird bug here.

I'm setting up my web3 like this

var web3 = new Web3(new Web3.providers.HttpProvider(BLOCKCHAIN_ADDR));

But I'm getting an error with web3.currentProvider.sendAsync is undefined, but web3.currentProvider.send is defined. Anyone know what's up?

Activity

  1. dkchv commented on Oct 17, 2017

    @dkchv

    try to add before create new instance:
    Web3.providers.HttpProvider.prototype.sendAsync = Web3.providers.HttpProvider.prototype.send

  2. frozeman commented on Oct 19, 2017

    @frozeman
    Contributor

    @dkchv thanks, could you tell me where you get this? which version of web3.js?

  3. dkchv commented on Oct 20, 2017

    @dkchv

    I tried to use web3 v1, but out app also use truffle-contract, which use web3 0.20. So then I setProvider to web3 v1, I also set this provider to truffle-contract. And finally truflle-contract tried to invoke sendAsync throw web3 0.20 interface.
    Line above fix this difference for httpProvider bettween v1 and v0.20.

  4. pfrank8 commented on Feb 2, 2018

    @pfrank8

    Hey folks, another potential fix for this could be to make sure you import Web3 before you import any artifacts -- even if you define networks later.

  5. Alexintosh commented on May 18, 2018

    @Alexintosh

    I have the same issue, strangely, this happen only on specific iphone models.
    The workaround doesn't seem to work.

    "web3": "^0.20.6",
    "web3-provider-engine": "13.6.0"
    
  6. Alexintosh commented on May 31, 2018

    @Alexintosh

    This issue should probably be reopened

  7. devzl commented on Jun 4, 2018

    @devzl

    web3.providers.HttpProvider.prototype.sendAsync = web3.providers.HttpProvider.prototype.send; fixes it for me, I think it's because truffle-contract uses the 0.2x version of web3 while I'm using the v1.0.0

  8. Alexintosh commented on Jun 4, 2018

    @Alexintosh

    @devzl it doesn't work client side with Infura nodes. Particularly with American iPhones.

  9. Alexintosh commented on Jun 21, 2018

    @Alexintosh

    Following my previous comment. I couldn't find any way to solve this client side, so I ended up only signing the transaction in the mobile client and broadcasting it server side. If you are interested in a microservice to do that you can find the Tx-broadcaster Repository by DEXlab.io here.

  10. self-assigned this
    on Aug 9, 2018
  11. Alexintosh commented on Aug 9, 2018

    @Alexintosh

    Not sure why this has been closed ¯_(ツ)_/¯

  12. nivida commented on Aug 9, 2018

    @nivida
    Contributor

    Oops sorry.. 🙈

  13. reopened this on Aug 9, 2018
  14. added a commit that references this issue on Sep 24, 2018
  15. jsliu27 commented on Nov 23, 2018

    @jsliu27

    Hey guys, getting a weird bug here.

    I'm setting up my web3 like this

    var web3 = new Web3(new Web3.providers.HttpProvider(BLOCKCHAIN_ADDR));

    But I'm getting an error with web3.currentProvider.sendAsync is undefined, but web3.currentProvider.send is defined. Anyone know what's up?

    您好,我想知道如何创建自己的web3,来实现链上支付,如果您知道,还请您多多帮助一下

  16. nivida commented on Mar 25, 2019

    @nivida
    Contributor

    Version 0.20.x got his last maintenance release with v0.20.7. Please update your code to the latest 1.0 version of Web3.js. Further details about the current project state are explained in the release announcement of version 1.0.0-beta.38.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions