Open thekesslereffect opened 2 years ago
`HTTP 200 OK Allow: OPTIONS, GET Content-Type: application/json Vary: Accept
{ "valid": false, "token_uri": "https://ipfs.io/ipfs/QmZcngsdAgfRWmAJ8S3hMmcywGZNQDe13v7ge7XjMwqWQL/0.json", "errors": [ "InvalidTokenUrlResponseException: Invalid JSON response for URL: https://ipfs.io/ipfs/QmZcngsdAgfRWmAJ8S3hMmcywGZNQDe13v7ge7XjMwqWQL/0.json" ] }`
Figured out the issue! The hidden metadata file REQUIRES an empty attributes list for some reason. So add
"attributes":[],
inside the hidden metadata file inside the curly brackets
EDIT: Check the next post first. This might be incorrect.
Update: It could also possibly be that we need to remove the comma on the last line within the curly brackets. So try that first before trying to add attributes. This is probably the issue { "name": "Name", "description": "Description", "image": "ipfs://imguri/img.png" }
Update: It could also possibly be that we need to remove the comma on the last line within the curly brackets. So try that first before trying to add attributes. This is probably the issue { "name": "Name", "description": "Description", "image": "ipfs://imguri/img.png" }
Ho-Lee Crap man. This. Thank you. I was about to literally start pulling out hair.
A comma ruined my night tonight. lol
Atualização: Também pode ser que precisamos remover a círia na última linha dentro dos suportes encaracolados. Então tente isso primeiro antes de tentar adicionar atributos. Esta é provavelmente a questão { "nome": "Nome", "descrição": "Descrição", "imagem": "ipfs://imguri/img.png" }
First, thank you very much! You just saved me a few hours of testing to find the error.
And I swear I thought about removing the comma from the code, but I thought that would be a waste of time.
After all.. it's just a comma.. lol
The metadata is now showing up again, thanks.
If it is the case of someone who is not able to display the images revealed on openea, I created a post talking about it, and how I solved it.
Check it out later when you have time.
Hi everyone. I’m having the same issues. Can this be fixed even after the contract is deployed?
I posted here earlier explaining what I thought the solution was… https://github.com/HashLips/hashlips_nft_contract/issues/57#issue-1192359970
Seems like multiple people are having this issue.