iOS - Search - Unable to double tap on the search field to highlight it

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.1.1.0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): applausetester+sj9032@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.3
App Component: Search

Action Performed:

1. Launch ND or hybrid app.
2. Tap search icon on the top right.
3. Type anything into the search field.
4. Double tap on the term on the search field.

Expected Result:

The search term can be highlighted.

Actual Result:

The search term cannot be highlighted.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6747719_1739961218736.ScreenRecording_02-19-2025_18-31-07_1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @danieldoglas (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @lschurr (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]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[luacmartins]

I can only reproduce sporadically. Gonna demote to NAB. @SzymczakJ it might have come from our PR, let's investigate in a follow up.

[SzymczakJ]

I've already made some investigation with @289Adam289, and it seems like it was present on main before the merge of my PR. Nevertheless we'll regroup tomorrow and try to assign somebody from our team to take this.

[luacmartins]

Thanks for the update! Yea, NAB for now.

[luacmartins]

Gonna close this issue in favor of #57191