Removing single quotes from logfile on WIN OS #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the start command is run on Windows, the single quotes appear as part of the logfile path or name.
We discovered this when we tried to set the log file argument to
"logfile" => "browserstack.log"
and found that the single quotes appeared as part of the file name.Trying to set a log file to a different folder path (i.e.
"logfile" => "logs/browserstack.log"
) would cause single quotes to appear in the path itself (which caused BrowserStackLocal.exe to fail all together).Removing the single quotes from the command string on Windows resolves the issue, but it does mean you can't use spaces in your log file path.