Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element Not identified in Real Device(Windows 10) #39

Open
SivagamiSakthivel opened this issue Dec 11, 2017 · 2 comments
Open

Element Not identified in Real Device(Windows 10) #39

SivagamiSakthivel opened this issue Dec 11, 2017 · 2 comments

Comments

@SivagamiSakthivel
Copy link

SivagamiSakthivel commented Dec 11, 2017

I use Winium CodedUI to launch Windows 10 OS Phone(Real Device with RedStone1 Anniversary update by Windows).When i tried to find an element in Windows Phone,i get an error message as
"[DEBUG] Sending ping request to Test Server
[DEBUG] RESPONSE:OK: {"sessionId":"XXXXX","status":33,"value":"Could not connect to Test Server"}
16:" and below error logs,
image

Any help on this?

@NickAb
Copy link
Contributor

NickAb commented Dec 12, 2017

Please try building the driver from the latest master.
Assuming you are using latest selenium binding, I think 3bf2bca might fix this for you.

@didi2391
Copy link

Hi Nick,

We have tried with the above mentioned comments and still we are facing blocker
Unable to run using the Emulator itself
Please find attached driver logs for the same
DriverLogs.txt

Help us in resolving this issue

If it works on Emulator we can try the same solution onto the real device as well

Also , We have built the driver from latest mater version using Visual Studio 2015

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants