-
Notifications
You must be signed in to change notification settings - Fork 819
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
Amplify command not working #13411
Comments
Hey @elkee2003, thank you for reaching out. Could you try running |
I have tried amplify -v --debug, there was no output.I have looked for the logs, nothing.I have uninstalled and reinstalled amplify using npm install -g @aws-amplify/cli, still nothing. Just to reiterate, this thing just happened out the blue. On Wednesday, November 15, 2023 at 03:47:19 PM GMT+1, Kethan sai ***@***.***> wrote:
Hey @elkee2003, thank you for reaching out. Could you try running amplify -v --debug and let us know if you observe any output.
could check the logs at C:\Users\<username>\.amplify\logs, run the amplify -v --debug and open the file that contains the latest date. Could you provide us the logs from the file this would help us in diving deeper.
Additionally, could you try reinstalling Amplify CLI using npm install -g @aws-amplify/cli or curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd for windows.
does the native CMD terminal with administrator permission also show similar behavior.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I forgot to show a screenshot of what I did. Please locate the attached
On Wednesday, November 15, 2023 at 04:05:38 PM GMT+1, opubo inko-tariah ***@***.***> wrote:
I have tried amplify -v --debug, there was no output.I have looked for the logs, nothing.I have uninstalled and reinstalled amplify using npm install -g @aws-amplify/cli, still nothing. Just to reiterate, this thing just happened out the blue. On Wednesday, November 15, 2023 at 03:47:19 PM GMT+1, Kethan sai ***@***.***> wrote:
Hey @elkee2003, thank you for reaching out. Could you try running amplify -v --debug and let us know if you observe any output.
could check the logs at C:\Users\<username>\.amplify\logs, run the amplify -v --debug and open the file that contains the latest date. Could you provide us the logs from the file this would help us in diving deeper.
Additionally, could you try reinstalling Amplify CLI using npm install -g @aws-amplify/cli or curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd for windows.
does the native CMD terminal with administrator permission also show similar behavior.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hey @elkee2003, interesting. i was not able to reproduce in a windows environment. what is the npm and node version currently installed? it appears the screenshot being referred to on the previous comment may have not come in. |
My node version is 18.14.2. Also, I have reattached the files On Wednesday, November 15, 2023 at 04:26:01 PM GMT+1, Kethan sai ***@***.***> wrote:
Hey @elkee2003, interesting. i was not able to reproduce in a windows environment. what is the npm and node version currently installed?
it appears the screenshot being referred to on the previous comment may have not come in.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Npm verison is: 9.8.1
On Wednesday, November 15, 2023 at 04:32:19 PM GMT+1, opubo inko-tariah ***@***.***> wrote:
My node version is 18.14.2. Also, I have reattached the files On Wednesday, November 15, 2023 at 04:26:01 PM GMT+1, Kethan sai ***@***.***> wrote:
Hey @elkee2003, interesting. i was not able to reproduce in a windows environment. what is the npm and node version currently installed?
it appears the screenshot being referred to on the previous comment may have not come in.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thank you for the information, as a quick test could you try removing the |
I tried what you see in the screenshot twice and I got same result. Should I resort to npm i -g @aws-amplify/cli? It is important to note that my internet connection is ok
On Wednesday, November 15, 2023 at 05:43:08 PM GMT+1, Kethan sai ***@***.***> wrote:
Thank you for the information, as a quick test could you try removing the C:/user/<user-name>/.amplify folder and if present remove the C:/user/<user-name>/.amplify-pending-delete.exe file.
Then install amplify CLI using curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd.
Do let us know if the behavior persists.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I have installed it using `npm i -g @aws-amplify/cli`, and it worked. Thank you so much. Now about the Synchronization issue, I have been making complaints in the past about my data in amplify studio not automatically syncing with my data in the local server. The last time we spoke about this you said if the solution you gave me didn't work you were going to transfer me to your javascript team.
On Wednesday, November 15, 2023 at 05:43:08 PM GMT+1, Kethan sai ***@***.***> wrote:
Thank you for the information, as a quick test could you try removing the C:/user/<user-name>/.amplify folder and if present remove the C:/user/<user-name>/.amplify-pending-delete.exe file.
Then install amplify CLI using curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd.
Do let us know if the behavior persists.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Glad to hear that you were able to get the commands working, I also transferred the issue aws-amplify/amplify-js#12573 to our JS repository for additional assistance. Closing the issue. |
|
Before opening, please confirm:
App Id
dnxdny8iom5jq
Region
us-east-1
Environment name
VS code
Figma File Version (if applicable)
No response
Amplify CLI Version
12.4.0
If applicable, what version of Node.js are you using?
v18.14.2
What operating system are you using?
Windows
Browser type?
Google Chrome
Describe the bug
No amplify command is working, even
amplify version
is not working. I know the version I am using because I have checked before.I also have another complaint of my data being unable to sync from amplify studio to my local server. I have made this complaint previously but I have not gotten a solution yet.
Expected behavior
Reproduction steps
running any command does not work. When I type a command nothing comes up. Please check attached.
Project Identifier
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: