Unable to resolve correct data for node

[hubsmoke]

Description

User reports data folder empty, and v1 is always shown instead of v2 on the app:

dpid resolver shows successful stream publish, and 2 versions, at same anchor time: https://beta.dpid.org/api/v2/resolve/dpid/268

1st version (v1) shows DAG with Data folder present, but empty: https://ipfs.desci.com/ipfs/bafybeicg5ih6owqyptln44yctbwfeywizyjbvuceybsoxzitn6t4rqa434

2nd version (v2) shows DAG with correct data inside Data folder: https://ipfs.desci.com/ipfs/bafybeiemd2hxo3xg6h3mw6a7ngaso47ey6vujn4c3gimaxys76yzjnl42y

retrieveTree api call shows Data folder empty with .nodeKeep https://nodes-api.desci.com/v1/data/pubTree/sgxrVKsueVjYyWXSw3hxyVcGhHVZrYF3hnJaEOyHfZ4/bafkreibyxnlkpgr22ived5vjr57r4a4daaalilnmldkezk3fi5f6lmmnyq?depth=1&dataPath=root/Data

Because the two versions have the same anchor time, I wonder if~retrieveTree call or~ frontend fails to correctly sort the versions?

Additional Information

Looks like definite frontend issue, incorrect version requested

[hubsmoke]

Looks like frontend is incorrectly requesting v1 everytime. v1 looks like bafkreibyxnlkpgr22ived5vjr57r4a4daaalilnmldkezk3fi5f6lmmnyq

[hubsmoke]

Note retrieveTree result is correct for v2 when manually entering the correct manifestCid https://nodes-api.desci.com/v1/data/pubTree/sgxrVKsueVjYyWXSw3hxyVcGhHVZrYF3hnJaEOyHfZ4/bafkreiev3wxvwd3vzttjpmycb3yvi5bwbz6rnogydsa2j7oychnprtr6lq?depth=1&dataPath=root/Data

Isolated to frontend issue

[kadamidev]

https://gist.github.com/kadamidev/f42d45922ff3e10218e11e52f5313df4

[hubsmoke]

fixed