blocks|key|2901950|text|这个问题让我痛苦万分，但我设法找到了一个合适的解决方案。在模拟器中，确保已禁用I/O+->+Keyboard+->+Connect+hardware+keyboard。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2901951|entityMap^0|13|18|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This issue caused me a world of pain, but I've managed to figure out a proper solution. In the Simulator, make sure <code>I/O -&gt; Keyboard -&gt; Connect hardware keyboard</code> is off.

blocks|key|2689385|text|最近，我们发现了一个技巧，可以让接受的答案持久化。要禁用模拟器设置：I/O+->+Keyboard+->+Connect+hardware+keyboard从命令行应这样写：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2689386|defaults+write+com.apple.iphonesimulator+ConnectHardwareKeyboard+0|code-block|syntax|javascript|2689387|它不会影响正在运行模拟器-您需要重新启动模拟器或启动新的模拟器才能使设置生效。|2689388|entityMap^0|Y|18|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Recently we found a hack to make solution from accepted answer persistent. To disable Simulator setting: <code>I/O -&gt; Keyboard -&gt; Connect hardware keyboard</code> from command line one should write:
<pre><code>defaults write com.apple.iphonesimulator ConnectHardwareKeyboard 0
</code></pre>
It will not affect a simulator which is running - you need to restart simulator or start a new one to make that setting have its effect.

blocks|key|129655|text|我已经写了一个很小的扩展(Swift)，它非常适合我。代码如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|129656|extension+XCTestCase+{

++++func+tapElementAndWaitForKeyboardToAppear(element:+XCUIElement)+{
++++++++let+keyboard+=+XCUIApplication().keyboards.element
++++++++while+(true)+{
++++++++++++element.tap()
++++++++++++if+keyboard.exists+{
++++++++++++++++break;
++++++++++++}
++++++++++++NSRunLoop.currentRunLoop().runUntilDate(NSDate(timeIntervalSinceNow:+0.5))
++++++++}
++++}
}|code-block|syntax|javascript|129657|其主要思想是在键盘出现之前不断点击一个元素(文本字段)。|129658|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I have written a small extension (Swift) which works perfect for me.
Here is the code:

<pre><code>extension XCTestCase {

 func tapElementAndWaitForKeyboardToAppear(element: XCUIElement) {
 let keyboard = XCUIApplication().keyboards.element
 while (true) {
 element.tap()
 if keyboard.exists {
 break;
 }
 NSRunLoop.currentRunLoop().runUntilDate(NSDate(timeIntervalSinceNow: 0.5))
 }
 }
}
</code></pre>

The main idea is to keep tapping an element (text field) before the keyboard is presented.

blocks|key|130504|text|斯坦尼斯拉夫的想法是正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|130505|在团队环境中，你需要一些能够自动工作的东西。我在我的博客上提出了一个修复here。|offset|length|130506|基本上你只需要粘贴：|130507|UIPasteboard.generalPasteboard().string+=+"Their+password"
let+passwordSecureTextField+=+app.secureTextFields["password"]
passwordSecureTextField.pressForDuration(1.1)
app.menuItems["Paste"].tap()|code-block|syntax|javascript|130508|entityMap|0|LINK|mutability|MUTABLE|url|http://ryanpliske.com/^0|0|10|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Stanislav has the right idea. 

In a team environment, you need something that will automatically work. I've come up with a fix <a href="http://ryanpliske.com/" rel="noreferrer">here</a> on my blog.

Basically you just paste:

<pre><code>UIPasteboard.generalPasteboard().string = "Their password"
let passwordSecureTextField = app.secureTextFields["password"]
passwordSecureTextField.pressForDuration(1.1)
app.menuItems["Paste"].tap()
</code></pre>

blocks|key|2689414|text|导致此错误的另一个原因是，如果您试图在文本字段的父视图中输入设置为辅助功能元素(view.isAccessibilityElement+=+true)的文本。在这种情况下，XCTest无法获得子视图上的句柄来输入文本，并返回错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2689415|2689416|+UI测试失败-元素或任何子体都没有键盘焦点。|blockquote|2689417|2689418|2689419|这并不是说没有元素具有焦点(正如您经常在UITextField中看到键盘打开并闪烁光标那样)，而是它所能到达的元素都没有焦点。在尝试在UISearchBar中输入文本时，我遇到了这个问题。搜索栏本身不是文本字段，当将其设置为辅助功能元素时，对基础UITextField的访问被阻止。为了解决此问题，在UISearchBar上设置了searchBar.accessibilityIdentifier+=+"My+Identifier"，但isAccessibilityElement未设置为true。之后，测试表单的代码：|2689420|app.otherElements["My+Identifier"].tap()
app.otherElements["My+Identifier"].typeText("sample+text")|code-block|syntax|javascript|2689421|作品|2689422|entityMap^0|14|Y|0|0|0|0|0|46|B|4L|1F|62|M|6S|4|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|N|3|O|5|P|7|1C|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1D|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|V|$]]

Another cause of this error is if there is a parent view of the text field in which you are trying to enter text that is set as an accessibility element (<code>view.isAccessibilityElement = true</code>). In this case, XCTest is not able to get a handle on the subview to enter the text and returns the error.

<blockquote>
 UI Testing Failure - Neither element nor any descendant has keyboard
 focus.
</blockquote>

It isn't that no element has focus (as you can often see the keyboard up and blinking cursor in the UITextField), it is just that no element it can reach has focus. I ran into this when attempting to enter text in a UISearchBar. The search bar itself is not the text field, when setting it as an accessibility element, access to the underlying UITextField was blocked. To resolve this, <code>searchBar.accessibilityIdentifier = "My Identifier"</code> was set on the <code>UISearchBar</code> however the <code>isAccessibilityElement</code> was not set to <code>true</code>. After this, test code of the form:

<pre><code>app.otherElements["My Identifier"].tap()
app.otherElements["My Identifier"].typeText("sample text")
</code></pre>

Works

blocks|key|2689397|text|它在我身上发生了很多次。您必须在模拟器中禁用键盘硬件和与OSX相同的布局|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689398|硬件/键盘(全部禁用)|2689399|之后，键盘软件将不会被忽略，并且您的测试可以输入文本|2689400|​|2689401|📷|atomic|offset|length|2689402|2689403|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d7d32b648231d52951adce0f4f751bb7.png|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@$K|11|L|12|1|13]]|A|$]]|$1|M|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

It occurred with me for many times. 
You have to disable Keyboard Hardware and Same Layout as OSX in your Simulator

Hardware/Keyboard (disable all)

After that keyboard software won't dismiss and your tests can type text

<a href="https://i.stack.imgur.com/uXaCZ.png" rel="noreferrer"><img src="https://i.stack.imgur.com/uXaCZ.png" alt="Disable Hardware"></a>

blocks|key|2689362|text|func+pasteTextFieldText(app:XCUIApplication,+element:XCUIElement,+value:String,+clearText:Bool)+{
++++//+Get+the+password+into+the+pasteboard+buffer
++++UIPasteboard.generalPasteboard().string+=+value

++++//+Bring+up+the+popup+menu+on+the+password+field
++++element.tap()

++++if+clearText+{
++++++++element.buttons["Clear+text"].tap()
++++}

++++element.doubleTap()

++++//+Tap+the+Paste+button+to+input+the+password
++++app.menuItems["Paste"].tap()
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2689363|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>func pasteTextFieldText(app:XCUIApplication, element:XCUIElement, value:String, clearText:Bool) {
 // Get the password into the pasteboard buffer
 UIPasteboard.generalPasteboard().string = value

 // Bring up the popup menu on the password field
 element.tap()

 if clearText {
 element.buttons["Clear text"].tap()
 }

 element.doubleTap()

 // Tap the Paste button to input the password
 app.menuItems["Paste"].tap()
}
</code></pre>

blocks|key|2689405|text|在启动应用程序和在文本字段中键入数据之间使用睡眠，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689406|sleep(2)|code-block|syntax|javascript|2689407|在我的例子中，我每次都会得到这个错误，只有这个解决方案才能帮助我走出困境。|2689408|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Use a sleep between launching the app and typing in data in textfields like this:

<pre><code>sleep(2)
</code></pre>

In my case I was keeping getting this error every time and only this solution helped my out.

blocks|key|2689358|text|这可能会有帮助:我只是在错误前添加了一个“点击”操作；仅此而已:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689359|[app.textFields[@"theTitle"]+tap];
[app.textFields[@"theTitle"]+typeText:@"kk"];|code-block|syntax|javascript|2689360|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This maybe help: I just add a "tap" action before the error; that´s all :)

<pre><code>[app.textFields[@"theTitle"] tap];
[app.textFields[@"theTitle"] typeText:@"kk"];
</code></pre>

blocks|key|2901977|text|无论是键盘还是不连接键盘，都可以随心所欲地记录大小写。但在进行测试之前，请执行以下操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2901978|在玩测试时，应取消选中以下选项(连接硬件键盘)。|2901979|​|2901980|📷|atomic|offset|length|2901981|2901982|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/364ec4a6f3ef80081ca8c377d0411b9c.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@$I|Y|J|Z|1|10]]|A|$]]|$1|K|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

Record case however you want, keyboard or without keyboard attached.
But do the following before playing test.

This following option (connect hardware keyboard) should be unchecked while playing test.

<a href="https://i.stack.imgur.com/NxfGZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/NxfGZ.png" alt="enter image description here"></a>

blocks|key|127367|text|[转发Bartłomiej+Semańczyk的评论作为回答，因为它为我解决了问题]|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|127368|我需要在模拟器菜单栏中执行Simulator+>+Reset+Contents+and+Settings，这样才能开始为我工作。|127369|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/2725435/bart%25c5%2582omiej-sema%25c5%2584czyk^0|3|K|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

[Reposting <a href="https://stackoverflow.com/users/2725435/bart%c5%82omiej-sema%c5%84czyk">Bartłomiej Semańczyk</a>'s comment as an answer because it solved the problem for me]

I needed to do Simulator > Reset Contents and Settings in the simulator menu bar to make this start working for me.

blocks|key|129673|text|我遇到了这个问题，并能够在我的场景中修复它，方法是采用@AlexDenisov发布的解决方案，并将其添加到我的run+&测试的前置操作中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|129674|​|129675|📷|atomic|129676|129677|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/34812979|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d50ea5f99663f87753f1a70f1208dfc9.png|imageAlt^0|1J|3|1O|2|R|C|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|K|3|G|5|6|7|1C|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|U|P|V|E|$W|X|Y|-4]]]]

I ran into this issue and was able to fix it in my scenario by taking the solution posted by <a href="https://stackoverflow.com/a/34812979">@AlexDenisov</a> and adding it to my pre-actions for run &amp; test.
<a href="https://i.stack.imgur.com/RxgrE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RxgrE.png" alt="Pre-Action Run Script" /></a>

blocks|key|2689453|text|适用于我：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689454|extension+XCUIElement+{
++++func+typeTextAlt(_+text:+String)+{
++++++++//+Solution+for+`Neither+element+nor+any+descendant+has+keyboard+focus.`
++++++++if+!(self.value(forKey:+"hasKeyboardFocus")+as?+Bool+??+false)+{
++++++++++++XCUIDevice.shared.press(XCUIDevice.Button.home)
++++++++++++XCUIApplication().activate()
++++++++}
++++++++self.typeText(text)
++++}
}|code-block|syntax|javascript|2689455|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Works for me:
<pre><code>extension XCUIElement {
 func typeTextAlt(_ text: String) {
 // Solution for `Neither element nor any descendant has keyboard focus.`
 if !(self.value(forKey: &quot;hasKeyboardFocus&quot;) as? Bool ?? false) {
 XCUIDevice.shared.press(XCUIDevice.Button.home)
 XCUIApplication().activate()
 }
 self.typeText(text)
 }
}
</code></pre>

blocks|key|128407|text|当模拟器UI在前台(当您可以在模拟器窗口中看到变化时)运行UI测试时，上面的答案为我解决了这个问题。然而，它在后台运行它们时不起作用(例如，fastlane就是这样运行它们的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|128408|我不得不去Simulator+>+Device+>+Erase+All+Content+and+Settings...|offset|length|style|CODE|128409|为了清楚起见，我在模拟器设置中手动禁用-启用-禁用了硬件键盘，设置了defaults+write+com.apple.iphonesimulator+ConnectHardwareKeyboard+0，然后清除了内容和设置。|128410|entityMap^0|0|5|1I|0|Y|1U|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

The above answers solved it for me when running UI tests while the simulator UI is in the foreground (when you could see the changes in the simulator window). However, it did not work when running them in the background (which is how fastlane ran them, for example).
I had to go to <code>Simulator &gt; Device &gt; Erase All Content and Settings...</code>
To be clear, I manually disabled-enabled-disabled the Hardware Keyboard in the Simulator Settings, set <code>defaults write com.apple.iphonesimulator ConnectHardwareKeyboard 0</code>, and then erased content and settings.

blocks|key|2902000|text|有时文本字段不是作为文本字段实现的，或者它们被包装到另一个UI元素中而不容易访问。这是一个变通的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2902001|​|2902002|//XCUIApplication().scrollViews.otherElements.staticTexts["Email"]+the+locator+for+the+element
RegistrationScreenStep1of2.emailTextField.tap()
let+keys+=+app.keys
+keys["p"].tap()+//type+the+keys+that+you+need
+
+//If+you+stored+your+data+somewhere+and+need+to+access+that+string+//you+can+cats+your+string+to+an+array+and+then+pass+the+index+//number+to+key[]
+
+let+newUserEmail+=+Array(newPatient.email())
+let+password+=+Array(newPatient.password)
+
+//When+you+cast+your+string+to+an+array+the+elements+of+the+array+//are+Character+so+you+would+need+to+cast+them+into+string+otherwise+//Xcode+will+compain.+
+
+let+keys+=+app.keys
+++++keys[String(newUserEmail[0])].tap()
+++++keys[String(newUserEmail[1])].tap()
+++++keys[String(newUserEmail[2])].tap()
+++++keys[String(newUserEmail[3])].tap()
+++++keys[String(newUserEmail[4])].tap()
+++++keys[String(newUserEmail[5])].tap()+++++++|code-block|syntax|javascript|2902003|2902004|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|N|8|@]|9|@]|A|$G|H]]|$1|I|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|K|$]]

Sometime text fields are not implemented as text fields, or they're wrapped into another UI element and not easily accessible. 
Here's a work around:

<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>//XCUIApplication().scrollViews.otherElements.staticTexts["Email"] the locator for the element
RegistrationScreenStep1of2.emailTextField.tap()
let keys = app.keys
 keys["p"].tap() //type the keys that you need
 
 //If you stored your data somewhere and need to access that string //you can cats your string to an array and then pass the index //number to key[]
 
 let newUserEmail = Array(newPatient.email())
 let password = Array(newPatient.password)
 
 //When you cast your string to an array the elements of the array //are Character so you would need to cast them into string otherwise //Xcode will compain. 
 
 let keys = app.keys
 keys[String(newUserEmail[0])].tap()
 keys[String(newUserEmail[1])].tap()
 keys[String(newUserEmail[2])].tap()
 keys[String(newUserEmail[3])].tap()
 keys[String(newUserEmail[4])].tap()
 keys[String(newUserEmail[5])].tap() </code></pre>
</div>
</div>

blocks|key|2902019|text|以下是来自Swift+5.4，SwiftUI应用程序的场景，该场景将导致UI测试失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2902020|app.cells.firstMatch.tap()
//+transition+from+list+view+to+detail+view+for+item
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.tap()
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.typeText("7620")+//+:FAIL:|code-block|syntax|javascript|2902021|2902022|+测试：未能合成事件:元素和任何子体都没有键盘焦点。|blockquote|offset|length|style|BOLD|2902023|2902024|2902025|解决方案:再次点击|2902026|发现通过了第二个tap()。|CODE|2902027|app.cells.firstMatch.tap()
//+transition+from+list+view+to+detail+view+for+item
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.tap()
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.tap()
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.typeText("7620")+//+:PASS:|2902028|但是，.doubleTap()和tap(withNumberOfTaps:+2,+numberOfTouches:+1)仍然会失败。|2902029|解决方案:等待TextField到达，然后点击|2902030|有时视图转换需要明确地等待TextEdit的到来。下面的方法等待目标TextEdit字段的到来。|2902031|XCTestCase.swift扩展：|2902032|extension+XCTestCase+{
++++func+awaitArrival(element:+XCUIElement,+timeout:+TimeInterval)+{
++++++++let+predicate+=+NSPredicate(format:+"exists+==+1")
++++++++expectation(for:+predicate,+evaluatedWith:+element)+
++++++++waitForExpectations(timeout:+timeout)
++++}

++++func+awaitDeparture(element:+XCUIElement,+timeout:+TimeInterval)+{
++++++++let+predicate+=+NSPredicate(format:+"exists+==+0")
++++++++expectation(for:+predicate,+evaluatedWith:+element)+
++++++++waitForExpectations(timeout:+timeout)
++++}
}|2902033|示例用法：|2902034|app.cells.firstMatch.tap()
//+transition+from+list+view+to+detail+view+for+item
awaitArrival(
++++element:+app.textFields.matching(identifier:+"balance_textedit").element,+
++++timeout:+5)
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.tap()
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.typeText("7620")+//+:PASS:|2902035|Tap解决方案:先使用waitForExistence**，，然后使用**|2902036|使用XCUIElement提供的waitForExistence(timeout:)方法。|2902037|app.cells.firstMatch.tap()
//+transition+from+list+view+to+detail+view+for+item
app.textFields.matching(identifier:+"balance_textedit")
++++.element.waitForExistence(timeout:+5)
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.tap()
app.textFields
++++.matching(identifier:+"balance_textedit")
++++.element.typeText("7620")+//+:PASS:|2902038|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/documentation/xctest/xcuielement|1|https://developer.apple.com/documentation/xctest/xcuielement/2879412-waitforexistence/^0|0|0|0|1|2|0|0|0|0|9|0|8|5|0|0|3|C|G|18|0|0|N|0|0|0|0|0|0|B|I|Z|2|B|G|0|0|19|2|B|G|Q|2|B|0|G|Q|1|0|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1S|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1U|8|@$K|1V|L|1W|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1Z|8|@$K|20|L|21|M|N]]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@$K|23|L|24|M|U]]|9|@]|A|$]]|$1|V|3|W|5|D|7|25|8|@]|9|@]|A|$E|F]]|$1|X|3|Y|5|6|7|26|8|@$K|27|L|28|M|U]|$K|29|L|2A|M|U]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2B|8|@$K|2C|L|2D|M|N]]|9|@]|A|$]]|$1|11|3|12|5|6|7|2E|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2F|8|@]|9|@]|A|$]]|$1|15|3|16|5|D|7|2G|8|@]|9|@]|A|$E|F]]|$1|17|3|18|5|6|7|2H|8|@]|9|@]|A|$]]|$1|19|3|1A|5|D|7|2I|8|@]|9|@]|A|$E|F]]|$1|1B|3|1C|5|6|7|2J|8|@$K|2K|L|2L|M|N]|$K|2M|L|2N|M|N]|$K|2O|L|2P|M|U]]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|2Q|8|@$K|2R|L|2S|M|N]|$K|2T|L|2U|M|U]|$K|2V|L|2W|M|U]]|9|@$K|2X|L|2Y|1|2Z]|$K|30|L|31|1|32]]|A|$]]|$1|1F|3|1G|5|D|7|33|8|@]|9|@]|A|$E|F]]|$1|1H|3|-4|5|6|7|34|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O]]|1P|$5|1K|1L|1M|A|$1N|1Q]]]]

The following is from a Swift 5.4, SwiftUI app scenario which would fail UI Testing.
<pre class="lang-swift prettyprint-override"><code>app.cells.firstMatch.tap()
// transition from list view to detail view for item
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.tap()
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.typeText(&quot;7620&quot;) // :FAIL:
</code></pre>
<blockquote>
Test: Failed to synthesize event: Neither element nor any descendant has keyboard focus.
</blockquote>
Solution: Tap Again
A second <code>tap()</code> was found to pass.
<pre class="lang-swift prettyprint-override"><code>app.cells.firstMatch.tap()
// transition from list view to detail view for item
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.tap()
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.tap()
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.typeText(&quot;7620&quot;) // :PASS:
</code></pre>
However, <code>.doubleTap()</code> and <code>tap(withNumberOfTaps: 2, numberOfTouches: 1)</code> would still fail.
Solution: Await TextField Arrival, Then Tap
Sometimes a view transition needs to expressly await the TextEdit arrival. The approach below awaits the arrival of the targeted TextEdit field.
XCTestCase.swift extension:
<pre class="lang-swift prettyprint-override"><code>extension XCTestCase {
 func awaitArrival(element: XCUIElement, timeout: TimeInterval) {
 let predicate = NSPredicate(format: &quot;exists == 1&quot;)
 expectation(for: predicate, evaluatedWith: element) 
 waitForExpectations(timeout: timeout)
 }

 func awaitDeparture(element: XCUIElement, timeout: TimeInterval) {
 let predicate = NSPredicate(format: &quot;exists == 0&quot;)
 expectation(for: predicate, evaluatedWith: element) 
 waitForExpectations(timeout: timeout)
 }
}
</code></pre>
Example use:
<pre class="lang-swift prettyprint-override"><code>app.cells.firstMatch.tap()
// transition from list view to detail view for item
awaitArrival(
 element: app.textFields.matching(identifier: &quot;balance_textedit&quot;).element, 
 timeout: 5)
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.tap()
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.typeText(&quot;7620&quot;) // :PASS:
</code></pre>
Solution: <code>waitForExistence</code>, Then Tap
Use the <code><a href="https://developer.apple.com/documentation/xctest/xcuielement/2879412-waitforexistence/" rel="nofollow noreferrer">waitForExistence(timeout:)</a></code> method provided by <code><a href="https://developer.apple.com/documentation/xctest/xcuielement" rel="nofollow noreferrer">XCUIElement</a></code>.
<pre class="lang-swift prettyprint-override"><code>app.cells.firstMatch.tap()
// transition from list view to detail view for item
app.textFields.matching(identifier: &quot;balance_textedit&quot;)
 .element.waitForExistence(timeout: 5)
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.tap()
app.textFields
 .matching(identifier: &quot;balance_textedit&quot;)
 .element.typeText(&quot;7620&quot;) // :PASS:
</code></pre>

blocks|key|2901939|text|第一行只是一个查询定义，这并不意味着passwordSecureTextField实际上是存在的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2901940|您的第二行将动态执行查询，并尝试(重新)将查询绑定到UI元素。您应该在其上放置一个断点，并验证是否找到了一个且只有一个元素。或者只使用断言：|2901941|XCTAssertFalse(passwordSecureTextField.exists);|code-block|syntax|javascript|2901942|否则看起来没问题，tap应该强制键盘可见，然后typeText就可以正常工作了。错误日志应该会告诉你更多信息。|2901943|entityMap^0|7|4|I|N|0|0|0|9|3|N|8|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|W|8|@]|E|@]|F|$]]|$1|I|3|J|5|K|7|X|8|@]|E|@]|F|$L|M]]|$1|N|3|O|5|6|7|Y|8|@$9|Z|A|10|B|D]|$9|11|A|12|B|D]]|E|@]|F|$]]|$1|P|3|-4|5|6|7|13|8|@]|E|@]|F|$]]]|Q|$]]

Your first line is just a query definition, which doesn't mean that <code>passwordSecureTextField</code> would actually exist.

Your second line will dynamically execute the query and try to (re)bind the query to UI element. You should put a breakpoint on it and verify that one and only one element is found. Or just use an assert:

<pre><code>XCTAssertFalse(passwordSecureTextField.exists);
</code></pre>

Otherwise it looks ok, <code>tap</code> should force keyboard visible and then <code>typeText</code> should just work. Error log should tell you more info.

blocks|key|127371|text|别搞砸了，发现问题的原因是你记录了你的测试时间，你的应用程序会连接硬件键盘，而你的自动测试时间模拟器只使用软件键盘。所以关于如何解决这个问题。只需使用软件键盘对您的录制时间。你可以看到魔力。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|127372|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Don't messed up, There problem caught the reason is you are recorded your testing time your app will connection hardware keyboard while your automatic testing time simulator takes only software keyboard. so for how to fix this issues. Just use software keyboard on your recording time. you can see the magic.

blocks|key|2901984|text|我的问题和Ted的问题是一样的。实际上，如果在登录字段和硬件KB打开后点击密码字段，则软件键盘将在第二次字段点击时自行关闭，并且它不是特定于UI测试的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2901985|在花了一段时间摆弄AppleScript之后，我想出了以下建议(欢迎改进)：|2901986|tell+application+"Simulator"+++++activate+++++tell+application+"System+Events"+++++++++try+++++++++++++tell+process+"Simulator"+++++++++++++++++tell+menu+bar+1+++++++++++++++++++++tell+menu+bar+item+"Hardware"+++++++++++++++++++++++++tell+menu+"Hardware"+++++++++++++++++++++++++++++tell+menu+item+"Keyboard"+++++++++++++++++++++++++++++++++tell+menu+"Keyboard"+++++++++++++++++++++++++++++++++++++set+menuItem+to+menu+item+"Connect+Hardware+Keyboard"+++++++++++++++++++++++++++++++++++++tell+menu+item+"Connect+Hardware+Keyboard"+++++++++++++++++++++++++++++++++++++++++set+checkboxStatus+to+value+of+attribute+"AXMenuItemMarkChar"+of+menuItem+++++++++++++++++++++++++++++++++++++++++if+checkboxStatus+is+equal+to+"✓"+then+++++++++++++++++++++++++++++++++++++++++++++click+++++++++++++++++++++++++++++++++++++++++end+if+++++++++++++++++++++++++++++++++++++end+tell+++++++++++++++++++++++++++++++++end+tell+++++++++++++++++++++++++++++end+tell+++++++++++++++++++++++++end+tell+++++++++++++++++++++end+tell+++++++++++++++++end+tell+++++++++++++end+tell+++++++++on+error+++++++++++++tell+application+"System+Preferences"+++++++++++++++++activate+++++++++++++++++set+securityPane+to+pane+id+"com.apple.preference.security"+++++++++++++++++tell+securityPane+to+reveal+anchor+"Privacy_Accessibility"+++++++++++++++++++++display+dialog+"Xcode+needs+Universal+access+to+disable+hardware+keyboard+during+tests(otherwise+tests+may+fail+because+of+focus+issues)"+++++++++++++++++end+tell+++++++++end+try+++++end+tell+end+tell|offset|length|style|CODE|2901987|使用上面的代码创建一个脚本文件，并将其添加到必要的目标(可能仅限UI测试目标，您可能希望向开发目标添加类似的脚本，以便在开发期间重新启用HW键盘)。您应该在构建阶段中添加Run+Script阶段，并像这样使用它：osascript+Path/To/Script/script_name.applescript|2901988|entityMap^0|0|0|0|163|0|2D|A|2Y|1C|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@$F|T|G|U|H|I]|$F|V|G|W|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

The problem for me was the same as for Ted. Actually if password field gets tapped after login field and hardware KB is on, software keyboard will dismiss itself on second field tap, and it's not specific to UI tests.

After some time messing around with AppleScript, here's what I came up with(improvements are welcome):

<code>
tell application "Simulator"
 activate
 tell application "System Events"
 try
 tell process "Simulator"
 tell menu bar 1
 tell menu bar item "Hardware"
 tell menu "Hardware"
 tell menu item "Keyboard"
 tell menu "Keyboard"
 set menuItem to menu item "Connect Hardware Keyboard"
 tell menu item "Connect Hardware Keyboard"
 set checkboxStatus to value of attribute "AXMenuItemMarkChar" of menuItem
 if checkboxStatus is equal to "✓" then
 click
 end if
 end tell
 end tell
 end tell
 end tell
 end tell
 end tell
 end tell
 on error
 tell application "System Preferences"
 activate
 set securityPane to pane id "com.apple.preference.security"
 tell securityPane to reveal anchor "Privacy_Accessibility"
 display dialog "Xcode needs Universal access to disable hardware keyboard during tests(otherwise tests may fail because of focus issues)"
 end tell
 end try
 end tell
end tell
</code>

Create a script file with code above and add it to necessary targets(probably UI tests target only, you may want to add similar script to your development targets to re-enable HW keyboard during development).
You should add <code>Run Script</code> phase in build phases and use it like this:
<code>osascript Path/To/Script/script_name.applescript</code>

blocks|key|2689410|text|在为包含UIControl子视图的自定义视图(UIStackView子类)设置accessibilityIdentifier值时，我们遇到了相同的错误。在这种情况下，XCTest无法获得后代元素的键盘焦点。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2689411|我们的解决方案只是从父视图中删除accessibilityIdentifier，并通过专用属性为子视图设置accessibilityIdentifier。|2689412|entityMap^0|4|9|N|B|13|N|0|G|N|1H|N|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

We encountered the same error when setting the <code>accessibilityIdentifier</code> value for a custom view (<code>UIStackView</code> subclass) containing <code>UIControl</code> subviews. In that case XCTest was unable to get the keyboard focus for the descendent elements.

Our solution was simply to remove the <code>accessibilityIdentifier</code> from our parent view and set the <code>accessibilityIdentifier</code> for the subviews through dedicated properties.

blocks|key|128394|text|另一个答案，但对我们来说，问题是这个观点太接近于另一个观点，即它上的手势识别器。我们发现我们需要视图至少有20个像素的距离(在下面的例子中)。从字面上看，15个不起作用，20个或更多起作用。这很奇怪，我承认，但我们有一些UITextViews是有效的，一些不是，所有的都在相同的父级和相同的其他位置(当然还有变量名)。键盘开着还是关着，或者其他什么都没有影响。可访问性显示了这些字段。我们重新启动了我们的电脑。我们做了干净的构建。新的源码签出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|128395|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another answer, but for us the problem was the view was too close to another view that a Gesture recognizer on it. We found we needed the view to be at least 20 pixels away (in our case below). Literally 15 didn't work and 20 or more did. This is strange I'll admit, but we had some UITextViews that were working and some that were not and all were under the same parent and identical other positioning (and variable names of course). The keyboard on or off or whatever made no difference. Accessibility showed the fields. We restarted our computers. We did clean builds. Fresh source checkouts.

blocks|key|2689428|text|无需在I/O中打开/关闭键盘。不要在secureTextField中使用.typeText，只需使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689429|app.keys["p"].tap()
app.keys["a"].tap()
app.keys["s"].tap()
app.keys["s"].tap()|code-block|syntax|javascript|2689430|奖励:你会听到键盘的声音，点击:)|2689431|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

No Need to turn on/off keyboard in I/O.
Don't use .typeText for secureTextField, just use

<pre><code>app.keys["p"].tap()
app.keys["a"].tap()
app.keys["s"].tap()
app.keys["s"].tap()
</code></pre>

Bonus: You get keyboard sound click :)

blocks|key|2689433|text|最后，我编写了一个脚本来编辑模拟器的.plist文件，并将所选模拟器的ConnectHardwareKeyboard属性设置为false。您没听错，它更改了"DevicePreferences“字典中特别选择的模拟器的属性，而不是编辑全局属性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2689434|首先，使用以下内容创建一个名为disable-hardware-keyboard.sh的shell脚本。您可以将其放在“YourProject/xyzUITests/Scripts/”中：|BOLD|2689435|echo+"Script:+Set+ConnectHardwareKeyboard+to+false+for+given+Simulator+UDID"

if+[[+$1+!=+*-*-*-*-*+]];+then
++++echo+"Pass+device+udid+as+first+argument."
++++exit+1
else
++++DEVICE_ID=$1
fi

DEVICE_PREFERENCES_VALUE='<dict><key>ConnectHardwareKeyboard</key><false/></dict>'
killall+Simulator+#+kill+restart+the+simulator+to+make+the+plist+changes+picked+up
defaults+write+com.apple.iphonesimulator+DevicePreferences+-dict-add+$DEVICE_ID+$DEVICE_PREFERENCES_VALUE
open+-a+Simulator+#+IMPORTANT|code-block|syntax|javascript|2689436|现在按照以下步骤调用它，并将所选模拟器的udid作为参数传递：|2689437|2689438|编辑您的Xcode方案(或UI测试特定方案，如果有)|ordered-list-item|2689439|转到:测试>通过点击"%2B“符号>+"New+Run+script+Action".|2689440|Important:+Inside”提供构建设置来创建新脚本“下拉列表选择您的主应用程序目标，而不是UI测试目标。|2689441|现在在下面的文本区域中添加以下脚本。|2689442|2689443|测试>预操作中的脚本：|2689444|#!/bin/sh
#+$PROJECT_DIR+is+path+to+your+source+project.+This+is+provided+when+we+select+"Provide+build+settings+from"+to+"AppTarget"
#+$TARGET_DEVICE_IDENTIFIER+is+the+UDID+of+the+selected+simulator
sh+$PROJECT_DIR/xyzUITests/Scripts/disable-hardware-keyboard.sh+$TARGET_DEVICE_IDENTIFIER

#+In+order+to+see+output+of+above+script,+append+following+with+it:
#++%7C+tee+~/Desktop/ui-test-scheme-prescript.txt|2689445|测试它的时间：|2689446|2689447|启动适用于它的simulator|2689448|Enable硬件键盘|2689449|运行任何带有键盘交互的UI测试。观察模拟器重新启动，硬件键盘被禁用。测试的键盘交互运行良好。:)|2689450|2689451|entityMap^0|Z|N|0|F|S|0|0|0|V|0|0|0|0|0|A|0|0|0|0|0|4|3|0|0|0|0|G|2|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1J|8|@$9|1K|A|1L|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1M|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1N|8|@$9|1O|A|1P|B|H]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|Q|3|R|5|S|7|1R|8|@]|D|@]|E|$]]|$1|T|3|U|5|S|7|1S|8|@]|D|@]|E|$]]|$1|V|3|W|5|S|7|1T|8|@$9|1U|A|1V|B|H]]|D|@]|E|$]]|$1|X|3|Y|5|S|7|1W|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1X|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|12|3|13|5|K|7|1Z|8|@]|D|@]|E|$L|M]]|$1|14|3|15|5|6|7|20|8|@$9|21|A|22|B|H]]|D|@]|E|$]]|$1|16|3|-4|5|6|7|23|8|@]|D|@]|E|$]]|$1|17|3|18|5|S|7|24|8|@]|D|@]|E|$]]|$1|19|3|1A|5|S|7|25|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|S|7|26|8|@$9|27|A|28|B|H]]|D|@]|E|$]]|$1|1D|3|-4|5|6|7|29|8|@]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|2A|8|@]|D|@]|E|$]]]|1F|$]]

Finally, I wrote a script which edits the Simulator's .plist file and sets the <code>ConnectHardwareKeyboard</code> property to false for the selected simulator. You heard it right, it changes the property for the specifically selected simulator inside &quot;DevicePreferences&quot; dictionary rather than editing the global property.
First, create a shell script named disable-hardware-keyboard.sh with the following contents. You can place it within &quot;YourProject/xyzUITests/Scripts/&quot;.:
<pre><code>echo &quot;Script: Set ConnectHardwareKeyboard to false for given Simulator UDID&quot;

if [[ $1 != *-*-*-*-* ]]; then
 echo &quot;Pass device udid as first argument.&quot;
 exit 1
else
 DEVICE_ID=$1
fi

DEVICE_PREFERENCES_VALUE='&lt;dict&gt;&lt;key&gt;ConnectHardwareKeyboard&lt;/key&gt;&lt;false/&gt;&lt;/dict&gt;'
killall Simulator # kill restart the simulator to make the plist changes picked up
defaults write com.apple.iphonesimulator DevicePreferences -dict-add $DEVICE_ID $DEVICE_PREFERENCES_VALUE
open -a Simulator # IMPORTANT
</code></pre>
Now follow these steps to call it with passing the selected simulator's udid as an argument:
<ol>
<li>Edit your Xcode scheme (or UI tests specific scheme if you have one)</li>
<li>Go to: Test &gt; Pre-actions</li>
<li>Add new script by tapping &quot;+&quot; symbol &gt; &quot;New Run Script Action&quot;.</li>
<li>Important: Inside &quot;Provide build settings from&quot; dropdown choose your main app target, not the UI tests target.</li>
<li>Now add the following script in the text area below.</li>
</ol>
Script inside Test&gt;Pre-actions:
<pre><code>#!/bin/sh
# $PROJECT_DIR is path to your source project. This is provided when we select &quot;Provide build settings from&quot; to &quot;AppTarget&quot;
# $TARGET_DEVICE_IDENTIFIER is the UDID of the selected simulator
sh $PROJECT_DIR/xyzUITests/Scripts/disable-hardware-keyboard.sh $TARGET_DEVICE_IDENTIFIER

# In order to see output of above script, append following with it:
# | tee ~/Desktop/ui-test-scheme-prescript.txt
</code></pre>
Time to test it:
<ol>
<li>Launch simulator</li>
<li>Enable hardware keyboard for it</li>
<li>Run any UI test with keyboard interaction. Observe the simulator restarts and the hardware keyboard is disabled. And the test's keyboard interaction is working fine. :)</li>
</ol>

