Originally Posted by
doogald I have to say that I tried to recreate this on my Mac running Monterey. At first (e.g. just after note creation), I couldn't search for any of the strings. But, after testing a while later (a few hours later), I could successfully search for any of the substrings, and they were also case-independent (so "String3" returned the same way as "string3").
well - this is the problem, and explains why not many people immediately run into this issue.
It seems to be particular combinations of characters & words, that work, or not.
Normally, when starting to work with such an app, nobody will do extensive testing - nor is it possible - to figure out if EVERY combination works. This happens mainly by accident, like in my case.
All of the not working strings have been in my notes app since forever, AND I rebuilt the search index according to Apples advice, with no success.
In the meanwhile, 3 Apple people, independent from each other, could recreate the problem on their computers (and on mine). Yesterday we recorded a demo on my computer, to be sent to Apple R & D.
I did not want to bother you with the original string-combination that made problems, because it contains language specific special characters. But I found another note titled "Question for the Avengers Endgame specialist", making the same problems:
Avengers : found
venger : not found
vengers : found
avenger : found
endgame : not found (nor any substring version)
specialist : found
cialist : not found
pecialist : found
It might also be that the same strings that don't work on mine, do work on other computers, due to problems in the indexing process, but this is a thing only R&D people will be able to clarify, imho.