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

@metamask/abi-utils/dist/parsers/bool.js #1854

Closed
xinKyy opened this issue Jul 1, 2024 · 9 comments
Closed

@metamask/abi-utils/dist/parsers/bool.js #1854

xinKyy opened this issue Jul 1, 2024 · 9 comments

Comments

@xinKyy
Copy link

xinKyy commented Jul 1, 2024

image
After following the steps in the document to install the webAuth/modal library, the following error occurred. I am using React

@kapilkumartomar
Copy link

kapilkumartomar commented Jul 4, 2024

I encountered a similar bug related to MetaMask RPC errors. I found that there is a dependency issue: everything works fine with @metamask/[email protected], but updating the dependency causes some packages to start using 6.3.1, which then throws the above error.
image

@chaitanyapotti
Copy link
Member

Please use vite for now or eject create react app to use latest babel/env plugins

@SaschaKubisch
Copy link

Hi Team, is there any update on this?

Migrating to vite is not a small task for us, and ejecting does not work.

Starting to look into alternative authentication solutions here because we cannot deploy since 1 week now.

@chaitanyapotti
Copy link
Member

Fixed in the latest release: 8.11.0

@kapilkumartomar
Copy link

kapilkumartomar commented Jul 25, 2024

@chaitanyapotti After run yarn build it's giving same error. Not yet fixed!. Tried multiple times, by even removing node_modules, yarn.lock and build etc folders. But same above error.

@chaitanyapotti
Copy link
Member

Hey.. pls check the version of "@metamask/rpc-errors" in your lock file. If it's above 6.2.1, Please pin it to 6.2.1
That should solve it.

@shahbaz17
Copy link
Member

Hi Team, is there any update on this?

Migrating to vite is not a small task for us, and ejecting does not work.

Starting to look into alternative authentication solutions here because we cannot deploy since 1 week now.

The migration would be an easy 7-step process that we also did for our demo apps. Alternatively, some tools let you do the same.

@arpitB-dev
Copy link

Hey @shahbaz17 , we are facing the same issue when using web3auth.
the package versions are

 "@web3auth/base": "^8.12.1",
  "@web3auth/ethereum-provider": "^8.12.1",
  "@web3auth/no-modal": "^8.12.1",
  "@web3auth/openlogin-adapter": "^8.12.1",
   "@metamask/rpc-errors": "^6.2.1",

@chaitanyapotti
Copy link
Member

Please upgrade to v9. it's fixed there

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

6 participants