-
Notifications
You must be signed in to change notification settings - Fork 56
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
The binary found in ~/.browserstack is of size 0KB #27
Comments
Are you still facing after this #28 ? |
Yes, as I would rather use the default one rather than a defined path. |
Hey @shanep2300, bs_local.start(bs_local_args, function(error) {
console.log("Error:", error);
}); Also, a 0kb file in that particular path should not be an issue as this module re-downloads the binary if it cannot start the binary / the binary is corrupted. So the 0kb file should be fixed on re-downloading (or cough-up a LocalError object if it fails to do so) |
Hello @vedharish, console.log("Connecting local");
exports.bs_local = new browserstack.Local();
exports.bs_local.start({
'key': exports.config.multiCapabilities['browserstack.key'],
'localIdentifier': exports.config.multiCapabilities['browserstack.localIdentifier']}, function(error) {
if (error) return reject(error);
console.log('Connected. Now testing...');
resolve();
}); This is the error I'm getting:
|
Ashwin, from BrowserStack support, helped me fix the spawn issue. Well half of it. The path to the binary needed the .exe. The other half of the problem still hasn't been fixed. I can't get this to work without the binary path defined. |
Found a better solution for the path.
This will point the path to the working directory instead of the home directory. |
This is after deleting the binary and re-initiating the test script to try and get a fresh binary.
Using version 1.3.0 on Windows 7.
The text was updated successfully, but these errors were encountered: