Expose AutomationId as resource-id for Android automation - #21780
Merged
MrJul merged 1 commit intoJul 15, 2026
Conversation
|
You can test this PR using the following package version. |
MrJul
pushed a commit
that referenced
this pull request
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does the pull request do?
Adds uiautomator visibility to
AutomationProperties.AutomationIdto Android.What is the current behavior?
Android automation tree does not have the automation id available.
What is the updated/expected behavior with this PR?
Tested with ControlCatalog.Android on a physical device with only the XAML changes below. When using automation properties such as:
resource-idis now populated (previously empty) when dumping the automation tree with:adb exec-out uiautomator dump /dev/ttyHow was the solution implemented (if it's not obvious)?
Assigns
AutomationProperties.AutomationIdtoAccessibilityNodeInfoCompat.ViewIdResourceNameChecklist
Breaking changes
None expected. Didn't notice any restrictions on string length or character set.
Obsoletions / Deprecations
None
Fixed issues
None
Background
We're evaluating using Maestro for Android end-to-end testing on physical devices. This works, but matching based on
textorcontent-descis not ideal.iOS, too, when accessibility is implemented there.