Kethan sai

Hey @thegrandpooba, thank you for reaching out. It appears the behavior is occurring due to following https://github.com/aws-amplify/amplify-cli/blob/a644a1f1577c29567c1b6986cc6041ef99623219/packages/amplify-cli-core/src/utils/packageManager.ts#L109-L118 To mitigate the issue you could try removing the `yarn.lock` and `node_modules` from...

apologies on the delay in a response. diving into the code https://github.com/aws-amplify/amplify-cli/blob/a644a1f1577c29567c1b6986cc6041ef99623219/packages/amplify-cli-core/src/utils/packageManager.ts#L130-L156 it appears the code checks for any lock file first present in the directory: The order of check:...

Hey, thanks for raising this! I'm going to transfer this over to our codegen repository for better assistance.

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

Hey, thanks for raising this! I'm going to transfer this over to our codegen repository for better assistance

Hey @stephenjen, thank you for reaching out. To modify the authorizer on the REST API, you would need to override the resource. Refer to [AWS Amplify documentation on authorizing API...

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

Hey @nootn, thank you for reaching. Marking this as feature request for `customType ` enhancement on form generation.

Reproduced this behavior, this does not appear to be a supported workflow. marking this as feature request for further evaluation.

Hey, thanks for the feedback and information on how this can be solved. Transferring the issue to the documentation repository for updates.