-
Notifications
You must be signed in to change notification settings - Fork 17
Cannot Bid On A Card #50
Comments
@erights If you could look at this and advise, as it seems to be dying in Zoe. |
It looks like something called |
I just narrowed it down to this line in the contract: session.makeBidInvitation() Which invokes the zoe auction contact And the actual error being thrown in Which points to some installation being a promise. However, I'm checking all the "installation" references in the contract and deploy scripts, and they all seem to be resolved before being passed to zoe. |
@erights I determined that it was the |
The root cause is that But I'm not sure if that's better than the above. Perhaps we should even be fixing the fact that |
This call to
I don't understand why it doesn't work:
@michaelfig didn't we fix that? |
I had fixed it with a |
Btw, it is named |
@dckc, the path to the client now goes through |
This should be fixed now from #51. However, it seems like there's work we want to on the chain in addition. Perhaps we should create a separate issue under |
Describe the bug
I have been trying to run the demo following the steps on the README.md. Everything was okay until I try to bid on a card. When I click on a card and the details view opens, then I set the bid amount and clieck "Bid" button, the issue shows itself. The button gets stuck at the clicked state and stays that way until it times out.
To Reproduce
Steps to reproduce the behavior:
Start the local chain on the 5000 port.
export PORT=5000 agoric start --reset --verbose
Open the wallet using port 5000
Deploy Api and the Contract
export API_URL=http://127.0.0.1:5000 agoric deploy --hostport 127.0.0.1:5000 contract/deploy.js api/deploy.js
Start UI
Add wallet bridge to
https://local.agoric.com/
Enable DApp from the wallet
Go to UI
Click on a Card
See details view
Set a bid amount
Click "Bid"
See the text on the button turn into "Submitting" in a clicked state
Gets stuck
Expected behavior
To see the minted card nft in my wallet
Platform Environment
Additional context
Below are the stack traces for both backend and frontend
Frontend
Backend
Screenshots
Below is the screenshot of the stuck state
The text was updated successfully, but these errors were encountered: