Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>From the help documents</p> <p><a href="http://developer.android.com/reference/android/view/inputmethod/InputConnection.html">http://developer.android.com/reference/android/view/inputmethod/InputConnection.html</a></p> <blockquote> <p>The InputConnection interface is the communication channel from an InputMethod back to the application that is receiving its input. It is used to perform such things as reading text around the cursor, committing text to the text box, and sending raw key events to the application.</p> </blockquote> <p>In addition, further reading shows</p> <blockquote> <p>getExtractedText(): This method may fail either if the input connection has become invalid <strong>(such as its process crashing) or the client is taking too long to respond with the text (it is given a couple seconds to return)</strong>. In either case, a null is returned.</p> </blockquote> <p>It appears to also monitor changes to such text, and alert changes.</p> <p>To hunt the issue down you'll have to explore any database queries you are making, perhaps around listViews or lists in a layout.</p> <p>If you don't have any views, for example it's happening randomly in the background, then i would suggest that its not a UI element issue, so ignore textfields and such. It could be a background service that's storing information in a cursor or requesting a cursor. </p> <p>Also, does the issue arise from your app? or perhaps someone else's that you've installed recently. List the full logCat trace. Someone might recognise the issue. </p> <p>I would hazard a guess that if you haven't written something specific around this that its someone elses log message, or perhaps that of a library your using?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload