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 2026-01-20] [$250] Split - Unable to add comma, unable to add number after comma when app is in Spanish #78095
Version Number: 9.2.82-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74652 Email or phone of affected tester (no customers):sjoinsjosjoisdjos@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Precondition:
App language is Spanish.
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense of amount 30.00
Open expense report.
Click More > Split > Percent.
Click on any input field.
Enter a comma.
BUG 1: Comma cannot be entered.
Enter a full stop.
Enter any amount after the comma.
BUG 2: Number cannot be added after comma.
Go to Amount (Importe) tab.
Enter 10.00 and 20.00 for the splits.
Switch to Percent.
Click on any input field and place cursor at the end.
👋 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:
Identify the pull request that introduced this issue and revert it.
[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: N/A
[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.
Regression Test Proposal
Precondition:
Set app language to Spanish
Navigate to workspace chat
Create an expense with amount $30.00
Open the expense report
Click "More" > "Split" > "Percent" tab
Enter "7,5" in the percentage field
Expected Result: Input accepts "7,5" and correctly interprets it as 7.5%
Activity
melvin-bot commentedon Dec 19, 2025
Triggered auto assignment to @JmillsExpensify (
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 Dec 19, 2025
Triggered auto assignment to @dangrous (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 19, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 19, 2025
👋 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:
38 remaining items
btkcodedev commentedon Jan 20, 2026
@suneox Can you share what the bot meant by BZ, It would pay via upwork isn't it? I am a newbie here.
melvin-bot commentedon Jan 20, 2026
Payment Summary
Upwork Job
BugZero Checklist (@JmillsExpensify)
btkcodedev commentedon Jan 21, 2026
This is my upwork proposal, please feel free to tag me if you need any additional info.
suneox commentedon Jan 21, 2026
BugZero Checklist
[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: https://github.com/Expensify/App/pull/74652/changes#r2712467009
[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: N/A
[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.
Regression Test Proposal
Precondition:
Set app language to Spanish
Expected Result: Input accepts "7,5" and correctly interprets it as 7.5%
Do we agree 👍 or 👎
suneox commentedon Jan 21, 2026
@btkcodedev The bot is just reminding us that I’ve completed the checklist. You’re currently waiting for the internal team to send the Upwork offer.
btkcodedev commentedon Jan 27, 2026
Thanks @suneox. Awaiting internal team response.
btkcodedev commentedon Jan 28, 2026
@JmillsExpensify Bump on this 🙇
mallenexpensify commentedon Jan 31, 2026
Payment Summary
Contributor: @btkcodedev paid $250 via Upwork
Contributor+: @suneox due $250 via NewDot
@btkcodedev can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022017391310160120311
^ Test case created
trjExpensify commentedon Jan 31, 2026
approved $250 for @suneox.
btkcodedev commentedon Jan 31, 2026
@mallenexpensify Accepted!
Thanks!
mallenexpensify commentedon Feb 3, 2026
@btkcodedev paid, summary updated above. Sorry it took a min.
Thx!