[Bug]: Unable to "Send" an NFT from the item page

[javiergarciavera]

Describe the bug

When I tried to send an NFT, after specifying the amount to send (only had 1, so set to 1), the continue button didn't get enabled, so I couldn't finish the send flow. See the recording

Expected behavior

User is able to send the NFT just specifying the destination address and the amount

Screenshots/Recordings

https://www.loom.com/share/b555a44dbcab4abdb587ed650c0c718d

Steps to reproduce

1. Go to NFT tab
2. Click on an NFT item
3. Click on send
4. Specify the destination address
5. Specify the amount of NFT to be sent
   Expected:
6. Continue button is enabled
   Current:
7. Continue button is not enabled

Error messages or log output

Detection stage

During release testing

Version

12.10.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

It is an important flow within the assets

[Unik0rnMaggie]

Send failing only for this specific NFT QA MM TEST

Send.QAMM.NFT.mov

[seaona]

Where did you get this NFT from? I see it has a very short contract bytecode, which seems to indicate it's not complying with a token standard, possibly missing functions / incorrect implementation 🤔

0x363d3d373d3d3d363d7375a2b4fd1c386ffe4eeb6b4ff3b5aa07ed77473e5af43d82803e903d91602b57fd5bf3

I would expect this to also fail in prod. Do you know if is this the case @javiergarciavera ?

[javiergarciavera]

@seaona it is a token I created, the best way to test it is minting it
https://phosphor.xyz/javiergv87/c/qa_mm_test/3abbd6cb-0ac4-4ffc-8f89-c4cbb354b97a
I think there is an issue in the contract, hence the failure when minting, but the validation amount specified in the ticket I think is unrelated to the contract.

[seaona]

thanks! Do you have the code? From your link I see it says it's non-transferrable, so possibly that's the reason why it cannot be sent.
It seems like an old issue -- we currently don't handle very well the UX for soulbond / non-transferrable tokens (or other deviations from standards) see this other issue here. Possibly we should display some info in the UI indicating it's non-transferrable and block the Send flow.

I think we should add the prod label instead of being an RC regression. Does it make sense @javiergarciavera ?

[danjm]

@javiergarciavera can you confirm whether or not this bug is reproducible on v12.9.3?