Closed prury closed 5 months ago
What is the http status from the reuquest?
Cc @kodadot/internal-dev pls
wfm
I tested again and it still works.
wfm
it is not always tho, intermittent bug
Should we put an error message on toast? So we can capture the error message. Does $i18n.t('drops.mintPerAddress')
not seem relevant anymore? https://github.com/kodadot/nft-gallery/blob/79523adb69d370dd857e226e36e7423e623db46b/components/collection/drop/PaidGenerative.vue#L393
not seem relevant anymore
not relevant the error could come from any one of
allocateClaim
fetchDropStatus
fetchNft
See that readme was left unread 😌
@vikiival @preschian
409 mint already claimed
request:
{
"sn":61,
"txHash":"0xf12d93137091ceefb3b915ad0d023856c9497e2ae70b28051743cd99e6b25c24",
"address":"DBVPJeM91LawsF8dqphFYmdPwtxfpXqbgBtVaxn41CT3Amn"
}
409 mint already claimed
So it means that reqest to assign metadata for particular NFT has been already sent. Sending it again would result into overwriting the metadata.
Oh, maybe there is some glitch on the UI that calls the endpoint multiple times? On allocate claim, we already filter sn with claimed === 0
Oh, maybe there is some glitch on the UI that calls the endpoint multiple times?
Highly possible :)
https://github.com/kodadot/nft-gallery/assets/36627808/d82f3e7b-4ba4-428a-b256-c966a7204ab4