We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
You cannot opt into an asset using asset transfer transaction.
Should be able to opt into an asset with asset transfer transaction.
Error: RUNTIME_ERR1404: Account ENBABX5NX4CCBETS2MJWYFIGTXA6TVTML7FBDLNR4NIPMYEKT2VHM7JWEQ doesn't hold asset index 1
from this line https://github.com/scale-it/algo-builder/blob/master/packages/runtime/src/ctx.ts#L277
You should catch the error thrown and check for this https://github.com/scale-it/algo-builder/blob/master/packages/runtime/src/ctx.ts#L281 and then only throw the error if you are not opting into asset.
Create runtime asset transfer transaction with 0 amount and same sender and asset receiver.
The text was updated successfully, but these errors were encountered:
@gidonkatten thanks for spotting. It is a bug.
Sorry, something went wrong.
fixed in v1.1.1
v1.1.1
ratik21
No branches or pull requests
Describe the bug
You cannot opt into an asset using asset transfer transaction.
Expected Behavior
Should be able to opt into an asset with asset transfer transaction.
Current Behavior
Error: RUNTIME_ERR1404: Account ENBABX5NX4CCBETS2MJWYFIGTXA6TVTML7FBDLNR4NIPMYEKT2VHM7JWEQ doesn't hold asset index 1
from this line https://github.com/scale-it/algo-builder/blob/master/packages/runtime/src/ctx.ts#L277
Possible Solution
You should catch the error thrown and check for this https://github.com/scale-it/algo-builder/blob/master/packages/runtime/src/ctx.ts#L281 and then only throw the error if you are not opting into asset.
Steps to Reproduce
Create runtime asset transfer transaction with 0 amount and same sender and asset receiver.
The text was updated successfully, but these errors were encountered: