After migration NFT collection does not update with new owner of NFTs and internal errors

iotaflea commented 6 months ago

If you look at NFT collection: https://soonaverse.com/collection/0x81a7845b52d0725c607c80a2c83d390334565b09

NFTs still remain for sale at floor and within prior owners soonaverse profile. It appears as though Soonaverse captured the private sale but new owner cannot withdraw and receives error along the lines of "internal error". NFTs do not appear in new owners profile.

New owner can change listing price... but collection and marketplace page does not change listing from prior owner and price.

emmap3-do commented 6 months ago

@adamunchained this issue is related to what I mentioned today

epochzro commented 6 months ago

I suspect its related the call for transactions our bots use to relate sales and listings to users

https://api.buildcore.io/search/getUpdatedAfter?dataset=nft&updatedAfter=(timestamp_here) The above call returns no records

@adamunchained the vacation is over... get to work !

iotaflea commented 6 months ago

I've also deposited numerous NFTs and it shows as success with correct owner. But the NFTs cannot be found and are not within the user profile.

emmap3-do commented 6 months ago

If I got it right from @adamunchained , Soonaverse is using Algolia for some lists (eg. collection nft list, profile nft list) and it seems Algolia is not properly syncing the data for Soonaverse, hence some lists show old data.

Based on this, the issue @epochzro mentions is a separate one, because it's related to the usage of the API, which is returning 404 error on any requests. I've just tried a working request I had on Postman and it returns 404: https://api.buildcore.io/api/getById?collection=member&uid=0x4bdea1ceb9f480d6116b3d12855554b382d33692

I've tried GET and POST verbs. I've tried with and without /api in the url, same response: 404 not found

Maybe there is something blocking by IP or something new that was added to the APIs and we're not aware?

epochzro commented 6 months ago

try this one https://api.buildcore.io/search/getById?dataset=member&uid=0x4bdea1ceb9f480d6116b3d12855554b382d33692

epochzro commented 6 months ago

seems like api and collection no longer work as of this morning (EST)

emmap3-do commented 6 months ago

You're right.

Minor thing, I tried that one you provided and returned an error saying setId is required. So, I replaced uid with setId and it worked: https://api.buildcore.io/search/getById?dataset=member&setId=0x4bdea1ceb9f480d6116b3d12855554b382d33692

epochzro commented 6 months ago

Still no luck with this one though... https://api.buildcore.io/search/getUpdatedAfter?dataset=nft&updatedAfter=(timestamp_here)

epochzro commented 6 months ago

@adamunchained is someone looking into this or should we just move on?

flyingrabbit-lab commented 6 months ago

Algolia should be fixed now. Could you check and confirm please?

I am currently checking why getUpdatedAfter is not working.

iotaflea commented 6 months ago

Ok things seem to be moving forward. Owners seem to now be updated. but the collection page now doesnt display listing prices or anything.

epochzro commented 6 months ago

he likes you more flea... for some reason it was more important than the api

flyingrabbit-lab commented 6 months ago

Api is also fixed now

epochzro commented 6 months ago

sweet !! confirming now

epochzro commented 6 months ago

have fields changed? i'm getting key errors... updateon._seconds looks to be updatedon.seconds now are there any others?

flyingrabbit-lab commented 6 months ago

Only that and nanoseconds. So date fields don't have the underscore anymore.

epochzro commented 6 months ago

entry['payload']['restrictions']['nft']['saleAccess']

key error on nft now

flyingrabbit-lab commented 6 months ago

Could you send me a transaction id?

epochzro commented 6 months ago

looks liek things have moved

flyingrabbit-lab commented 6 months ago

Not on payload.restrictions.

iotaflea commented 6 months ago

withdrew NFTs... then they disappear from soonaverse as normal, then later, they reappear in profile. of course clicking on them, they return the normal error that they are in another universe but never seen that before where it refreshes with old data again and withdrawn NFTs come back

epochzro commented 6 months ago

I think I got it to a working state, there were a lots of changes and i'm sure i'm not done finding them

iotaflea commented 6 months ago

opening another issue now. deposit NFT sent to deposit address and stayed there. nothing happened...

adamunchained commented 6 months ago

Ok things seem to be moving forward. Owners seem to now be updated. but the collection page now doesnt display listing prices or anything.

What do you mean by listing price? If I select NFT on Sale it shows them. I don't think price is shown since bulk purchase was added. or was it?

adamunchained commented 6 months ago

@flyingrabbit-lab - I think I understand the issue. This is due Algolia as suspected. Soonaverse really need to stop using it. It causing all these issues. It should use the API directly to produce lists.

Syncing into Algolia is not properly synching "date" across. See availableFrom is coming back as empty Timestamp in the Algolia's result:

This is why price field does not show. It shows on the actual NFT record because that's retrieving the data directly from BUILDCORE API's.

flyingrabbit-lab commented 6 months ago

Algolia should be up to date now. Could you check please?

adamunchained commented 6 months ago

It was a Soonaverse issue, I've just pushed fixed and released into prod. There was an inconsistency how Soonaverse deals with date field on availableFrom coming from Algolia.

soonaverse / app

After migration NFT collection does not update with new owner of NFTs and internal errors #152