Closed emmap3-do closed 3 months ago
I've been looking at how it works, so far I found that when clicking on 'Confirm and Lock' button, it makes a request to api.build5.com/ordernft, which returns back some data to the browser including a 'uid'. Then, it stores this id in a local storage variable named 'App/checkoutTransaction'.
When you close the checkout popup, and click on 'Open Checkout' button, it is making a request to api.build5.com/api/getManyById provinding the uid from that local storage variable, in order to fetch nft details back to the UI.
At least this is how I think it works by running it locally.
Now, when I checked the same thing on the live website, I found that when it calls api.build5.com/api/getManyById upon clicking on 'Open Checkout' button, it is sending different uid value than the one stored in the local storage. So I guess this is the issue, it can't fetch the right data to open the checkout details up again.
On top of that, I found that on the live website there are multiple requests made to api.build5.com/api/getManyById, always sending different uids (never the one that matters).
Stale issue, closing!
Describe the bug When buying an NFT, if I accidentally close the checkout window, the "Open Checkout" blue button does not bring it back up (clicking on it does not seem to have any effect).
To Reproduce
Expected behavior 'Open checkout' button should open up the checkout popup window again so the user can complete the process.
Desktop (please complete the following information):
Additional context I wanted to replicate the bug locally, so I run the app from master branch. But I wasn't able to reproduce the bug!