I want to add a search box inside my user keyboard, which allows the user to search for content that can then be entered into the main text document for which the keyboard is displayed.
However, calling -becomeFirstResponder on a -becomeFirstResponder object causes a 3-4 second lag during which no input is accepted. The same thing happens if I call -resignFirstResponder . I can set the text property of the text field just fine, but that means there is no caret and the text is truncated to fit.
When calling (become|resign)FirstResponder I get the following log messages:
2014-10-28 13: 39: 50.920 Giffy KB [2073: 514844] 0 images received
2014-10-28 13: 39: 57.942 Giffy KB [2073: 514745] <_UIRemoteInputViewController: 0x14762a030> time to wait for the fence barrier from com.theappical.giffage.giffagekb
2014-10-28 13: 39: 58.446 Giffy KB [2073: 514745]. The viewing service did not balance fencing start messages with end messages for a second; exit time.``
Other third-party keyboards don't seem to use text fields (they use custom views instead). Does this mean that this is a mistake at the end of Apple, or can I do something to resolve it?
source share