-
-
Notifications
You must be signed in to change notification settings - Fork 420
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: terminateApp with devicectl for iOS 17 #1997
Conversation
@@ -192,7 +193,7 @@ class IOSDeploy { | |||
} | |||
} | |||
|
|||
async terminateApp(bundleId) { | |||
async terminateApp(bundleId, platformVersion) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say it makes sense to keep platformVersion as IOSDeploy property as it might be useful in other methods as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, that sounds good. let me do it as a follow-up pr (to pr split)
updated ✅ |
## [5.2.1](v5.2.0...v5.2.1) (2023-09-19) ### Bug Fixes * terminateApp with devicectl for iOS 17 ([#1997](#1997)) ([16c7319](16c7319))
🎉 This PR is included in version 5.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Related to appium/appium#18749
This PR kills the process directly against iOS 17 devices via
devicectl
command without appium-ios-device side modifications.terminateApp via XCTest (WDA) works without any issues, but instrument service gets an issue in iOS 17 with current appium-ios-device implementation. This could have small overhead than existing implementation (because of
devicectl
), but should not be a big issue for this usageNote
Maybe we need to build a wrapper module for
devicectl
to use it widely for our use. This PR should refer to it later.