Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS Terminal.app does not open when launching an application remotely. #236425

Open
3 tasks done
BDisp opened this issue Jul 11, 2024 · 1 comment · May be fixed by #236426
Open
3 tasks done

macOS Terminal.app does not open when launching an application remotely. #236425

BDisp opened this issue Jul 11, 2024 · 1 comment · May be fixed by #236426
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@BDisp
Copy link

BDisp commented Jul 11, 2024

Is there an existing issue for this bug?

  • I have searched the existing issues

Required Troubleshooting Steps

  • I have followed these troubleshooting steps
  • I have tried both values of the remote.SSH.useLocalServer setting

Connect Locally

It connects successfully

->

I can connect via SSH from a Windows 11 host, I can launch the application with integratedTerminal. I can attach an application running on the remote computer (macOS) to the debugger. I just can't launch an application with externalTerminal.

Sometimes gives this error:

Captura de ecrã 2024-07-11 183931

Sometimes gives this error:

Unable to launch debugger worker process (vsdbg) through the terminal. osascript: /Users/user/.vscode-server/cli/servers/Stable-f1e16e1e6214d7c44d078b1f0607b2388f29d729/server/out/vs/workbench/contrib/externalTerminal/node/TerminalHelper.scpt: No such file or directory

I don't have the externalTerminal folder but only the terminal folder on the remote computer (macos).

Using the vscode terminal I can open Terminal.app with the following command line.

open -n /System/Applications/Utilities/Terminal.app

From what I think it's not a permissions issue.

With vscode installed on the remote computer (macOS) it opens the terminal but as it is installed in a virtual machine it becomes slow, so I prefer to use vscode installed on the host because it runs faster.
The fact that I prefer to use Terminal.app is because the application uses keybindings that conflict with vscode. With the external terminal there is never this conflict.

Expected Behavior

Terminal.app should open if externalTerminal is configured.

Steps To Reproduce

  1. Open vscode on Windows 11 and connect to remote computer running macOS operating system.
  2. Open a folder where you have created a console app in C# where the launch.json configuration has "console": "externalTerminal".
  3. Run the app.
  4. Terminal.app should open on the remote computer.
  5. You will see the errors described above.

Remote-SSH Log

I can connect through SSH. The problem is that the path "/Users/user/.vscode-server/cli/servers/Stable-f1e16e1e6214d7c44d078b1f0607b2388f29d729/server/out/vs/workbench/contrib/externalTerminal/node/TerminalHelper.scpt" does not exist.

Anything else?

Thanks for your help.

@joshspicer
Copy link
Member

@connor4312 I don't think this is a possible workflow, right?

@connor4312 connor4312 transferred this issue from microsoft/vscode-remote-release Dec 18, 2024
@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues and removed ssh labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants