[Due for payment 2025-09-02] [$1000] Space inserted in search bar when replacing whole search string

[m-natarajan]

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.71-0
Reproducible in staging?: Y
Reproducible in production?: Y
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: @dubielzyk-expensify
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Go to Reports
2. Click Reports in the left hand nav
3. Click search bar and select everything
4. Type test and observe

Expected Result:

The system types the string "test" without any spaces or interruptions, resulting in a continuous sequence of characters: test

Actual Result:

The system types the string "t est" with an unintended space between the "t" and "est", resulting in a broken sequence: t est.

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:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021940250505308910320
• Upwork Job ID: 1940250505308910320
• Last Price Increase: 2025-08-15

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot]

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.

[thelullabyy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The system types the string "t est" with an unintended space between the "t" and "est", resulting in a broken sequence: t est.

What is the root cause of that problem?

The autocomplete parser incorrectly adds an extra space when calculating position offsets in the identifier rule.
We always adds 1 to the position counter, regardless of whether there's actually a comma separator or not. This causes the parser to calculate incorrect position offsets.

App/src/libs/SearchParser/autocompleteParser.peggy

Line 107 in 014edee

count += filter.length + 1;

When a user selects all text and types the first character, the parser treats the entire text as a single element and applies this offset calculation, resulting in an extra space being inserted after the typed character.

What changes do you think we should make in order to solve the problem?

Should only add the +1 offset when there's actually a comma separator between elements, not for every element processed.

count += filter.length + (index < value.length - 1 ? 1 : 0)

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

@strepanier03 Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@strepanier03 Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021940250505308910320

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)