android uiautomator enableMultiWindows bug?

[TesterWa]

set enableMultiWindows：true，getPagesource Only return root，use adb shell dump Return to page source normally,Whether it is a bug of appium. test application Wechat!

[KazuCocoa]

Is it native elements?
The enableMultiWindows returns views from as

appium-uiautomator2-server/app/src/main/java/io/appium/uiautomator2/utils/AXWindowHelpers.java

Lines 86 to 98 in 0111c09

	private static AccessibilityNodeInfo[] getWindowRoots() {
	List<AccessibilityNodeInfo> result = new ArrayList<>();
	List<AccessibilityWindowInfo> windows = CustomUiDevice.getInstance()
	.getUiAutomation()
	.getWindows();
	for (AccessibilityWindowInfo window : windows) {
	AccessibilityNodeInfo root = window.getRoot();
	if (root == null) {
	Logger.info(String.format("Skipping null root node for window: %s", window.toString()));
	continue;
	}
	result.add(root);
	}

, so it returns only root, then the Android's AccessibilityNodeInfo also can show them.

[TesterWa]

是原生元素吗？ 来自 as的enableMultiWindows返回视图

appium-uiautomator2-server/app/src/main/java/io/appium/uiautomator2/utils/AXWindowHelpers.java

Lines 86 to 98 in 0111c09

	private static AccessibilityNodeInfo[] getWindowRoots() {
	List<AccessibilityNodeInfo> result = new ArrayList<>();
	List<AccessibilityWindowInfo> windows = CustomUiDevice.getInstance()
	.getUiAutomation()
	.getWindows();
	for (AccessibilityWindowInfo window : windows) {
	AccessibilityNodeInfo root = window.getRoot();
	if (root == null) {
	Logger.info(String.format("Skipping null root node for window: %s", window.toString()));
	continue;
	}
	result.add(root);
	}

, 所以它只返回 root，那么 Android 的 AccessibilityNodeInfo 也可以显示它们。

Yes ! Native element get roots It should be normal, but is there any problem with appium-ui2-server in generating the page source? Although the page source generation failed, you can get elements with Android native uiselector, provided that you call driver.source before calling findelement to empty windows in ui2-server. The cache. In order to return the element normally.

[KazuCocoa]

Generally the result by Appium depends on https://developer.android.com/reference/android/app/UiAutomation#getWindows() and https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo. A potential reason was they did not retuirn entire page source.

allowInvisibleElements and ignoreUnimportantViews also could help https://github.com/appium/appium-uiautomator2-driver/#elements-cannot-be-found