Closed FreeBLD closed 1 year ago
Thanks for reporting the problem. This was not a problem with Wallaby, but instead a breaking change in the latest version of Chrome (v.110.0.5481.178
) for the chrome remote debugger communication protocol that is required by Wallaby.
This has been fixed in the latest version of Wallaby, v1.0.1394
. Please update to the latest version, it will fix your problem.
Alternatively, you may try downloading and explicitly specifying an older version of Chrome for Wallaby to use (set the env.runner
configuration setting as described in our docs).
Hello @smcenlly,
Could we have an estimation for when this will be available for the VS Code plugin?
When I do "Force Core Update" I get v1.0.1360
, it looks like it's not very close to v1.0.1394
.
I guess this could be because I have a license that has expired recently, but does this mean I will not get the fix unless I renew the license?
@Arthoo
I guess this could be because I have a license that has expired recently, but does this mean I will not get the fix unless I renew the license?
Yes, your license has expired and the support for the latest chrome remote debugger communication protocol has been added in v1.0.1394
that is not covered by your license. To get the latest version with added support, you'll need to renew your license.
Alternatively, you may try downloading and explicitly specifying an older version of Chrome for Wallaby to use (set the env.runner
configuration setting as described in our docs).
Thanks for the support 🙏
Issue description or question
Upon starting wallaby.js the engine throws the error bellow in the Wallaby.js Tests output window.
[Error] Test run failure: Sandbox load failed, status: failed: Using unsafe HTTP verb GET to invoke /json/new. This action supports only PUT verb.
I tried googling this problem and found something similar relatated to wallaby.js here https://github.com/wallabyjs/public/issues/2881. I had my environment variable CHROME_BIN set to edge so I replaced it with the chrome one, but it did not solve the issue.
I tried also to clear the wallaby cache as well as removing the extension and deleting the files associated with the extension and re-installing it but with no luck.
There were other projects that stumbled across this issue, related to chromium enforcing more stringent rules against XSS. Like in this one here https://github.com/GoogleChrome/lighthouse/pull/14063
Thanks for your support, Cristian
Wallaby diagnostics report