Troubleshooting problems with IDEs - Amazon CodeCatalyst

Troubleshooting problems with IDEs

Consult the following sections to troubleshoot problems related to IDEs in CodeCatalyst. For more information on IDEs, see Using Dev Environments with an IDE.

I have mismatched runtime image versions in AWS Cloud9

AWS Cloud9 is using different versions of the frontend asset and the backend runtime image. Using different versions might cause the Git extension and AWS Toolkit to work incorrectly. To fix the problem, navigate to the Dev Environment dashboard, stop your Dev Environment, and then start it again. To fix the problem using APIs, use the UpdateDevEnvironment API to update the runtime. For more information, see UpdateDevEnvironment in the Amazon CodeCatalyst API reference.

I can't access my files in /projects/projects in AWS Cloud9

The AWS Cloud9 editor is unable to access files in the directory /projects/projects. To fix the problem, use the AWS Cloud9 terminal to access your files or move them to a different directory.

I can't launch my Dev Environment in AWS Cloud9 using a custom devfile

Your devfile image might not be compatible with AWS Cloud9. To fix the problem, review the devfile from your repository and corresponding Dev Environment and create a new one to continue.

I'm having issues in AWS Cloud9

For other issues, check the troubleshooting section in the AWS Cloud9 User Guide.

In JetBrains, I can't connect to my Dev Environments through CodeCatalyst

To fix the problem, check that you have only latest version of JetBrains installed. If you have multiple versions, uninstall the older versions and register your protocol handler again by closing the IDE and the browser. Then open JetBrains and register the protocol handler again.

I can't install AWS Toolkit for my IDE

To fix this problem for VS Code, manually install AWS Toolkit for Visual Studio Code from GitHub.

To fix this problem for JetBrains, manually install AWS Toolkit for JetBrains from GitHub.

In my IDE, I can't launch my Dev Environments

To fix this problem for VS Code, check that you have latest version of VS Code and AWS Toolkit for Visual Studio Code installed. If you don't have the latest version, update and launch your Dev Environment. For more information, see Amazon CodeCatalyst for VS Code.

To fix this problem for JetBrains, check that you have latest version of JetBrains and AWS Toolkit for JetBrains installed. If you don't have the latest version, update and launch your Dev Environment. For more information, see Amazon CodeCatalyst for JetBrains.