Missing metadata nfts in the mobile application

### **Description**

I have done many tests by deploying different collections and I have noticed that on some collections I do not see the metadata (image, name and description) correctly while on others I do.

What I found is that if I pass to the ERC1155 constructor the IPFS uri of the folder with all the json (which have the format below) of the tokens metadata (e.g. ipfs://IPFSHASH/{id}.json) as per the standard, I don’t display any nft correctly, but I see the black background with “collection_name #id_token”. If I pass a baseURI without {id}.json instead, it works. I have also tried re-importing the token more than once, also clearing the cache, but no positive results.

In all this, the nfts that I do not see on MetaMask I see correctly on OpenSea.

I wanted to ask if it is possible to find a solution to this and what is the clean way to display a collection with pinned metadata on IPFS.

I am waiting for answers, thanks in advance.

### **Technical Details**

The collections I tested use the erc1155 standard and follow the following format for the metadata of tokens pinned to Pinata IPFS:

{
“name”: “Token Name”,
“description”: “Token Description”,
“image”: “ipfs://IPFSHASH”,
“animation_url”: “ipfs://IPFSHASH”,
“attributes”: [
{
“trait_type”: “test1”,
“value”: “Value1”
},
{
“trait_type”: “Test2”,
“value”: “Value2”
}
]
}

where IPFSHASH = QmNfKHs…

Start by reproducing the ERC1155 metadata display problem in the mobile application with an IPFS URI containing the `{id}.json` pattern, comparing it with a base URI that omits the pattern. Done means token image, name, and description display correctly for the affected collection, consistently with the metadata visible on OpenSea.

Written by the indexing model from the issue text.