Skip to content
New issue

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

HTS NFTs not supported in Metamask mobile wallet #583

Closed
Ashe-Oro opened this issue Oct 3, 2022 · 2 comments · Fixed by #598
Closed

HTS NFTs not supported in Metamask mobile wallet #583

Ashe-Oro opened this issue Oct 3, 2022 · 2 comments · Fixed by #598
Assignees
Labels
enhancement New feature or request limechain P1
Milestone

Comments

@Ashe-Oro
Copy link

Ashe-Oro commented Oct 3, 2022

Problem

HTS NFTs are not supported by Metamask mobile app. When attempting to add an HTS NFT, the metamask mobile wallet errors with Personal address detected. Input the collectible contract address

image

Note: User is able to add the same NFT Collection (ie token_id) to the Metamask chrome extension.

Details:
Platform: Hedera testnet
token_id: 0.0.48014385
evmAddress: 0x0000000000000000000000000000000002dca431
OS: Android 13
MM version: 5.7.0 (972)

Steps to reproduce:

  1. Create HTS NFT and send to your account
  2. Open MM mobile wallet select "NFTs"
  3. Click "import NFTs"
  4. Enter Address and ID of the NFT which is already in your account.
  5. Note error message Personal address detected. Input the collectible contract address

To test ERC721 tokens, do the exact same steps with an ERC721 asset in your account.

Solution

So on MM mobile, it specifically asks for the contract address and ID whereas the chrome extension does NOT ask for ID. The ID here is the serial number of the NFT.

I have no issues adding a Hedera ERC721 NFT asset to MM mobile, only HTS NFTs.

Alternatives

No response

@Ashe-Oro Ashe-Oro added the enhancement New feature or request label Oct 3, 2022
@Nana-EC Nana-EC added this to the 0.10 milestone Oct 5, 2022
@dimitrovmaksim
Copy link
Collaborator

dimitrovmaksim commented Oct 5, 2022

Hey, the issue here is that HTS token addresses are actually account addresses and not contract addresses, and probably this is why you get the Personal address detected. Input the collectible contract address error. I'm not sure if anything can be done about this

UPDATE

Metamask performs eth_getCode for that address, but currently the result for HTS token addresses is INVALID_CONTRACT_ID

@georgi-l95
Copy link
Member

Hey, @Ashe-Oro
This problem will be fixed with this PR #598 . You can try again to add your NFT when this change get to testnet. If you are still experiencing issues, reopen this issue or open another one.

Repository owner moved this from Sprint BackLog to Done in Smart Contract Sprint Board Oct 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request limechain P1
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants