rstolpe
November 18, 2022, 12:59pm
1
Hi,
Is it any documentation regarding how to get it to work at Mac?
rstolpe
November 18, 2022, 4:19pm
2
Has anyone installed powershell pro tools on macOS arm64 and got it working?
rstolpe
November 18, 2022, 9:28pm
3
@adam can it be the same issue that I did race in this thread?
I want to try out PowerShell Tools but I can’t seem to get it working, when I install it on vscode PST is just stuck on “PowerShell pro tools is Connecting…”
I have made sure that I have the PowerShell module 2022.3.0.0 PowerShellProTools installed, not sure if I need it for macOS? The Module? But now it’s installed anyway.
Running macOS 12.3
OS: macOS 12.3
Tool: Visual Studio Code (latest), PowerShell Pro Tools (latest)
Version: latest release
Got this for more than a year and every time I’m trying to get it to work on my Mac it fails.
I did also email with you today on the support case with some findings
rstolpe
November 21, 2022, 5:21pm
4
Got a ticket with the support and I also opened a GitHub issue.
opened 05:05PM - 21 Nov 22 UTC
bug
PowerShell Pro Tools
I have reported this bug with a ticket also but I just want to highlight it here… also if people getting the same issue.
So, when I install vsCode extension of PowerShell Pro Tools it won't start and just loops.
In the Log (Extension Host) I can see the following error:
```
2022-11-21 12:22:07.575 [error] Error: ENOENT: no such file or directory, chmod '/Users/xxx/PowerShellProTools/2022.11.2/osx-arm64/PowerShellProTools.Host'
at Object.chmodSync (node:fs:1830:3)
at PowerShellService.<anonymous> (/Users/xxx/.vscode/extensions/ironmansoftware.powershellprotools-2022.11.2/out/services/powershellservice.js:264:24)
at Generator.next (<anonymous>)
at fulfilled (/Users/xxx/.vscode/extensions/ironmansoftware.powershellprotools-2022.11.2/out/services/powershellservice.js:5:58)
```
When I go to the path ```/Users/xxx/PowerShellProTools/2022.11.2``` it don't contain the folder **osx-arm64** instead it contains the folder **osx**
So if I rename the folder to **osx-arm64** and restart vsCode I get the following error under Log (Extension Host):
```
2022-11-21 12:30:38.685 [error] Error: spawn /Users/xxx/PowerShellProTools/2022.11.2/osx-arm64/PowerShellProTools.Host EACCES
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
```
So @adamdriscoll did ask me to download the osx-arm64 version and manually import it to the path ```/Users/xxx/PowerShellProTools/2022.11.2/osx-arm64``` but that did not help either, when I did that I do get the following error in Log (Extension Host)
```
2022-11-21 14:28:53.465 [error] Error: spawn /Users/xxxx/PowerShellProTools/2022.11.2/osx-arm64/PowerShellProTools.Host EACCES
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
```
But now I can see the following under the OutPut and Powershell Pro Tools:
```
Starting PowerShell Pro Tools host from: /Users/xxxx/PowerShellProTools/2022.11.2/osx-arm64/PowerShellProTools.Host
Process started
```
Before I could not see anything in the OutPut and Powershell Pro Tools tab.
@adamdriscoll do you have some kind of nightly beta or similar of the PowerShell Pro Tools? I badly want it to work on my Mac :)
1 Like
