While creating ASA in algorand using stdlib.launchToken(), opts.metaDataHash value is ignored and not set in the asset.

[KodisBabu]

Describe the error

While creating ASA in algorand using stdlib.launchToken(), opts.metaDataHash value is ignored and not set in the asset.

opts.metaDataHash value is not set while creating the asset in algorand network

To Reproduce
const nft = await stdlib.launchToken(accLender, "Gold Pass", "GP",{metadataHash: "12345678901234567890123456789012",url:"ipfs://xss.zzz",clawback:accLender.getAddress(),decimals:0,defaultFrozen:false,freeze:accLender.getAddress(),note:JsonToArray(metaData),reserve:accLender.getAddress(),supply:1});

Expected behavior

metaDataHash value should have been set

Extra information

What version of Reach are you using? You can run reach version or reach hashes to find out.

[jeapostrophe]

First, the key is metadataHash, not metaDataHash. How can you tell that it is not being set? That is, what do you check afterwards?

[KodisBabu]

Actually, i am passing metadataHash as key and it is not set, when i check in algoexplorer.

…

-Kodis

On Mon, Sep 26, 2022 at 6:57 PM Jay McCarthy ***@***.***> wrote: First, the key is metadataHash, not metaDataHash. How can you tell that it is not being set? That is, what do you check afterwards? — Reply to this email directly, view it on GitHub <#1439 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXX77FAAROF6XUTX7H7743TWAGQDTANCNFSM6AAAAAAQVABMDU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jeapostrophe]

Ok. Thank you. I'll schedule someone to debug and get a stable test case for this

[jeapostrophe]

Hi @KodisBabu , as #1487 demonstrates, this has always worked if you look at the right field names