appium-uiautomator2-driver 5.0.4 → 5.0.6

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+## [5.0.6](https://github.com/appium/appium-uiautomator2-driver/compare/v5.0.5...v5.0.6) (2025-10-22)
+
+### Miscellaneous Chores
+
+* Bump android driver ([7730ccb](https://github.com/appium/appium-uiautomator2-driver/commit/7730ccb9970260bc217b8d1f10e1ee9e818e6941))
+
+## [5.0.5](https://github.com/appium/appium-uiautomator2-driver/compare/v5.0.4...v5.0.5) (2025-10-08)
+
+### Miscellaneous Chores
+
+* Bump android driver ([885b8b6](https://github.com/appium/appium-uiautomator2-driver/commit/885b8b6191863a4536a511efc662a36486614a76))
+
 ## [5.0.4](https://github.com/appium/appium-uiautomator2-driver/compare/v5.0.3...v5.0.4) (2025-10-03)
 
 ### Miscellaneous Chores

package/README.md

@@ -329,6 +329,7 @@ includeExtrasInPageSource | boolean | Whether to include `extras` element attrib
 includeA11yActionsInPageSource | boolean | Whether to include `actions` element attribute in the XML page source result. Its value consists of names of available accessibility actions from [getActionList](https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#getActionList()), separated by a comma. The value could be huge if elements in the XML page source have a lot of actions and could affect the performance of XML page source generation.
 snapshotMaxDepth | int | The number of maximum depth for the source tree snapshot. The default value is `70`. This number should be in range [1, 500]. A part of the elements source tree might be lost if the value is too low. Also, StackOverflowError might be caused if the value is too high (Issues [12545](https://github.com/appium/appium/issues/12545), [12892](https://github.com/appium/appium/issues/12892)). The available driver version is `2.27.0` or higher.
 currentDisplayId | int | The id of the display that should be used when finding elements, taking screenshots, etc. It can be found in the output of `adb shell dumpsys display` (search for `mDisplayId`). The default value is [Display.DEFAULT_DISPLAY](https://developer.android.com/reference/android/view/Display#DEFAULT_DISPLAY). **Please note that it is different from the physical display id, reported by `adb shell dumpsys SurfaceFlinger --display-id`**. **Additionally, please note that `-android uiautomator` (e.g., `UiSelector`) doesn't work predictably with multiple displays, as this is an Android limitation.** **Multi-display support is only available since Android R (30 API level).**
+alwaysTraversableViewClasses | string | Allows to continue the tree traversal for user defined classes even though the node itself is invisible. The default logic for the UI tree traversal (controlled by the `allowInvisibleElements` setting) is to stop recursing when an invisible node is found. However, with certain Jetpack Compose classes (e.g. androidx.compose.ui.viewinterop.ViewFactoryHolder), it is possible that invisible parent nodes have visible child nodes.  See [Google issue \#354958193](https://issuetracker.google.com/issues/354958193) and [UIA2 server issue \#709](https://github.com/appium/appium-uiautomator2-server/issues/709) for more details. This setting only affects the XPath lookup and the page source buildup. You can provide a comma separated list of glob patterns, that will be used as an exemption list: `androidx.compose.ui.viewinterop.*,android.widget.ImageButton`.
 
 
 ## Platform-Specific Extensions