txSummary not returning contract call operation in some cases

[LuizAsFight]

What version of fuels-ts are you using?

0.88.1

Steps to Reproduce

• use the latest fuel-wallet
• access connectors demo and connect your wallet
• click on increment button
• you will see this screen

More details

The screen above tries to show the operations of the transaction for the user to check and confirm it. It's currently showing no operations.

Behind the scenes it's consuming getTransactionSummary.
When this method tries to compute the contract call operations, it tries to identify who called the contract using the assetId returned from the receipt.

The problem is that the receipt returns 0x0000..., as there was no assetId in the contract call made. The previous code was working only because the baseAssetId was the same, and the input would have the correct assetId.

Solution

When the receipt returns assetId: 0x0000..., consider getting the input that has the current baseAssetId, meaning that who payed the fee will be identified as the contract caller.

fuel-core FuelLabs/fuel-core#1941

I think this is something that could be changed in the VM, it could return null instead of 0x0000..., but it doesn't change the solution above

[maschad]

I think the more permanent fix for this should involve fuel-core determining what the correct response is based on FuelLabs/fuel-core#1941

In the interim we have released a patch which solves this.

[LuizAsFight]

@maschad
makes sense to close this issue? the bug in this issue is fixed.

the change on VM may or may not happen haha, can it be tracked in another issue as an improvement instead of a bug ?

cc @arboleya

[maschad]

I agree @LuizAsFight this particular issue closed since both

• Fix transaction summary with contract calls #2530
• CallReceipt is returning wrong from property #2449

have been created to address this on our end going forward, if FuelLabs/fuel-core#1941 gets integrated on fuel-core then we can create another issue to make accommodations for that.