Winium doesn't work properly on Windows 10

[RomanIovlev]

For example this simple Windows Calculator test doesn't work on Windows 10 See example here: https://github.com/Supreme85/jdi-desktop-example/blob/master/src/test/java/org/mytests/tests/example/PureWinium.java e.g. winiumTest1()

First click on 7 done correctly but all other clicks misplaced on similar position right-bottom Misplacement depends on left-top app corner position

[vinuthamikkilineni]

Hey Even i was facing the same problem .you have change the screen scaling to 100% then only it works.

[RomanIovlev]

How I can do this programmatically? Can you provide some example? (better in example above) Thanks!

[Jyothish77]

I am facing similar issue. The screen scaling is 100% and the control is identified using the AutomationID for the WPF application. But while running application the click is not happening on the identified control.

[Jyothish77]

The clicking is working as expected for me after updating the Windows10 OS Version from 1607 to 1709

[vinuthamikkilineni]

I have fixed this issue in Winium Crutius code in my local machine. i need to raise a pull request for the same. Now it works on all VMs ,Windows machine without changing your resolution

[vinuthamikkilineni]

I have raised pull request. i will update this thread as soon as it gets merged

[roopaturlapati]

waiting for your reply @vinuthamikkilineni ., please update .

[vinuthamikkilineni]

i have raised the pull request on winium crutius. its says still pending.

[vinuthamikkilineni]

https://github.com/2gis/Winium.Cruciatus/pull/75 is the link for pull request.

[vinuthamikkilineni]

you can pull the code from here https://github.com/vinuthamikkilineni/Winium.Cruciatus. build WiniumCrutius and add it as external reference for Winium desktop driver. It works

[ChaoLiou]

