Kethan sai

Hey, thank you for filing this. Marking this as feature request.

Hey @dotto95, thank you for reaching out. Tried reproducing the issue with the following steps and latest Amplify CLI version. 1. created a new user pool with app client and...

Hey @dotto95, curious when running `amplify import auth` are you importing both the user pool and identity pool? you should be able to import the existing user pool and the...

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @sidshrivastav, thank you for reaching. The issue is currently being tracked on https://github.com/aws-amplify/amplify-cli/issues/13001 and https://github.com/aws-amplify/amplify-cli/issues/13377. Refer to the workarounds posted here: https://github.com/aws-amplify/amplify-cli/issues/13001#issuecomment-1906930211 and https://github.com/aws-amplify/amplify-cli/issues/13377#issuecomment-1901602090 After switching to npm, was...

Hey @sidshrivastav, the `amplify.state` may be hidden on Vscode. Could you open the `.vscode/setting.json` and set the `"amplify/**/amplify.state"` as `false`. Additionally, refer to comment https://github.com/aws-amplify/amplify-cli/issues/13377#issuecomment-1948367193 providing information on using yarn...

@sidshrivastav thank you for the information. We can add/modify the scripts in the state to modify the build command. For example default lambda function: ``` { "pluginId": "amplify-nodejs-function-runtime-provider", "functionRuntime": "nodejs",...

Closing the issue due to inactivity. Do reach out to us if you require any assistance.

Hey @basadee, thank you for reaching out. The error appears to be due to a permission issue when trying to create a new user. Do you experience a similar error...

Hey @basadee , thank you for confirming this. Wanted to get some additional information. 1. How was Node/npm installed? was this installed as administrator? 2. what is the output of...