You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the createAsset transaction, if default values for addDecimals (set to 0) and addDefaultFrozen (set to false) are used and these functions are chained, the transaction fails.
Currently, I’ve managed this at the API level by ensuring addDecimals and addDefaultFrozen are not mandatory to chain in the function call. However, this can be confusing during debugging, even if the developer provides correct default values.
Would it be possible to handle this at the individual function level to avoid such issues?
The text was updated successfully, but these errors were encountered:
In the createAsset transaction, if default values for addDecimals (set to 0) and addDefaultFrozen (set to false) are used and these functions are chained, the transaction fails.
Currently, I’ve managed this at the API level by ensuring addDecimals and addDefaultFrozen are not mandatory to chain in the function call. However, this can be confusing during debugging, even if the developer provides correct default values.
Would it be possible to handle this at the individual function level to avoid such issues?
The text was updated successfully, but these errors were encountered: