Upgrade androidx.test.uiautomator:uiautomator to 2.3.0 to fix issue #398

[xiaoPierre]

Hello,

I ran into the same issue as #398, and I see that the issue submitted to google has been resolved in version 2.3.0 (here's the release notes).

Could we upgrade androidx.test.uiautomator:uiautomator to 2.3.0 to fix this long-lasting issue ? (It seems that write permission is not open for the repository..) Thanks in advance !

cc @mykola-mokhnach @KazuCocoa as you followed similar issues before.

[update by KazuCocoa]
Moved to appium/appium#19597

[mykola-mokhnach]

feel free to open a PR. you need to fork the current repository in order to do that.

[mykola-mokhnach]

Also it's an alpha version. Do you think it is a good idea to include it into the release before it stabilizes?

[xiaoPierre]

Oh indeed it's still alpha01, probably it's better to wait for official stabilised release of 2.3.0 after several months, but I'll try and test if the fix works in a separate fork.

(we're still using appium 1 so I hope it would easy to upgrade this library in appium 1 in our fork😃)

[xiaoPierre]

For info I just validated the fix with the new 2.3.0-alpha01 version with a local appium build, the buttons at the bottom of screen now have correct size. (screenshot taken from appium inspector)

Before the fix :

After the fix :

Note : I had a small issue in code when I do the upgrade, and I opened an issue here #491

[Comeodore]

@KazuCocoa @xiaoPierre Any updates with it? Maybe we can upgrade to 2.3.0 beta?

@xiaoPierre mb can u share how u install locally uiautomator 2.3.0 alpha/beta?
Can i use this with actual appium-uiautomator-server?

[KazuCocoa]

It looks like the lib changed to beta recently https://developer.android.com/jetpack/androidx/releases/test-uiautomator

[Comeodore]

It looks like the lib changed to beta recently https://developer.android.com/jetpack/androidx/releases/test-uiautomator

Can u update lib in project to 2.3.0 beta?

[mykola-mokhnach]

Lets create a PR and see how the CI results look like with this beta

[KazuCocoa]

Basically, we've been waiting for the stable version release.

You can manually modify this branch directly and create the server as https://github.com/appium/appium-uiautomator2-server?tab=readme-ov-file#building-project . Then once you replace existing apk in

appium-uiautomator2-server/index.js

Line 4 in 50066df

const SERVER_APK_PATH = path.resolve(__dirname, 'apks', `appium-uiautomator2-server-v${version}.apk`);

with the buit apk, the new apk will be picked up.

[Comeodore]

@KazuCocoa @mykola-mokhnach UiAutomator devs depredecate getDefaultDisplay method
Now this is getDisplay(int), can u help me with changing it for my local using?
https://developer.android.com/reference/android/hardware/display/DisplayManager#getDisplay(int)

[KazuCocoa]

Do you mean https://developer.android.com/reference/android/view/WindowManager#getDefaultDisplay() ?

This method was deprecated in API level 30.
Use Context#getDisplay() instead.

https://developer.android.com/reference/android/content/Context#getDisplay()

appium-uiautomator2-server/app/src/main/java/io/appium/uiautomator2/core/UiAutomatorBridge.java

Line 57 in 1a1d473

return (Display) invoke(getMethod(UiDevice.class, "getDefaultDisplay"), Device.getUiDevice());

Updated
#585 ?

[Comeodore]

@KazuCocoa
With ur last changes on 2.3.0-beta01 version of uiautomator

[KazuCocoa]

Perhaps #585 change helps. We haven't verified the latest deps version, so possibly the version has compatibility issues.
Please report such new issues with newer dependencies we should update in https://github.com/appium/appium 's bug template.

[KazuCocoa]

For your case, it looks like the latest 2.3.0-beta01 package dropped the getDefaultDisplay, so all OS versions should follow #585 , thus it is a breaking change in uia 2.3.0 beta01 since their alpha.

[KazuCocoa]

#588 is a fix for the beta01

[Comeodore]

@KazuCocoa Thanks, its working, but now when i trying to click on element, has trouble like this

E       selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Cannot create UiObject2 instance with 'null' selector
E       Stacktrace:
E       io.appium.uiautomator2.common.exceptions.UiAutomator2Exception: Cannot create UiObject2 instance with 'null' selector

Any thoughts?

[KazuCocoa]

No, just we need to test well and fix them.
Early alpha maybe did not have such issues, so probably you could use early alpha version.

[Comeodore]

@KazuCocoa The same trouble on 2.3.0-alpha01

[KazuCocoa]

Then we should test the library carefully and update code. I guess we should update the base sdk version first, and wait for upcoming beta to see if it is intended changes in the lib or possible issue in the version.

[Comeodore]

@KazuCocoa Okay, please keep me posted, because fixing the screen size is very important for me (and judging by the many questions on various resources, not only for me)

[KazuCocoa]

Sure, then, please create a new issue in the main appium repository so that we can track issues easier for future investigation.

[KazuCocoa]

appium/appium#19597 will be the primary (instead of this issue) place to link GitHub issues, but as #490 (comment), it would be helpful to create separate issue for different behavior. Then I'll keep linking them to the primary issue'