Get error when try to add contract to other contract call

TypeScript SDK
1

I updated SwayLend market contract to latest versions and also to beta 4. I have function on frontend that check MaxBorrowAmount from contract state, on previous beta3 I was using this code to be able to get value

 updateMaxBorrowAmount = async (marketContract: MarketAbi) => {
    const { addressInput } = this.rootStore.accountStore;
    if (addressInput == null) return;
    const { priceOracle } = this.rootStore.settingsStore.currentVersionConfig;
    const oracle = new Contract(
      priceOracle,
      OracleAbi__factory.abi,
      this.rootStore.accountStore.provider
    );
    const { value } = await marketContract.functions
      .available_to_borrow(addressInput)
      .txParams({ gasLimit: (1e8).toString() })
      .addContracts([oracle])
      .simulate();
    this.setMaxBorrowBaseTokenAmount(new BN(value.toString()));
  };

Contract abis are here: https://github.com/compolabs/sway-lend/tree/master/frontend/src/contracts

But after update it started to fail with next error:

image
image818Ă—432 103 KB

Did way how to connect other contract change?

1 Like
2

There’s something failing on the transaction simulation since “decodeCallResult” is throwing an error.

However, the error wrapper is falling to catch an undefined value in the Transaction result. This might be an issue beyond your specific case. I’ll escalate this.

Meanwhile, I recommend you to set “txParams.gasLimit” as a number rather than an string. I don’t see anything else that might be wrong with your transaction simulation.

1 Like
3

@sway There seems to be a bug in our revert reason-parsing logic for the simulate function. I’ll file an issue for this.

Instead of simulate-ing, if you call this transaction - do you see a revert reason?

4

Please also make sure that you specified/initialized the storageSlots when you deployed your contract. I was facing a similar issue this morning and it was fixed once I deployed the contract with storageSlots specified

1 Like
5

Thanks for the suggestion but in my contract I have everywhere catches that would prevent failing if the variable is not initialized, like below.

let balance = storage.user_collateral.get((account, asset_config.asset_id)).try_read().unwrap_or(0);

Also would like to notify you that the Rust tests are passing successfully for this contract, we just have some problems with typescript SDK due to updates

But it’s really interesting to hear about how to initialize storage slots, probably it will make my contract cleaner, please have a look at new topic here

1 Like
6

Changed into number and also tried to make call, it still fails

image
image970Ă—1130 198 KB

1 Like
7

Hi there!
I’ll scalate this issue.

8

Follow-up issue:

1 Like
9

An issue for the “out of gas” error was opened as well.

10

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.