You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
Hi team,
I've recently updated to CLI version 1.7.4 and I've noticed that when I move on an initial input, such as the screenshot attached, it freezes and I have to crash out of the terminal.
I've confirmed the issue with a few members of the team and we're all experiencing it across environments (Cloud9/Linux server & local MacOS terminal).
To Reproduce
Steps to reproduce the behavior:
Instal latest version of Amplify cli
run "amplify init" and it will freeze after the initial input.
Expected behavior
A clear and concise description of what you expected to happen.
Looks to be a bug with the newest version.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Mac-Os/Linux server
Additional context
Add any other context about the problem here.
Looks like there could be a related issue here - #1688
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
Hi team,
I've recently updated to CLI version 1.7.4 and I've noticed that when I move on an initial input, such as the screenshot attached, it freezes and I have to crash out of the terminal.
I've confirmed the issue with a few members of the team and we're all experiencing it across environments (Cloud9/Linux server & local MacOS terminal).
To Reproduce
Steps to reproduce the behavior:
Instal latest version of Amplify cli
run "amplify init" and it will freeze after the initial input.
Expected behavior
A clear and concise description of what you expected to happen.
Looks to be a bug with the newest version.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
Looks like there could be a related issue here -
#1688
The text was updated successfully, but these errors were encountered: