Android
3.6.18
Since the latest update, I am frequently (not always) unable to enter any text via keyboard or inserting from clipboard into the serach field. Stopping & restarting Joplin fixes it.
Anyone else notice this behaviour?
Cheers,
kai.
I noticed this happening once on the new version. It has not happened since though
Also can you clarify, is the issue with the search field in the note editor, or the global search available from the note list? In my case ot happened with the global search
Global search from the note list here as well.
Sorry for being unprecise here; never use the search function within a note. If this merits a proper issue in Github, I could raise one later today.
Yes, please raise an issue on Github
I do not have the same exact problem but something related to the search function. Since last update, on android when I search something, the searched text is no longer highlighted within the notes.
@franKamente I assume you're using the Rich text editor? I have created issue Mobile: Inline search does not scroll to the position of the match when using the Rich text editor · Issue #15429 · laurent22/joplin · GitHub which I suspect is your issue. The highlighting works fine for me in both the markdown editor and rich text editor, but there is a problem with scrolling to the result not working in the Rich text editor
@Kai Also would you mind providing a video when it happens? If you don't want to share note names, you could edit it afterward to blur over some areas
No, I think I never used the Rich text editor, I refer to the markdown one. I am curre tly using Joplin 3.6.18 on android 16
I can try. The note names aren't the problem, since if the error occurs (no input in input field) then there will be no list of results; but how do I record something that is not happening, especially when it isn't deterministic? I'll try.
@franKamente I think what you're seeing is that when you open a note, in Joplin 3.6 it now opens in the last mode you were in (view or edit). If the last open mode is edit mode, in the markdown editor you wont see the search highlighting as soon as you open the note via the search (in the rich text editor you do see the highlighting immediately). You either need to switch to view mode, or open the inline search from the editor (which is auto filled with the global search term), in order to see the search highlighting.
FYI Joplin 3.6 is going to receive an update soon, which will revert to the original behaviour of opening in view mode first, but instead there will be a configuration option to allow opening in the last mode
You were right! Thank you 
Yeah I get you. What I mean is record it when you notice it happening, as you said it happens regularly for you. Ideally you should show exiting the search and going to the note list, then going back to the search again showing the issue persisting
@Kai It's been a few days now and you haven't uploaded a video so far. So is the issue happening less now, or was it never actually a 'frequent' issue?
That is correct. It occurs frequently enough for me to notice it but I don't track it; obviously it depends on how often I search. So two points here:
But I have just restarted Joplin and tried again, so please check the attached video. (And I would be interested in how this helps us ...)
Cheers,
kai.
And once it occurres it's too late to start the recording
I thought you said you have to restart the app to resolve the issue, which should mean once it occurs it isn't too late to start the recording. Are you saying the issue goes away if you exit the search screen and come back, without needing to restart?
Regarding the video, that was actually really helpful. I can see that the caret is blinking (consistently at the same rate, even while typing) but typing using the on screen keyboard is not making any changes to the search term, and pressing the tick on the keyboard does not dismiss the keyboard either. I think I recall that was what happened to me before, but it's a blur because it only happened to me once. This tells us 2 things: the search input is in focus, and the search input is not disabled. I still have no idea what is causing the issue, but we now at least have a lead about what it is happening internally. Another observation is the typed characters accumulate in the suggestion area of the Gboard onscreen keyboard, but the TextInput itself never updates. So there is a lot that can be drawn from just being able to see what happens 
Sorry, terrible at describing things; not a professional tester ...
Yes, I have to restart Joplin to (usually) fix the issue, and no, unfortunately it does not disappear after just exiting and returning to the search screen; so your objection that it isn't too late to start the recording is correct; it just never came to my mind.
Anyway, I'm glad the recording worked, and if it even helps towards a fix, so much the better. Should I also upload this to the Github issue?
Cheers,
kai.
Yes please
