Cannot debug on Linux

I am having trouble getting VS Code to work in a debug session with the simulator on my Linux development machine. The simulator works fine from both VS Code and command line, however when I attempt to run in debug mode with some breakpoints set, the simulator simply runs and the breakpoints are grayed out in VS Code. If I set a watch, it shows "not available", any command in the debug console is returned with "Internal error.". If I pause the debugging, the simulated program will stop running, but in VS Code I get a new tab open titled <native api> and in it is the following error message "The editor could not be opened due to an unexpected error: Cannot read properties of undefined (reading 'create')"

It seems like there is some sort of failure in connecting to whatever debug service runs in the simulator, but I am not sure.

Does anyone have any suggestions on what I might want to try to fix this?

  • The CIQ SDK and tools are only supported on a limited number of Linux distros.  Here's a post from one of the Garmin CIQ folks: https://forums.garmin.com/developer/connect-iq/i/bug-reports/no-longer-able-to-run-sdk-manager-or-simulator?CommentId=06dc24e2-5226-44fc-be58-bf15d527bf2c

    "Like Jim mentioned, be sure you're using the latest SDK Manager. We had an issue like this in version 1.0.4 that affected both Windows and Linux. Also, not sure how relevant this is, but we only support the LTS version of Ubuntu Linux and can't guarantee our tools with function properly on other distros."

  • Thanks. I should have mentioned more about my configuration. I am using Ubuntu 22.4 LTS.

    But after fighting with this all day, I finally found the problem. I had created a symbolic link to the '.Garmin' folder to make it easier to access and I was using the samples directory. If VS Code acccesses the project through that symbolic link, then the debug connection to the simulator will be broken.

  • Dealing with an inserted disk that's unreadable by your PC can be a perplexing and frustrating experience, seemingly making debugging an impossible task. When faced with such issues, it's crucial to explore potential solutions to salvage your data and restore functionality. From corrupted file systems to incompatible formats, the causes can be diverse. A comprehensive guide on fixing the "disk not readable" problem on a Mac is available at https://setapp.com/how-to/fix-disk-not-readable-issue. This resource provides step-by-step instructions and valuable insights to troubleshoot and resolve the problem. Whether it's a malfunctioning external drive or an internal disk issue, the guide offers practical solutions to make your disk readable again, minimizing data loss and ensuring your MacBook operates seamlessly. Don't let the frustration linger; tackle the problem head-on with the assistance of this informative guide.