Metamask web3 instance's contract deploy callback function not fired twice

[tina1998612]

From the official doc of web3js API about contract deploy, the callback function of MyContract.new should be fired twice(one for the transaction hash and the other for the contract address after it is deployed).
However, using the metamask's web3 instance, this callback function seems to be fired only once. Namely, the contract address is not printed even after the contract is mined, and I can only view the contract address within the metamask extension itself.
The problem is, if not having the original callback function settings(the one that is fired twice), how can I get the contract address efficiently after the contract is mined? (without using setTimeout)
I'm trying to write a client-slide contract deploy utility script which will return the contract address once deployed with metamask. Is it possible with the current metamask web3 library? Or this issue is not related to the library?

Any help will be much appreciated!

[KPull]

I've noticed this issue as well and it is a genuine problem. I believe by polling using getTransactionReceipt, it should be able to determine whether the contract has been deployed (and where).

However, remember that DApps will not be able to tell whether web3 is injected by MetaMask or not. Having a hack such as the one described above, that is specifically for MetaMask, is undesirable.

[skozin]

I believe that this issue prevents truffle-contract from working properly with MetaMask: it doesn't resolve promises of successfully deployed contracts. The issue is only present when web3 is pointed to MetaMask's provider.

Here is the code of truffle-contract's callback function:

var intermediary = function(err, web3_instance) {
  if (err != null) {
    reject(err);
    return;
  }

  if (err == null && web3_instance != null && web3_instance.address != null) {
    accept(new self(web3_instance));
  }
};

As you can see, it checks web3_instance.address (which is not set on the first call) and ignores the call if it's not set, so the promise ends up never being resolved.

[yarrumretep]

+1 on this issue

[domharrington]

I had to fallback to using web3 directly to create contracts https://github.com/trufflesuite/truffle-contract/issues/70#issuecomment-355376332

[faeezshaikh]

Any updates on this issue? Still observing in ver 3.14.1

[derekchiang]

To restate the significance of this issue: the second callback provides an instance of the contract that has its methods mapped to contract functions. Without it, it's impossible to actually call any functions on the contract, rendering the deployed contract useless.

[derekchiang]

In case it helps: the same issue occurs in both Chrome and Firefox.

[derekchiang]

The same issue occurs on both Rinkeby and Ganache (local).

[domharrington]

@derekchiang the workaround here works, and you can get the contract instance: https://github.com/trufflesuite/truffle-contract/issues/70#issuecomment-355376332

[bdresser]

Hey folks, closing this issue due to inactivity, please let me know if you're still having trouble.