Skip to content

[Due for payment 2026-09-22] [$250] Android - Split - Percentage input has to be focused twice to be able to edit it. #78089

Description

@jponikarchuk

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): ibellicotest+2230@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Tap on "More" > "Split"
  6. Switch to "Percentage" tab.
  7. Tap on the percentage input of any split to edit it.
  8. Note that keyboard opens but input is automatically unfocused.
  9. Tap on input again.
  10. Note that now, input remains focused.

Expected Result:

Percentage input should remain focused after user taps on it to edit it.

Actual Result:

Percentage tab has to be tapped twice to be able to edit it. The first time that the user taps on it, input gets focused and unfocused automatically, despite keyboard being opened, and user is unable to edit it.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022003264354527804617
  • Upwork Job ID: 2003264354527804617
  • Last Price Increase: 2025-12-30
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @TaduJR

Activity

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

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (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 @carlosmiceli (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. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 19, 2025
  7. 171 remaining items

  8. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. mallenexpensify commented on Sep 24, 2026

    @mallenexpensify
    Contributor

    Bumped to weekly, tag me when the bug's resolved and propose payment amount. Thx

  10. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    @TaduJR Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. brunovjk commented on Oct 1, 2026

    @brunovjk
    Contributor

    Notoverdue

  12. melvin-bot commented on Oct 2, 2026

    @melvin-bot

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

  13. melvin-bot commented on Oct 3, 2026

    @melvin-bot

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

  14. melvin-bot commented on Oct 6, 2026

    @melvin-bot

    @TaduJR 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  15. melvin-bot commented on Oct 8, 2026

    @melvin-bot

    @TaduJR 10 days overdue. Is anyone even seeing these? Hello?

  16. TaduJR commented on Oct 9, 2026

    @TaduJR
    Contributor

    Not overdue. On HOLD for #101157

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

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions