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.

Sign up for GitHub

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

Jump to bottom

Not using correct ABI? #21

Closed
g-a-v-i-n opened this issue Oct 27, 2021 · 3 comments · Fixed by #33 or #39
Closed

Not using correct ABI? #21

g-a-v-i-n opened this issue Oct 27, 2021 · 3 comments · Fixed by #33 or #39

Comments

@g-a-v-i-n
Copy link
Contributor

g-a-v-i-n commented Oct 27, 2021 •
edited
Loading

Getting the following error when connecting to metamask on localhost

Error: Returned values aren't valid, did it run Out of Gas? You might also see this error if you are not using the correct ABI for the contract you are retrieving data from, requesting data from a block number that does not exist, or querying a node which is not fully synced.

Screen Shot 2021-10-27 at 11 10 37 AM
@g-a-v-i-n
Copy link
Contributor Author

g-a-v-i-n commented Oct 27, 2021 •
edited
Loading

Seems fine on the deployment, however I cannot access parts of the flow during dev unless I deploy.

@willbach
Copy link
Contributor

yeah I fixed this message. What parts of the flow can you not access?

@g-a-v-i-n
Copy link
Contributor Author

g-a-v-i-n commented Oct 27, 2021 •
edited
Loading

I get this message as soon as I connect to metamask in local dev, so anything that involves swapping.

@willbach willbach linked a pull request Oct 29, 2021 that will close this issue
Updating master ticket input and selection #33
Merged
@willbach willbach linked a pull request Nov 23, 2021 that will close this issue
Change eligibility check, add infura endpoint, and update ETH balance retrieval #39
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@g-a-v-i-n @willbach