-
Notifications
You must be signed in to change notification settings - Fork 89
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
EAS Cli is not recognized after installation #2369
Comments
I'm facing the same issue too. Still have not figured out the solution for this! I have 3 projects finished but cannot build because of this one issue! |
It doesn't seem like an issue/bug with EAS CLI. It looks like a problem with your Node installation on a Windows machine - binaries installed via I would start with finding the directory where |
use eas command with npx was worked for me. for examlpe: |
This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed. |
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem. |
I'm facing the same issue too. Still have not figured out the solution for this! |
work for me |
What?, what i have to do first ? |
for me using npm solved the issue |
Build/Submit details page URL
I am wanting to build but i can't because of that error
Summary
I installed eas cli from the docs, with
npm install --global eas-cli
after succesful installation i check foreas login
but i shows me this. even restarting my OSManaged or bare?
Bare
Environment
expo-env-info 1.2.0 environment info:
System:
OS: Windows 11 10.0.22621
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\scoop\apps\yarn\current\bin\yarn.CMD
npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
Error output
Terminal reloaded
Reproducible demo or steps to reproduce from a blank project
it is happening with all my projects
The text was updated successfully, but these errors were encountered: