John, are you saying that you create projects, save them, etc and then when you close and reopen VS builder and click on the CF tab on the left, all of the projects are gone? That's definitely a bug...

yes this is exactly what is happening.

This is on Mac, yes?

yes macOS

First problem, its a Mac..

Seriously? Talk about trolling... 🙄

Trolling, no, your lack of attention to detail on what the M1/M2 chip, yes. Its more than likely related to this issue here: https://github.com/microsoft/vscode/issues/187765 However, its only a small fraction of the number of "Bugs" the m1/m2 chips have created.

Seriously? You point out an ARM bug and a VS Code bug so can bash on Macs?

FWIW, I also have to reopen every project in the CF Builder extension for VS Code but I'm on Windows 10. Open up VScode, go to the CF Builder area, see nothing under project manager. I have to click the import project, browse to Enter the CFBuilder Workspace Location and then Choose Project Folder to get the workspace/project to show in the project manager area. This happens even when do "File > Open Workspace from File..." option. I did check and confirm that Restore Windows and Restore View State are checked. I figured either I messed up when making them in the first place (I don't use workspaces/projects regularly) or that it was how things just worked.

@Rodney, have you seen the number of BUGS that the M1/M2 chips are causing? Have you tried to run an emulator on the new chips? Have you tried using any functioning software that works nearly flawlessly on Linux and Windows yet bombs on MacOS? I am sorry, but the chip is flawed, and the implementation of the X86 emulation is completely botched, the storage even on the "PRO" versions of the hardware is slow, compared to the previous generation, and then there is the whole driver issue, which still is a persistent problem half a year later. This is way off-topic, but VSCODE, even in its most vanilla and latest patched version, still has issues on the m1/m2 chips. LItterally, if you want a stable MAC, either build yourself a Hackintosh, use the older Intel-based hardware, or deal with the crashes. Its a point of fact, not a point of "feeling" that the chips are causing all kinds of issues.