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

[🐛 Bug]: wdio-vscode-service stopped working on Mac M1 #14155

Closed
3 tasks done
bmingles opened this issue Feb 5, 2025 · 3 comments
Closed
3 tasks done

[🐛 Bug]: wdio-vscode-service stopped working on Mac M1 #14155

bmingles opened this issue Feb 5, 2025 · 3 comments
Labels
Bug 🐛 Needs Triaging ⏳ No one has looked into the issue yet

Comments

@bmingles
Copy link

bmingles commented Feb 5, 2025

Have you read the Contributing Guidelines on issues?

OS

M1 Mac
MacOS Sequoia 15.3

WebdriverIO Version

9.7.2

Node.js Version

20.13.1

Mode

WDIO Testrunner

Which capabilities are you using?

{
  browserName: "vscode",
  browserVersion: "stable",
  "wdio:vscodeOptions": {
    // points to directory where extension package.json is located
    extensionPath: __dirname,
    // optional VS Code settings
    workspacePath: path.join(__dirname, "test-ws"),
    userSettings: {
      "editor.fontSize": 14,
    },
  },
},

What happened?

I have been running tests for a vscode extension via wdio v8 for a while on my Mac M1. This week the runner started hanging, and the test instance of VS Code never opens. Output looks like:

[0-0] 2025-02-05T18:11:49.616Z INFO chromedriver: [FAKE VSCode Binary] STDERR:
[0-0] 2025-02-05T18:11:49.616Z INFO chromedriver: DevTools listening on ws://127.0.0.1:50841/devtools/browser/1a6092b0-546a-4e16-a2f1-68bb5cc99baa
[0-0] 2025-02-05T18:11:49.616Z INFO chromedriver:

I upgraded wdio to 9.7.2 to see if it fixed the issue. It now fails with errors:

INFO chromedriver: [FAKE VSCode Binary] STDERR: [main 2025-02-05T18:13:38.912Z] Blocked vscode-file request vscode-file://vscode-app/Users/myuser/my-code/.wdio-vscode-service/vscode-darwin-arm64-1.96.4/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js
[0-1] 2025-02-05T18:13:38.912Z INFO chromedriver:
[0-1] 2025-02-05T18:13:40.525Z ERROR webdriver: WebDriverError: no such window

What is your expected behavior?

Running tests should open an instance of VS Code and run tests from specs.

How to reproduce the bug.

On a Mac M1 running Mac OS Sequoia 15.3

Relevant log output

INFO chromedriver: [FAKE VSCode Binary] STDERR: [main 2025-02-05T18:13:38.912Z] Blocked vscode-file request vscode-file://vscode-app/Users/myuser/my-code/.wdio-vscode-service/vscode-darwin-arm64-1.96.4/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js
[0-1] 2025-02-05T18:13:38.912Z INFO chromedriver:
[0-1] 2025-02-05T18:13:40.525Z ERROR webdriver: WebDriverError: no such window

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues
@bmingles bmingles added Bug 🐛 Needs Triaging ⏳ No one has looked into the issue yet labels Feb 5, 2025
@christian-bromann
Copy link
Member

@bmingles can we raise this issue in the vscode service repo? Thank you!

@bmingles
Copy link
Author

bmingles commented Feb 5, 2025

@bmingles
Copy link
Author

bmingles commented Feb 5, 2025

Ok, I've created webdriverio-community/wdio-vscode-service#141

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐛 Needs Triaging ⏳ No one has looked into the issue yet
Projects
None yet
Development

No branches or pull requests

2 participants