iOS now 'corrects' search string

Operating system

iOS

Joplin version

12.5.3

What issue do you have?

In recent iOS releases, search in Joplin often fails because iOS alters the search string before I press Enter to submit it. Is there a way to suppress this behavior? Has something changed in Joplin to permit it? I cannot recall when this started.

Are you sure that’s not the auto correct feature on your keyboard? Can you give an example of what text you entered and what it changed to?

That’s exactly what it is. Normally it does not operate on recognized search fields in apps. It makes it difficult to search for proper names or to use a partial search string. E.g., if I type “Ocmu” to search for “Ocmulgee”, pressing Return changes the string to “Come”. I have to check the search suggestions and select “Ocmu” in order to prevent the “correction.” This is unexpected and obnoxious when doing a search.

To correct my first post, the search string changes upon selecting Return, not before.

I’m not sure why this only started happening in recent versions, but currently the search inputs on the mobile app are not excluded from auto correct, auto complete and auto capitalize behaviours of the input method. Logically it makes sense to disable these for search fields though, so I have created the following PR to address this: Mobile: Disable auto correct, auto complete and auto capitalize for search fields by mrjo118 · Pull Request #14759 · laurent22/joplin · GitHub

EDIT: The change has been merged, so will be included in the Joplin 3.6 release