2 Answers
- Newest
- Most votes
- Most comments
0
Thank you for reporting the Dev environment issue. I've raised it with our service team, and I'll reach out to you as soon as I have an update.
0
Hi there! From our initial investigation, it seems like an issue related to the toolkit's session. Could you please provide the version numbers of the toolkit and remote extension you are using to help us investigate further?
As a workaround, our team was able to connect to the dev environment after stopping it by following these steps:
- Connect local VSCode to CodeCatalyst.
- Open CDE using VSCode Toolkits.
- Stop CDE using VSCode Toolkits.
- Open CDE using VSCode Toolkits again (it opened in a new window) and connect to it.
Relevant content
- asked 4 months ago
- asked 4 months ago
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago