-
-
Notifications
You must be signed in to change notification settings - Fork 33
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: Only try to select Safari if it is enabled for automation #404
Conversation
## [12.1.1](v12.1.0...v12.1.1) (2024-08-11) ### Bug Fixes * Only try to select Safari if it is enabled for automation ([#404](#404)) ([4621589](4621589))
@KazuCocoa Do you think it makes sense to enable this condition for any web views or it is only applicable to Safari only? |
🎉 This issue has been resolved in version 12.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Let me check a bit carefully with some combinations. I think the true/false conditions themselves should be the same for both Safari/WebView, but I need to double check the Ui Automation and the WebInspector config in the settings app. UI Automation in Safari settings may not affect the remote debugger (WebInspector) usage but Web Inspector affects it. |
Just a note: as https://github.com/mykola-mokhnach/appium-remote-debugger/blob/e959dbb66aed40a97955b241227acf4019a6a6f9/lib/utils.js#L66-L67, we have a case isAutomationEnable is configured as "Unknown". It is a valid value for automation via Web Inspector. |
Another note for a webview app (uikitcatalog):
So, based on a couple of combinations, I think no much diff between Safari and WebView app in terms of properties like |
Safari does not return any pages if it is not available for automation