Paul

@nqdrizzt The reason for that is you have added your self to the group "dialoug" not "dialout". Also in your case (on your distro installation) the device file you think...

@PySchilling Does the issue still persists for you with v3.3.2?

Opening the MicroPico vREPL (a custom terminal profile) and type your code or just `.ls` and press enter. Or opening the virtual filesystem/workspace.

Thanks for reporting. > any updates on this matter - seems to be possibly related to https://github.com/paulober/MicroPico/issues/199 ? Maybe. To find out please reproduce the bug and then run following...

If that's the case, this could potential solve the issue: [wrapper_macOS_arm64.zip](https://github.com/paulober/MicroPico/files/14529840/wrapper_macOS_arm64.zip) On macOS arm64 replace the `wrapper_macOS_arm64` folder in `~/.vscode/extensions/paulober.pico-w-go-3.7.5-darwin-arm64/dist/scripts` with the folder in the zip file.

Do you have any error output in the output panel under "Extension Host"?

It does work with the latest VSCode version. This kind of bug seems to be a problem with the extension running on MacOS or a conflicting python installation. But in...

@breezin320 Could it be that you have multiple versions of Python installed on your system?

@nedamaleki The issue seems to be cause by Python 3.9. I fixed this compatibility issue with Patch v3.0.8. Does this solve the extension not activating issue with Python 3.9 and...

@breezin320 The Run button at the right top of the editor is provided by the Python extension and not Pico-W-Go therefore it runs everything locally, that's why it does not...