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.

Sign up for GitHub

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

docs: address com.apple.ContactsUI.LimitedAccessPromptView in troubleshooting #2474

Merged
merged 3 commits into from
Sep 19, 2024
+19 −0
Merged

docs: address com.apple.ContactsUI.LimitedAccessPromptView in troubleshooting #2474

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c3000d8
docs: address com.apple.ContactsUI.LimitedAccessPromptView in trouble…
KazuCocoa Sep 19, 2024
3aafc62
Update troubleshooting.md
KazuCocoa Sep 19, 2024
31d7e7f
Update troubleshooting.md
KazuCocoa Sep 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/guides/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,25 @@ XCUITest driver offers a couple of approaches to handle them:

[`mobile: activeAppInfo`](../reference/execute-methods.md#mobile-activateappinfo) helps to understand what application (bundleId) is considered as active for the XCUITest driver.

## Interact with dialogs managed by `com.apple.ContactsUI.LimitedAccessPromptView`

iOS 18 introduced a new process named `com.apple.ContactsUI.LimitedAccessPromptView`. See [this issue](https://github.com/appium/appium/issues/20591) for more details.
As of XCUITest driver v7.26.4, the only workaround to interact with views available through the process is the below method:

- `defaultActiveApplication` setting in [Settings](../reference/settings.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does activateApp not help in this case?

Copy link
Member Author

@KazuCocoa KazuCocoa Sep 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested. It looks like no. Activating com.apple.ContactsUI.LimitedAccessPromptView brought the bundle id to the front or springboard?, then the running app went to background. It caused home screen only view. This new view was maybe running over the app under test's GUI but not remains on the home screen like system level dialog.

- e.g. With the [Appium Ruby client](https://github.com/appium/ruby_lib_core)
```ruby
# Interacting with the test target
driver.settings.update({defaultActiveApplication: "com.apple.ContactsUI.LimitedAccessPromptView"})
# to accept the alert
driver.find_element("accessibility_id", "Select Contacts").click
driver.settings.update({defaultActiveApplication: "auto"})
# keep interacting with the test target
```

The `com.apple.ContactsUI.LimitedAccessPromptView` process can get elements available through `com.apple.springboard`, such as several system permission dialogs.
iOS 18+ devices may be possible to use `com.apple.ContactsUI.LimitedAccessPromptView` to interact with elements managed either by `com.apple.ContactsUI.LimitedAccessPromptView` or `com.apple.springboard`.

## Leftover Application Data on Real Devices

There might be a situation where application data is present on the real device, even if the
Expand Down
Loading