enable "select target platform" for remote ssh sessions

[RDMurray]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I want to be able to use VSCode on windows to develop for iOS via a remote ssh session. Currently select target platform doesn't work.

Describe the solution you'd like
A clear and concise description of what you want to happen.

The select target platform command to work for remote sessions when the remote is macOS.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I tried live share, but don't get any language services. It looks for a swift toolchain on the client instead.

Additional context
Add any other context or screenshots about the feature request here.

The reason I would like this feature is that I am blind and use a screen reader. While macOS has voiceover which does work with VSCode, it is much better on Windows with the NVDA screen reader.

[matthewbastien]

@RDMurray can you confirm whether or not this is still happening for you? I was able to reproduce this issue a while ago, but with the latest version of the Swift extension (v2.2.0) it seems to be fixed.

[RDMurray]

strangely With 2.2.0 I don't see the "select target platform" command, even when running VSCode directly on the Mac. I tried creating a new blank profile with just the swift extension and it still doesn't work.

[RDMurray]

I didn't realise that it now requires Swift 6.1. After updating Xcode, the command is available when running locally. It still doesn't work from a remote ssh session on a Windows client.

The LSP does work correctly in a remote ssh session if I use the local VSCode to select the target platform and save it in the workspace settings first. It's just the command that doesn't appear in the command pallet.

[matthewbastien]

Okay I can reproduce this again. I was SSHing from macOS -> Windows instead of the other way around. Sorry about that. Investigating further...

[matthewbastien]

Fixed by #1567. Going to try to put out a pre-release tomorrow that contains the fix.