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

fix: respect executableDir even non-adb environment such as desktop #383

Merged
merged 6 commits into from
Mar 8, 2024

Conversation

KazuCocoa
Copy link
Member

@KazuCocoa KazuCocoa commented Mar 8, 2024

When executableDir is given, it would be nice to respect executableDir rather than forcefully use system's one for non-adb env such as desktop.

Current implementation does not respect given executableDir for non-adb environment. It means automatic detection/download does not work by getCompatibleChromedriver.

@KazuCocoa KazuCocoa changed the title chore: remove unnecessary adb check as no usage chore: respect executableDir even non-adb environment such as desktop Mar 8, 2024
@KazuCocoa KazuCocoa changed the title chore: respect executableDir even non-adb environment such as desktop fix: respect executableDir even non-adb environment such as desktop Mar 8, 2024
@KazuCocoa KazuCocoa marked this pull request as ready for review March 8, 2024 19:45
@KazuCocoa KazuCocoa merged commit 0a3e80e into master Mar 8, 2024
12 checks passed
@KazuCocoa KazuCocoa deleted the remove-unnecessary-adbcheck branch March 8, 2024 21:23
github-actions bot pushed a commit that referenced this pull request Mar 8, 2024
## [5.6.38](v5.6.37...v5.6.38) (2024-03-08)

### Bug Fixes

* respect executableDir even non-adb environment such as desktop ([#383](#383)) ([0a3e80e](0a3e80e))
Copy link
Contributor

github-actions bot commented Mar 8, 2024

🎉 This PR is included in version 5.6.38 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants