Skip to content

[Due for payment 2026-01-20] [$250] Split - Unable to add comma, unable to add number after comma when app is in Spanish #78095

Closed

Description

@mitarachim

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.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.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense of amount 30.00
  4. Open expense report.
  5. Click More > Split > Percent.
  6. Click on any input field.
  7. Enter a comma.
    BUG 1: Comma cannot be entered.
  8. Enter a full stop.
  9. Enter any amount after the comma.
    BUG 2: Number cannot be added after comma.
  10. Go to Amount (Importe) tab.
  11. Enter 10.00 and 20.00 for the splits.
  12. Switch to Percent.
  13. Click on any input field and place cursor at the end.
  14. Press Delete key.
    BUG 3: Nothing happens after pressing Delete key.

Expected Result:

BUG 1: Comma can be entered.
BUG 2: Number can be added after comma.
BUG 3: Delete key will delete the amount.

Actual Result:

BUG 1: Comma cannot be entered.
BUG 2: Number cannot be added after comma.
BUG 3: Nothing happens after pressing Delete key.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7033315_1766103447603.18.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022002024408395653252
  • Upwork Job ID: 2002024408395653252
  • Last Price Increase: 2025-12-19
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Dec 19, 2025
  2. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 19, 2025

    @github-actions
    Contributor

    👋 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.
  6. 38 remaining items

  7. btkcodedev commented on Jan 20, 2026

    @btkcodedev
    Contributor

    @suneox Can you share what the bot meant by BZ, It would pay via upwork isn't it? I am a newbie here.

  8. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @suneox owed $250 via NewDot
    • ROLE: @btkcodedev paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@JmillsExpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/2002024408395653252/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  9. btkcodedev commented on Jan 21, 2026

    @btkcodedev
    Contributor

    Reference for my Upwork proposal
    PR: #78246

    This is my upwork proposal, please feel free to tag me if you need any additional info.

  10. suneox commented on Jan 21, 2026

    @suneox
    Contributor

    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

    1. Navigate to workspace chat
    2. Create an expense with amount $30.00
    3. Open the expense report
    4. Click "More" > "Split" > "Percent" tab
    5. Enter "7,5" in the percentage field

    Expected Result: Input accepts "7,5" and correctly interprets it as 7.5%

    Do we agree 👍 or 👎

  11. suneox commented on Jan 21, 2026

    @suneox
    Contributor

    @suneox Can you share what the bot meant by BZ, It would pay via upwork isn't it? I am a newbie here.

    @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.

  12. btkcodedev commented on Jan 27, 2026

    @btkcodedev
    Contributor

    Thanks @suneox. Awaiting internal team response.

  13. btkcodedev commented on Jan 28, 2026

    @btkcodedev
    Contributor

    @JmillsExpensify Bump on this 🙇

  14. mallenexpensify commented on Jan 31, 2026

    @mallenexpensify
    Contributor

    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

  15. trjExpensify commented on Jan 31, 2026

    @trjExpensify
    Contributor

    approved $250 for @suneox.

  16. btkcodedev commented on Jan 31, 2026

    @btkcodedev
    Contributor

    @mallenexpensify Accepted!
    Thanks!

  17. mallenexpensify commented on Feb 3, 2026

    @mallenexpensify
    Contributor

    @btkcodedev paid, summary updated above. Sorry it took a min.

    Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions