Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dapp frontend errors #2

Open
aashidham opened this issue Mar 14, 2023 · 4 comments
Open

Dapp frontend errors #2

aashidham opened this issue Mar 14, 2023 · 4 comments
Assignees

Comments

@aashidham
Copy link
Contributor

aashidham commented Mar 14, 2023

If the user does not update the client contract address, the user can press submit and receive an error:

Something went wrong. Error missing revert data (action="estimateGas", data=null, reason=null, transaction={ "data": "0xdd27fe90000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000001600000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001c0000000000000000000000000000000000000000000000000000000000007ef40000000000000000000000000000000000000000000000000000000000017bb000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000000270181e203922020a7e9e959fc0aaea427901d3000682bd90b7d5f4cb2ef2cf447e3b0a615fb72250000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000406261676136656134736561716b7032706a6c683661766c766565366962326d61616e617635736333356c35676c66337a6d36726436686d666763783578656a690000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000480d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006f68747470733a2f2f646174612d6465706f742e6c69676874686f7573652e73746f726167652f6170692f646f776e6c6f61642f646f776e6c6f61645f6361723f66696c6549643d38363266623131352d643234612d346666312d613163382d6561646262626664313963662e6361720000000000000000000000000000000000", "from": "0x2A089369A955d97c44370AD1bafcB4FE47fc74fe", "to": "0xf4E0C74D76Bf324293bB3B3DA184d164d06F7664" }, invocation=null, revert=null, code=CALL_EXCEPTION, version=6.1.0)

See related Slack thread here: https://filecoinproject.slack.com/archives/C04QGFF5EDR/p1678766374041759

@lordshashank
Copy link
Contributor

Me getting same after cloning
image

@lordshashank
Copy link
Contributor

Just change the contract address at line 11 in frontend/src/components/input.js with the contract address of your own deployed contract. It worked for me.

@xBalbinus
Copy link
Contributor

xBalbinus commented Mar 15, 2023 via email

@aashidham
Copy link
Contributor Author

aashidham commented Mar 20, 2023

The original scope of the issue assumes that you do not change the frontend/src/components/input.js, since the README and code comments make clear this is what is expected from the user. However, it is useful to analyze the unhappy path. Why is this necessary? What actually goes wrong?

Perhaps some more granular logging in the frontend and client contract can help resolve this.

However until we have some understanding of what is going on here, I would recommend we leave the issue open. =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants