I spent a while searching and I can't find this reported anywhere else, but I've never used Phabricator before. Sorry if this is a duplicate.
Steps to replicate the issue
- Open the Wikipedia app.
- Navigate to the Search view (via any route).
- Start typing in the search field.
What happens?
- Search results are very slow to arrive.
- Previously-displayed results disappear whenever text is inserted into the search field, leaving the results area blank until more results appear. When typing at normal speed, this causes a jarring flickering effect as results rapidly pop in and out of view. When repeatedly backspacing, the flickering becomes very fast.
- Sometimes, rarely, once typing is finished, the final search results take either a very long time to appear, or do not appear at all. I have found that when the results do not appear, continuing typing seems to prompt the appearance of new results, and the extra text can then be backspaced to get the desired results. Unfortunately I have no video of this.
What should have happened instead?:
- When text is inserted into the search field, the previous results should remain visible until new ones are ready to be displayed. (I think this is the old behaviour; either that, or the lack of a significant delay made this a non-issue.)
- Results should appear quickly.
- New results should always appear when the text in the search box changes.
Wrt the latency issue: I don't think this is a network issue as I was not experiencing this before the update, and the issue has occurred on all (three? I believe) networks I have tried; it did not happen on any of them before. I have noticed no change in any other apps.
Software version
Wikipedia 7.7.0 (4878) on iOS 18.3 (22D63)
Other information
I was able to replicate this both logged in and logged out, and it persists after manually clearing the cache in the app's settings. The bug presents consistently (now): I can't say whether it has happened consistently since the update to 7.7.0, but it never happened before, and it always happens now. I have attached a screen recording of the issue.
