[Due for payment 2025-02-27] Search - Last digits are cleared when trying to enter a second decimal point (dot)

[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: v9.0.94-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #53695
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: MacOS Chrome, Desktop
App Component: Search

Action Performed:

1. Go Reports > click on Filter > click on Total
2. Enter few digits > press dot key or comma key to enter a decimal point
3. Enter two digits after the decimal point
4. Move the cell pointer on the left side of the entered decimal point (dot)
5. Press dot key

Expected Result:

Nothing should happen as there is an existing decimal point (dot) in the number
Or pointer should jump to the end of entered amount as it does on production

Actual Result:

The last digits next to first decimal point are cleared

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6733024_1738666256330.Screen_Recording_2025-02-04_at_1.43.56_in_the_afternoon.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @alexpensify (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.

[IuliiaHerets]

Not repro on prod

bandicam.2025-02-04.13-57-52-985.mp4

[brunovjk]

@kirillzyusko do you know what might be causing this too? I'll look into it in a moment.

[kirillzyusko]

Looking into this 👀

[kirillzyusko]

I think I found a fix - will try to prepare PR tomorrow!

[luacmartins]

Thanks @kirillzyusko! This is a deploy blocker, so we'll try to address it today. Do you know the cause of the issue?

[luacmartins]

Demoting it to NAB. @kirillzyusko let's address this tomorrow

[kirillzyusko]

Do you know the cause of the issue?

Well, yeah, a new input implementation 😁

And now the algorithm works like:

• we have an input 123,456
• let's try to format it to mask, so the value will be 123,45
• let's apply the mask

My current approach is to create a variations of the mask (affine format) so that 123,456 will be considered as invalid input for mask and such change will be simply ignored.

Thanks for demoting this!

[kirillzyusko]

Okay, the trick with affinity format didn't work, so currently I'm working on another solution.

The new approach will be the validation of a new string before proceeding to "masking" stage. I think tomorrow I can prepare a PR and will ask @brunovjk to test these changes (because he has a lot of knowledge on how to test this component) 👀

[melvin-bot]

@alexpensify, @luacmartins, @kirillzyusko, @brunovjk Huh... This is 4 days overdue. Who can take care of this?

[brunovjk]

Update: Still working on the PR

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.1-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• fix: pre-validate masked input #56462

If no regressions arise, payment will be issued on 2025-02-27. 🎊

For reference, here are some details about the assignees on this issue:

• @kirillzyusko does not require payment (Contractor)
• @brunovjk requires payment (Needs manual offer from BZ)

[melvin-bot]

@brunovjk @alexpensify @brunovjk 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]