appium-uiautomator2-driver 4.1.4 → 4.2.0

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+## [4.2.0](https://github.com/appium/appium-uiautomator2-driver/compare/v4.1.5...v4.2.0) (2025-04-08)
+
+### Features
+
+* document the new currentDisplayId setting ([#882](https://github.com/appium/appium-uiautomator2-driver/issues/882)) ([cbb8d93](https://github.com/appium/appium-uiautomator2-driver/commit/cbb8d9305aba36bb5decc03445d596cfb095d6fa))
+
+## [4.1.5](https://github.com/appium/appium-uiautomator2-driver/compare/v4.1.4...v4.1.5) (2025-03-21)
+
+### Miscellaneous Chores
+
+* Bump server version ([#874](https://github.com/appium/appium-uiautomator2-driver/issues/874)) ([b3b0898](https://github.com/appium/appium-uiautomator2-driver/commit/b3b089896e664efa50b0388e44ce1aa0e6af16bd))
+
 ## [4.1.4](https://github.com/appium/appium-uiautomator2-driver/compare/v4.1.3...v4.1.4) (2025-03-20)
 
 ### Bug Fixes

package/README.md

@@ -327,6 +327,7 @@ disableIdLocatorAutocompletion | boolean | According to internal Android standar
 includeExtrasInPageSource | boolean | Whether to include `extras` element attribute in the XML page source result. Then, XPath locator can find the element by the extras. Its value consists of combined [getExtras](https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo#getExtras()) as `keys=value` pair separated by a semicolon (`;`), thus you may need to find the element with partial matching like `contains` e.g. `driver.find_element :xpath, '//*[contains(@extras, "AccessibilityNodeInfo.roleDescription=")]'`. The value could be huge if elements in the XML page source have large `extras`. It could affect the performance of XML page source generation.
 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).**
 
 
 ## Platform-Specific Extensions

package/build/lib/doctor/required-checks.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"required-checks.d.ts","sourceRoot":"","sources":["../../../lib/doctor/required-checks.js"],"names":[],"mappings":"AAEA;;;+BAIq2E,eAAe;;;;EAJ5zE;AACxD;;;+BAGq2E,eAAe;;;;EAHl0E;AAClD,2DAA4D;AAC5D,qDAAsD;uBAL/B,uBAAuB"}
+{"version":3,"file":"required-checks.d.ts","sourceRoot":"","sources":["../../../lib/doctor/required-checks.js"],"names":[],"mappings":"AAEA;;;;;;;EAAwD;AACxD;;;;;;;EAAkD;AAClD,2DAA4D;AAC5D,qDAAsD;uBAL/B,uBAAuB"}