You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Mobile search puts an older settled thread with an exact title match below weaker results #31873
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
Have several settled threads with similar titles (repeated work), some older than what the phone keeps loaded.
On mobile, search for words from the title of one of the older ones.
Expected behavior
The thread whose title matches best is at or near the top.
Actual behavior
It shows up for a moment, then lands below other results, or doesn't show up at all. I mostly find threads by name, so this makes search hard to use for older work.
What I think is going on
From reading the code at 25b53299:
Older settled threads aren't on the phone, so their title matches come from the server and arrive after the local results. useThreadListSearchMatches keeps rows that are already shown in place, so late ones go below.
searchOlderSettled returns at most 15 title rows (OLDER_SETTLED_TITLE_ROWS). With many similar titles, recency and open counts decide which 15 come back, so the one I want can miss the cut.
Mobile passes picks: false, so it doesn't remember which thread I opened for this search last time. Desktop does.
Possible fixes: let a late title match move above results that only match inside messages, use picks on mobile, or rank older settled title rows by title quality before recency.
Activity