Contract field is undefined after Blueprint is deployed

[gregzaitsev]

This code from this tutorial used to work, but now result.contract is undefined:

    const unsub = await blueprint.tx
    .new(endowment, gasLimit, initValue)
    .signAndSend(alice, (result) => {
      if (result.status.isInBlock || result.status.isFinalized) {

        console.log("Contract deployed: ", result.contract); // <--- Prints undefined

        unsub();
        resolve(result);
      }
    });    

[jacogr]

Ummmm.... there has been no changes, so indeed should still be the same.

The only place it should not be included s if it doesn't pickup the event. Will test against a recent Substrate master.

[gregzaitsev]

I am using the API 3.6.4, but noticed that UI has newer API (3.6.5-6), and the UI contracts work.

[jacogr]

There really has been no changes in that layer :) All the stuff in the current betas have mostly revolved around parachains.

Ys, the UI uses the same api-contracts interface, so it doesn't use anything else or take shortcuts. Will try both though.

[gregzaitsev]

Turned out it was my fault, the deploying account did not have enough balance to pay for endowment.

But the documentation still refers to createContract, which is marked as deprecated. Would you like to leave this issue open to track this update?

[jacogr]

Ok, have not been able to reproduce.

Yes, the docs need an update. Additionally to support this #3112 - the put code & deploy would become one (the API will detect old vs new) and handle appropriately. Obviously once the code is deployed, you can still new the contract as per normal. That will go into the betas this week.

[jacogr]

Closing, replaced by polkadot-js/docs#172

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.