You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using electron: 11.0.0, spectron: 13.0.0 to run the test demo of electron,
javascript error: javascript error: Cannot convert undefined or null to object
(Session info: chrome=87.0.4280.60)
at Object.getErrorFromResponseBody (node_modules\webdriver\build\utils.js:94:12)
at WebDriverRequest._request (node_modules\webdriver\build\request.js:134:31)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Browser.wrapCommandFn (node_modules@wdio\utils\build\shim.js:63:29)
at async Browser.wrapCommandFn (node_modules@wdio\utils\build\shim.js:63:29)
The text was updated successfully, but these errors were encountered:
I'm having the exact same issue (down to the stack trace line / character numbers).
If this is relevant, I started from the Electron Vue scaffolding and updated all of the packages.
At this point, the dev process is rather opaque due to the complicated pipeline - Webpack, TypeScript, Babel, etc.
Can anyone recommend any way to get further visibility into this issue? @yoresu did you use the same scaffolding?
I see #812 shows similar symptoms, but in my case I don't see any output in the Electron windows, just an error message in the console where I start the spectron task.
I am using electron: 11.0.0, spectron: 13.0.0 to run the test demo of electron,
javascript error: javascript error: Cannot convert undefined or null to object
(Session info: chrome=87.0.4280.60)
at Object.getErrorFromResponseBody (node_modules\webdriver\build\utils.js:94:12)
at WebDriverRequest._request (node_modules\webdriver\build\request.js:134:31)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Browser.wrapCommandFn (node_modules@wdio\utils\build\shim.js:63:29)
at async Browser.wrapCommandFn (node_modules@wdio\utils\build\shim.js:63:29)
The text was updated successfully, but these errors were encountered: