question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Desired Capability "connectHardwareKeyboard" not work

See original GitHub issue

The problem

Briefly describe the issue you are experiencing (or the feature you want to see added to Appium). Tell us what you were trying to do and what happened instead. Remember, this is not a place to ask questions. For that, go to http://discuss.appium.io!

Environment

  • Appium version (or git revision) that exhibits the issue: 1.8.1
  • Last Appium version that did not exhibit the issue (if applicable): 1.7.2
  • Desktop OS/version used to run Appium: macOS 10.13.5
  • Node.js version (unless using Appium.app|exe): 10.6.0
  • Mobile platform/version under test: IOS 10.3.1
  • Real device or emulator/simulator: simulator
  • Appium CLI or Appium.app|exe: tested with appium cli and appium desktop 1.6.2

Details

send_keys not work (see logs). “connectHardwareKeyboard”: “False” - not work There is only one way to fix send_keys: uncheck in handly in Simulator -> Hardware -> Keyboard -> Connect Hardware Keyboard But I think “connectHardwareKeyboard”: “False” must work too.

Link to Appium logs

https://gist.github.com/romansvesh/af466277f531715e8628dadf05c2ae61

Got response with status 200: {"value":"Error Domain=com.facebook.WebDriverAgent Code=1 \"Keyboard is not present\" UserInfo={NSLocalizedDescription=Keyboard is not present}","sessionId":"44EE4BEB-E7FD-475A-9F70-6305DB7067BB","status":13}

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:18 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
mykola-mokhnachcommented, Jul 5, 2018

This stopped working since recent xCode releases. Simulator simply ignores the changed setting from its plist file and applies the default one each time after restart. Closed as third party issue.

1reaction
KazuCocoacommented, Aug 19, 2021

It seems ok for me with your concrete use case. Feel free to create a pr to accept an environment variable, too. We’re happy to review it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

ConnectHardwareKeyword not working - Issues/Bugs
I searched on Internet and found that it can be achieved using ConnectHardwareKeyboard desired capability but it is not working.
Read more >
appium-xcuitest-driver - npm
The capability must be of a string type. appium:connectHardwareKeyboard, Set this option to true in order to enable hardware keyboard in ...
Read more >
desired capabilities not recognized by appium - Stack Overflow
Please change capabilities.setCapability(MobileCapabilityType.VERSION, "4.4.2");. to capabilities.setCapability(MobileCapabilityType.
Read more >
Capabilities for running mobile app tests on BrowserStack
Default & BrowserStack specific capabilities for App Automate, to run Appium ... This feature is not supported on the following devices: ["Oppo Reno...
Read more >
appium/appium - Gitter
Why do we have scriptTimeoutW3C function in appium-ios-driver but not in uiautomator? Akshatha G K ... To change this, use 'showXcodeLog' desired capability...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found