I have been attempting to install nRF Connect SDK on macOS for several months without complete success. You can check my prior tickets for details. Nonetheless, I have recently made progress by ensuring that all traces of the SDK and, in particular, west, are removed before attempting a new installation. (I'll update my last ticket with more details on this.) -- enough progress to allow me to encounter the following problem with the VS Code IDE:
- When following Video 3 of the getting started series: nRF Connect for VS Code, 3: Building an application & Exploring windows. at 2:30, an application build has been completed. The lecturer has dragged up from the bottom bar of the VS Code window to open a terminal pane, which shows the output from the build process.
- At the bottom of the pane, a note is attached: "Terminal will be reused by tasks, press any key to close it."
- If I then click in the pane to give it focus and type a key (e.g., "m" or "l"), my applications will immediately crash.
- And I mean, my "applications', not only the VS Code app, but also all other open apps( e.g., nRF Connect, Safari, Mail, etc., background apps like Parallels Toolbox, even Finder). It's almost the same as a reboot (except the system isn't reloaded). Hence my description of the bug as severe.
- This bug is repeatable; also occurs later when following the video sequence to add and build a second app.
- I have never seen anything like this in VS Code before installing the nRF Connect package.
I'm actually impressed by this bug. Seems interesting that it can have effect beyond the VS Code app itself, without a total system crash.
Will be interesting to see if your engineers can reproduce this behavior. I should note that I'm not running an entirely stock macOS Monterey (Version12.1 Beta, Build 21C5039b, the latest developer release). I'm running on a MacBook Pro 10,1 (early 2013). which is not directly supported by Apple for Monterey. I'm using OCLP (OpenCore Legacy Patcher) to fool macOS into thinking I have a slightly more modern machine. Hard to see how this could be the root of this bug. In the case of my machine, the only patches used are for graphics acceleration. I've never seen any similar problem with OCLP before. Will be happy to run additional diagnostics with your engineers if there's any indication that my specific configuration is at fault.
Mike (making slow, but incremental progress with configuring SES and VS Code IDEs for nRF Connect)