blocks|key|2902013|text|长话短说:+iOS模拟器中的硬件键盘输入似乎损坏了很长一段时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2902014|问题是，来自com.apple.UIKit.axbundle的-[UIApplicationSupport+_accessibilityHardwareKeyboardActive]私有方法有时会返回NO，即使它应该返回YES+(当文本输入视图为firstResponder，并且光标闪烁时，从字面上看，这意味着硬件键盘是活动的)。|offset|length|style|CODE|2902015|把这个代码放在应用程序的任何地方，使iOS模拟器相信，如果软件键盘是不活动的，那么硬件键盘是活动的。|2902016|#if+TARGET_OS_SIMULATOR
__attribute__((constructor))
static+void+Fix_UIApplicationAccessibility__accessibilityHardwareKeyboardActive(void)+{
++++{
++++++++static+id+observer+=+nil;

++++++++observer+=+[[NSNotificationCenter+defaultCenter]+addObserverForName:NSBundleDidLoadNotification
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++object:nil
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++queue:nil
++++++++++++++++++++++++++++++++++++++++++++++++++++++usingBlock:%5E(NSNotification+*+_Nonnull+note)+{
++++++++++++NSBundle+*bundle+=+note.object;
++++++++++++if+([bundle.bundleIdentifier+isEqualToString:@"com.apple.UIKit.axbundle"])+{
++++++++++++++++Class+cls+=+objc_lookUpClass("UIApplicationAccessibility");
++++++++++++++++SEL+sel+=+sel_getUid("_accessibilityHardwareKeyboardActive");
++++++++++++++++Method+m+=+class_getInstanceMethod(cls,+sel);
++++++++++++++++method_setImplementation(m,+imp_implementationWithBlock(%5EBOOL(UIApplication+*app)+{
++++++++++++++++++++return+![[app+valueForKey:@"_accessibilitySoftwareKeyboardActive"]+boolValue];
++++++++++++++++}));
++++++++++++}
++++++++}];
++++}
}
#endif|code-block|syntax|javascript|2902017|entityMap^0|0|6|O|V|1O|2S|2|32|3|3F|E|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$]]

Long story short: hardware keyboard input in iOS Simulator seems to broken for a long time.
The thing is that <code>-[UIApplicationSupport _accessibilityHardwareKeyboardActive]</code> private method from <code>com.apple.UIKit.axbundle</code> sometimes returns <code>NO</code> even though it should return <code>YES</code> (when a text input view is <code>firstResponder</code>, and the cursor is blinking, which literally means that the hardware keyboard is active).
Put this code anywhere in the app to make iOS Simulator believe that if Software Keyboard is inactive then the hardware one is active.
<pre><code> 
#if TARGET_OS_SIMULATOR
__attribute__((constructor))
static void Fix_UIApplicationAccessibility__accessibilityHardwareKeyboardActive(void) {
 {
 static id observer = nil;

 observer = [[NSNotificationCenter defaultCenter] addObserverForName:NSBundleDidLoadNotification
 object:nil
 queue:nil
 usingBlock:^(NSNotification * _Nonnull note) {
 NSBundle *bundle = note.object;
 if ([bundle.bundleIdentifier isEqualToString:@&quot;com.apple.UIKit.axbundle&quot;]) {
 Class cls = objc_lookUpClass(&quot;UIApplicationAccessibility&quot;);
 SEL sel = sel_getUid(&quot;_accessibilityHardwareKeyboardActive&quot;);
 Method m = class_getInstanceMethod(cls, sel);
 method_setImplementation(m, imp_implementationWithBlock(^BOOL(UIApplication *app) {
 return ![[app valueForKey:@&quot;_accessibilitySoftwareKeyboardActive&quot;] boolValue];
 }));
 }
 }];
 }
}
#endif
</code></pre>

blocks|key|129660|text|Securetextfield也有同样的问题。我的模拟器中的连接硬件选项是的，但仍然遇到问题。最后，这对我很有效(Swift+3)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|129661|+let+enterPasswordSecureTextField+=+app.secureTextFields["Enter+Password"]
++++enterPasswordSecureTextField.tap()
++++enterPasswordSecureTextField.typeText("12345678")|code-block|syntax|javascript|129662|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Had the same issue with Securetextfields. The connect hardware option in my Simulator was of, but still ran into the issue. Finally, this worked for me (Swift 3):

<pre><code> let enterPasswordSecureTextField = app.secureTextFields["Enter Password"]
 enterPasswordSecureTextField.tap()
 enterPasswordSecureTextField.typeText("12345678")
</code></pre>

blocks|key|2689424|text|为我解决这个问题的方法是增加一个1秒的睡眠时间：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2689425|let+textField+=+app.textFields["identifier"]
textField.tap()
sleep(1)
textField.typeText(text)|code-block|syntax|javascript|2689426|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What fixed this problem for me was adding a 1 second sleep:

<pre><code>let textField = app.textFields["identifier"]
textField.tap()
sleep(1)
textField.typeText(text)
</code></pre>

This is my case:

<pre><code>let passwordSecureTextField = app.secureTextFields["password"]
passwordSecureTextField.tap()
passwordSecureTextField.typeText("wrong_password") //here is an error
</code></pre>

<blockquote>
 UI Testing Failure - Neither element nor any descendant has keyboard focus. Element:
</blockquote>

What is wrong? This is working nice for normal <code>textFields</code>, but problem arise only with <code>secureTextFields</code>. Any workarounds?

UI Testing Failure - Neither element nor any descendant has keyboard focus on secureTextField

这是我的案例：let passwordSecureTextField = app.secureTextFields["password"]passwordSecureTextField.tap()passwordSecureTextField.typeText("wrong_password") //here is an error UI测试失败-元素或任何子体都没有键盘焦点。元素：怎么啦？这对于

问UI测试失败-元素或任何子体都不将键盘焦点放在secureTextField上
EN

回答 26

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UI测试失败-元素或任何子体都不将键盘焦点放在secureTextField上EN

回答 26

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UI测试失败-元素或任何子体都不将键盘焦点放在secureTextField上
EN