Kethan sai

Hey @kazuki-takaya-sp, could you provide some information on the build failures you are experiencing on the export command. Any notable error messages?

@kazuki-takaya-sp glad to hear you were able to resolve the issue. Closing this issue, do reach out if you are experiencing any issues with Amplify CLI

Hey @ankit-927, the issue appears to be similar to https://github.com/aws-amplify/amplify-cli/issues/11765, when installing Amplify behind a corporate proxy or VPN. Are you utilizing a proxy or VPN? if yes, I would...

@ankit-927 found a similar issue [here](https://learn.microsoft.com/en-us/answers/questions/1320695/the-revocation-function-was-unable-to-check-revoca). This issue appears to be related to your network or network settings on your machine. Verify your local settings to check if a [proxy...

Hey @fistofzen, could you provide us the full error message printed on the terminal? Does the project have a `team-provider-info.json`? Tried reproducing the error message with and without a `team-provider-info.json`...

@fistofzen tried reproing this issue with a new account and removing the `team-provider-info.json` then run `amplify init` selecting the new profile but did not observe any init failure. Are you...

@fistofzen could you provide us the local yarn version being used. Could you trying using the yarn version `1.22.19` and retry the command.

Hey @GlenTiki, thank you for reaching out. Marking this as feature request to remove `amplify-state.json` from `.vscode/settings.json`.

Hey @MrFarhan, thank you for reaching out. The REST API currently only support creating path with Lambda proxy integration which should support all the methods request. But if you are...

@MrFarhan this is currently not supported with Amplify CLI. This is currently being tracked on https://github.com/aws-amplify/amplify-category-api/issues/316. Refer to the comment https://github.com/aws-amplify/amplify-category-api/issues/316#issuecomment-1129357342 providing this information.