NFT Tokens with Different IPFS Not Visible on Phantom Wallet: Any Advice?

[ttoele]

Hello everyone,
I’m experiencing an issue with displaying some NFTs on Phantom Wallet, and I’d like to ask for your help to understand if there are specific limitations or possible solutions.
I’ve created an ERC-721 contract that allows for the dynamic uploading of IPFS metadata, where each token has its own unique IPFS and is added at different times. This is because my NFTs represent custom bicycles, each with unique specifications and attributes that are not available immediately.
The structure of the contract is not that of a "closed collection," as is often the case with static formats like ipfs://CID/1.png, ipfs://CID/2.png, etc. Instead, I upload the metadata for each token individually, for example:
Token #4: ipfs://bafkreid5wsjdn4in4opdcmkrxcrmzwmydakh3rygjzuzsbsmrfv6zq2miu
Token #5: ipfs://bafkreia5iggl2x44k6vobcyfla7ysg6qqljgkkdmorij4k7ji32ddgq6fa
Token #6: ipfs://bafkreigdgli5wdpel4ia67gkq7mrbou2uvuwxo3uqgac6gygf5kqadbrmi
On platforms like OpenSea, everything works perfectly: the NFTs are visible and manageable without any issues. Even when querying the contract on Polygonscan (using the tokenURI method), the IPFS metadata is correctly returned.
The problem is that these NFTs are not displayed on Phantom Wallet. I suspect this is because it is not a collection with predefined and statically structured metadata.
Has anyone here faced a similar situation? Does Phantom Wallet support ERC-721 contracts with dynamically uploaded IPFS metadata? Are there any adjustments I can make to ensure these NFTs are visible in the wallet?
Thanks in advance for any advice or information!

[adamdelphantom]

@ttoele Do you have a holder wallet address I can inspect, please?