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

[Bug]: Cant connect to metamask after latest major upgrade in web3js to v4.x.y #60

Closed
begonaalvarezd opened this issue Jun 20, 2023 · 3 comments · Fixed by #61
Closed

Comments

@begonaalvarezd
Copy link

web3js has recently released a major upgrade to v4.x.y and this library does not seem to be compatible anymore with that version.
The latest version I seem to be able to get compatibility with is v1.3.4

If eg I try to connect to a chain with ID 1071 I get the following error coming from the web3js library added using the cdn (which points to latest).

s: Web3 validator found 1 error[s]: value "1071" at "/0" must pass "hex" validation

If needed I can provide a repository and a deployment url

Thank you very much 🌷

@begonaalvarezd begonaalvarezd changed the title [Bug]: Cant connect to metamask after latest major upgrade in web3js to v4.x.y [Bug]: Cant connect to metamask after latest major upgrade in web3js to v4.x.y Jun 20, 2023
@govi218
Copy link

govi218 commented Jun 20, 2023

I had this issue as well; found compatibility with [email protected] and had the exact same error with the latest version.

@clbrge
Copy link
Owner

clbrge commented Jun 22, 2023

I would need a testcase since It's probably not strictly related to svelte-web3 . chainId have been migrated to native BigInt which create all kind of incompatibilities.

@Crelde
Copy link
Contributor

Crelde commented Jul 15, 2023

I have the same issue.
I created a minimal testcase

Though its really just following the Installation instructions + basic usage in the readme.

@clbrge I hope you have a chance to have a look! :)

ps. @begonaalvarezd Nice to see somebody from IOTA here, hey from IOTA Heroes! :)

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

Successfully merging a pull request may close this issue.

4 participants