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
[Due for payment 2025-08-26] [$250] Recent search history missing when opening search switcher before app reconnects #62335
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@quinthar Slack conversation (hyperlinked to channel name): #Quality
Action Performed:
Open the app
Immediately tap on the search switcher
Observe that the page is empty — no recent history is shown
Wait 20+ seconds for the app to finish reconnecting
Tap the search switcher again — recent history is now visible.
Expected Result:
Recent search history should load instantly, even if the app is still reconnecting in the background.
Actual Result:
Recent search history does not appear until the app completes reconnecting.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
changed the title [-]Recent search history missing when opening search switcher before app reconnects[/-][+][$250] Recent search history missing when opening search switcher before app reconnects[/+]on May 26, 2025
changed the title [-][$250] Recent search history missing when opening search switcher before app reconnects[/-][+][Due for payment 2025-08-26] [$250] Recent search history missing when opening search switcher before app reconnects[/+]on Aug 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.96-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@DylanDylann@strepanier03 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[Contributor] Classify the bug: This looks like a performance improvement
Bug classification
Source of bug:
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: This looks like a performance improvement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Log in to application
While app is reconnecting open Search modal with 🔍 icon
observe autocomplete list
it should show skeleton if no data is available
recent searches should be visible while reconnecting
Activity
melvin-bot commentedon May 19, 2025
Triggered auto assignment to @strepanier03 (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon May 23, 2025
@strepanier03 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
[-]Recent search history missing when opening search switcher before app reconnects[/-][+][$250] Recent search history missing when opening search switcher before app reconnects[/+]melvin-bot commentedon May 26, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021927051599348689449
melvin-bot commentedon May 26, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @DylanDylann (
External)84 remaining items
[-][$250] Recent search history missing when opening search switcher before app reconnects[/-][+][Due for payment 2025-08-26] [$250] Recent search history missing when opening search switcher before app reconnects[/+]melvin-bot commentedon Aug 19, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.96-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-08-26. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 19, 2025
@DylanDylann @strepanier03 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Aug 26, 2025
Payment Summary
Upwork Job
BugZero Checklist (@strepanier03)
strepanier03 commentedon Aug 28, 2025
@DylanDylann - Checklist when you have a sec!
DylanDylann commentedon Aug 28, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: This looks like a performance improvement
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
strepanier03 commentedon Aug 28, 2025
Thanks @DylanDylann payment summary is above!
garrettmknight commentedon Oct 29, 2025
$250 approved for @DylanDylann