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

HideKeyboard Crashes Appium #73

Closed
KDeeds opened this issue Jan 8, 2015 · 2 comments
Closed

HideKeyboard Crashes Appium #73

KDeeds opened this issue Jan 8, 2015 · 2 comments

Comments

@KDeeds
Copy link

KDeeds commented Jan 8, 2015

I recently just upgraded to 1.2.0.7 and updated methods and interfaces in my code. Most things seem to work the same except HideKeyboard() crashes Appium whenever I try to use it. I noticed its trying to send a symbol for hiding the keyboard.

info: [debug] Socket data received (25 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":""}
info: [debug] Responding to client with success: {"status":0,"value":"","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}
info: <-- POST /wd/hub/session/edafd8d2-5357-499b-b33e-82b8bf3c9585/element/28/value 200 3676.050 ms - 74 {"status":0,"value":"","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}
info: --> GET /wd/hub/session/edafd8d2-5357-499b-b33e-82b8bf3c9585/element/28/name {}
info: [debug] Pushing command to appium work queue: "au.getElement('28').type()"
info: [debug] Sending command to instruments: au.getElement('28').type()
info: [debug] [INST] 2015-01-08 15:48:04 +0000 Debug: evaluation finished
info: [debug] [INST] 2015-01-08 15:48:04 +0000 Debug: responding with:
info: [debug] [INST] 2015-01-08 15:48:04 +0000 Debug: Running system command #32: /usr/local/bin/node /usr/local/lib/node_modules/appium/node_modules/appium-uiauto/bin/command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":""}...
info: [debug] [INST] 2015-01-08 15:48:05 +0000 Debug: Got new command 32 from instruments: au.getElement('28').type()
info: [debug] Socket data received (37 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":"UIASearchBar"}
info: [debug] Responding to client with success: {"status":0,"value":"UIASearchBar","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}
info: <-- GET /wd/hub/session/edafd8d2-5357-499b-b33e-82b8bf3c9585/element/28/name 200 968.173 ms - 86 {"status":0,"value":"UIASearchBar","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}
info: --> POST /wd/hub/session/edafd8d2-5357-499b-b33e-82b8bf3c9585/element/28/value {"value":[""],"keysToSend":[""]}
info: [debug] Pushing command to appium work queue: "au.getElement('28').setValueByType('')"
info: [debug] Sending command to instruments: au.getElement('28').setValueByType('')
info: [debug] [INST] 2015-01-08 15:48:05 +0000 Debug: evaluating au.getElement('28').type()
info: [debug] [INST] 2015-01-08 15:48:05 +0000 Debug: evaluation finished
info: [debug] [INST] 2015-01-08 15:48:05 +0000 Debug: responding with:
info: [debug] [INST] 2015-01-08 15:48:05 +0000 Debug: Running system command #33: /usr/local/bin/node /usr/local/lib/node_modules/appium/node_modules/appium-uiauto/bin/command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":"UIASearchBar"}...
info: [debug] [INST] 2015-01-08 15:48:06 +0000 Debug: Got new command 33 from instruments: au.getElement('28').setValueByType('')
info: [debug] [INST] 2015-01-08 15:48:06 +0000 Debug: evaluating au.getElement('28').setValueByType('')
info: [debug] Socket data received (25 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":""}
info: [debug] Responding to client with success: {"status":0,"value":"","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}
info: <-- POST /wd/hub/session/edafd8d2-5357-499b-b33e-82b8bf3c9585/element/28/value 200 1501.082 ms - 74 {"status":0,"value":"","sessionId":"edafd8d2-5357-499b-b33e-82b8bf3c9585"}

@TikhomirovSergey
Copy link
Contributor

It seems I found the rootcause. The fix is here: #75
Here are some new tests.

@TikhomirovSergey
Copy link
Contributor

The fix will be published as soon as possible.

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

2 participants