[SOLVED] Metadata missing on some wallet items when reading it from API

Technical Issue Reporting
#23

do you have some example that have this problem?
chain, token address, token id

#24

The wallet address : 0x493952E335EdD37Fd73C60eA05Ce12154859BB0e
The token address : 0x9c09596d3d3691ea971f0b40b8cad44186868267
Chain : Polygon
Token id examples : 1234, 1233

This items was working fine and all of sudden now they null in metdata

#25

we are investigating, thanks for reporting

#26

You are welcome, please keep me updated and thank you :slight_smile:

#27

can you check again now?

#28

That wallet address it showing it items back but there still many address with same problem sadly

#29

And I want to add during the night more of this problem kept showing on more than one address

#30

can you give other examples now with that problem?

#31

Wallet address : 0x2a5d77939b5021cd3f6a651dec5aef46b96d2168 (There many examples like that)
on same token address, chain and such

#32

we identified an issue yesterday, and we fixed it, we are going to resync the metadata for that token address.
are there other token addresses that have this same problem?

#33

We not using any other token address for now beside this

1 Like
#34

now it should work as expected, there are few token ids that seem to have a token uri that returns 404 error: 2587, 2590, 2591, 2586, 2588 and 2589

#35

I will check everything, thank you

#36

@cryptokid
Hello again, can we have full refresh on the token address.

There some items that even the API can’t resync anymore and it been like that for 2 weeks, now there more items that is broken and not showing special after wallet moving items between each other.

If we can have full resync on the whole token address, that would be great.

The token address : 0x9c09596d3d3691ea971f0b40b8cad44186868267

#37

I can not easily to that resync, you could run resync to for every token id

what is an example where resync didn’t work?

#38

5934 and 5926 for now refusing to resync and API keep returning “The metadata could not be updated! Try again later”

#39 
https://deep-index.moralis.io/api/v2/nft/0x9c09596d3d3691ea971f0b40b8cad44186868267/5934?chain=polygon&format=decimal

=>
{
  "token_address": "0x9c09596d3d3691ea971f0b40b8cad44186868267",
  "token_id": "5934",
  "transfer_index": [
    31894304,
    31,
    120,
    0
  ],
  "owner_of": "0xb312fa3fde1d0c21603a607abb239fed3286f709",
  "block_number": "31894304",
  "block_number_minted": "31894304",
  "token_hash": "16254077377152c418181ad85fcf7a72",
  "amount": "1",
  "contract_type": "ERC1155",
  "name": "Forest Knight: Kingdoms at War",
  "symbol": "ForestKnight",
  "token_uri": "https://app-api.forestknight.io/nftMetaData/000000000000000000000000000000000000000000000000000000000000172e",
  "metadata": null,
  "last_token_uri_sync": "2022-08-21T17:30:12.965Z",
  "last_metadata_sync": "2022-08-21T17:31:55.098Z"
}

that particular uri doesn’t work for me, meaning that I not able to see the metadata

is that the expected token_uri?

#40

5934,
5933,
5932
This is the 3 tokens.

And let me check on the url and come back to you

1 Like
#41

https://app-api.forestknight.io/nftMetaData/5934

The token should look like that, the url

#42

this is the returned token id from the contract (https://polygonscan.com/address/0x9c09596d3d3691ea971f0b40b8cad44186868267#readContract):

 https://app-api.forestknight.io/nftMetaData/{id}

based on the specifications for erc1155 it should be that token uri in the hex format:

https://app-api.forestknight.io/nftMetaData/000000000000000000000000000000000000000000000000000000000000172e

but the actual token id that is used is:

https://app-api.forestknight.io/nftMetaData/5934

and now we are able to handle only that version from ERC1155 specifications