@vinuthamikkilineni still same ;-( Do I need to change resolution settings with your version?

[vinuthamikkilineni]

@ChaoLiou , Nope There is no need of changing resolution settings. Have you build Winium Desktop driver with new Winium Cruciatus.

[vinuthamikkilineni]

I can upload the Winium.Desktop.Driver.exe with all those changes

[Schroet]

Hey guys! Are there any changes here?

[ghost]

@vinuthamikkilineni Please do so if you're able to <3

[vinuthamikkilineni]

hey Its working for me. I am using it for our UI Automation

On Sat, Jul 14, 2018 at 1:22 AM, Z [email protected] wrote:

@vinuthamikkilineni https://github.com/vinuthamikkilineni Please do so if you're able to <3

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/2gis/Winium.Desktop/issues/213#issuecomment-404936591, or mute the thread https://github.com/notifications/unsubscribe-auth/AJSpNNwHfoNMjtdyr2goVJLDS4or5GPVks5uGPqVgaJpZM4Rpx-E .

[bhaskaralluri]

@vinuthamikkilineni : Could you please upload the exe file with fix ? I am using Windows 10, Even though i gave everything correct ( automation id's for the text boxes ), it is not clicking on it to type, but i noticed mouse movement on the screen do not know why. Hopefully all these are related to scaling issues and your .exe driver will fix it. thank you.

[ankurb9]

I faced same issue... How I resolved this is I used below lines to start the service .

WiniumDriverService service = new WiniumDriverService.Builder() .usingDriverExecutable(new File(System.getProperty("user.dir")+"\Drivers\Winium.Desktop.Driver-1.6.exe")) .usingPort(9999) .withVerbose(true) .withSilent(false) .buildDesktopService(); service.start(); WiniumDriver driver = new WiniumDriver(service,opt);

After that You need to stop and start the service for each command. it worked like charm for me.

Remember you need to start only one service at a time otherwise you will get socketexception. service.start(); service.start(); is incorrect.

service.start(); service.stop() service.start(); this is correct

e.g." you have already started the service post initialisation so no need to start again driver.findelement(by.id(**)).click(); service.strop();

service.start(); driver.findelement(by.id(**)).click(); service.stop();

[carlosEnriqueGosalbez]

Hello, when I try to automate the calculator, the first click does it right but the rest clicks randomly. Someone has the solution. I have the resolution 100% connected with VGA. Thanks

[vinuthamikkilineni]

I faced same issue... How I resolved this is I used below lines to start the service .

WiniumDriverService service = new WiniumDriverService.Builder() .usingDriverExecutable(new File(System.getProperty("user.dir")+"\Drivers\Winium.Desktop.Driver-1.6.exe")) .usingPort(9999) .withVerbose(true) .withSilent(false) .buildDesktopService(); service.start(); WiniumDriver driver = new WiniumDriver(service,opt);

After that You need to stop and start the service for each command. it worked like charm for me.

Remember you need to start only one service at a time otherwise you will get socketexception. service.start(); service.start(); is incorrect.

service.start(); service.stop() service.start(); this is correct

e.g." you have already started the service post initialisation so no need to start again driver.findelement(by.id(**)).click(); service.strop();

service.start(); driver.findelement(by.id(**)).click(); service.stop();

@vinuthamikkilineni : Could you please upload the exe file with fix ? I am using Windows 10, Even though i gave everything correct ( automation id's for the text boxes ), it is not clicking on it to type, but i noticed mouse movement on the screen do not know why. Hopefully all these are related to scaling issues and your .exe driver will fix it. thank you.

I am attaching a zip file built locally. Please note my pull request is not approved by Winium team . so It cannot be actual released driver

[vinuthamikkilineni]

Winium.Desktop.Driver.exe.zip

[vinuthamikkilineni]

I faced same issue... How I resolved this is I used below lines to start the service .

WiniumDriverService service = new WiniumDriverService.Builder() .usingDriverExecutable(new File(System.getProperty("user.dir")+"\Drivers\Winium.Desktop.Driver-1.6.exe")) .usingPort(9999) .withVerbose(true) .withSilent(false) .buildDesktopService(); service.start(); WiniumDriver driver = new WiniumDriver(service,opt);

After that You need to stop and start the service for each command. it worked like charm for me.

Remember you need to start only one service at a time otherwise you will get socketexception. service.start(); service.start(); is incorrect.

service.start(); service.stop() service.start(); this is correct

e.g." you have already started the service post initialisation so no need to start again driver.findelement(by.id(**)).click(); service.strop();

service.start(); driver.findelement(by.id(**)).click(); service.stop();

Starting the service and stoping the service for every click means Starting a new connection for every operation that will be heavy on process. It will slowdown your overall performance

[Devil1061]

While trying to launch Winium.driver.exe socket exception has occurred. Below is the detailed message.

Starting Windows Desktop Driver on port 9999

15:19:56 [FATAL] Failed to start driver: System.Net.Sockets.SocketException (0x80004005): An attempt was made to access a socket in a way forbidden by its access permissions at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at Winium.Desktop.Driver.Listener.StartListening() at Winium.Desktop.Driver.Program.Main(String[] args)

Unhandled Exception: System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at Winium.Desktop.Driver.Listener.StartListening() at Winium.Desktop.Driver.Program.Main(String[] args)

I am using windows 10 OS. It is just working fine in the system which is running on Windows 7.

Can anyone suggest me to overcome the issue I am facing?

[vinuthamikkilineni]

Its because port 9999 is being used by another process

[Devil1061]

Thanks @vinuthamikkilineni, tried running it in different port and it worked.

[Shubham12Baid]

Winium.Desktop.Driver.exe.zip

Hi @vinuthamikkilineni I tried using this version of the driver to automate a custom application. However this driver is still giving the same issue as the previous one. It is still identifying and clicking a distance in the right down direction away from the actual position of the element. This driver along with the winium driver from the official site both work fine when zoom setting is set to 150% at 1920x1080 resolution. Yeah its not working for me at 100 % zoom. if u have any suggestions to correct this from the code itself insteadd of manually changing the zoom setting every time, pls help

[v3g3t4x]

Same issue. Don't works... p.s.: Winium latest commit was 3 years ago. The project is dead?

[vinuthamikkilineni]

https://github.com/2gis/Winium.Cruciatus/pull/75 here is my pull request link where I made changes. You can take look and build it locally

[vinuthamikkilineni]

Sorry I was busy I ll check it on my local and update if I added wrong build

[MumtazRashid]

I am using winium of version 0.1.0-1, My test cases are failing for desktop application if screen resolution get changed and also if application get minimized, Is there any way around we can handle such cases ?