Sign up to join our community!
Please login to your account!
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Hey guys!! I have a contract A calling a method of contract B that takes 1 argument and a token as inputs. When contract B is in the same shard as contract A, everything works fine, the transaction looks like: `ESDTTransfer@TOKEN-abcdef@1000000@method_contract_b@argument_contract_b` However, when contract B is not in the same shard as contract A, an additional unexpected argument appears at the end of the tx, which makes it fail as the method of contract B expects only 1 argument: `ESDTTransfer@TOKEN-abcdef@1000000@method_contract_b@argument_contract_b@unexpected_argument` Do you know why this unexpected argument is added to the tx?
Do you have some transactions you can link?
Are you using the latest version? I used to have a similar issue but it got solved using the latest version
Hey Dorin! Thanks for your answer ???? I am off right now but I will send some samples of txs next week if I keep struggling with this.
Hi @iancudorinmarian ! Here is an example of transaction on testnet where contract A (on shard 1) has a method callRemoteContract which calls a method methodContract of contract B (on shard 0) that takes no argument and no payment. Furthermore there is no callback in this async call. Although the call is successful, I don’t understand the presence of “453468” at the end of the transaction methodContract@453468