-
Notifications
You must be signed in to change notification settings - Fork 547
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
FIX: Error while running ignite scafflod in MacOS M3 Sequioa #4375
Comments
I wish to 100% confirm this bug. It is present with both an invocation of go install ./... and make install
I'm going to go ahead and spend a few minutes trying to resolve it, but unfortunately don't have too much time right now |
The issue is also present in the latests released binaries. When I download them, it explodes. |
Need to delete your ~/.ignite folder then it will work. Maybe you were using v0.29 |
Yes i had to downgrade the version to v0.27 ....it is working now but still Relayer issue im facing |
rm -rf ~/.ignite worked :) |
Great to hear, but that's a pretty dangerous command if you have a keyring there. Unfortunately I still haven't been able to reproduce |
Context: Plugin Compatibility Issue on ARM64 Architecture (cli-plugin-network v0.2.2)
Describe the Bug:
I encountered an issue while trying to use the cli-plugin-network plugin (v0.2.2) with the Ignite CLI on an ARM64 system (Apple M1/M2). The plugin fails to load with an error related to architecture compatibility, and the system logs indicate issues with the handshake process between Ignite and the plugin.
Steps to Reproduce:
1.Use a machine with an ARM64 architecture (Apple M1/M2).
2.Install Ignite CLI.
3.ignite scaffold chain hello
Expected Behavior:
The plugin should work correctly on ARM64 architecture without errors.
Actual Behavior:
The plugin fails to load, and the following error is logged:
Failed to read any lines from plugin's stdout. This usually means the plugin was not compiled for this architecture...
Environment Details:
The text was updated successfully, but these errors were encountered: