Skip to content

[HOLD for payment 2025-02-05] [HOLD for payment 2025-02-04] Split - Individual split amount field is not aligned correctly #55662

Closed

Description

@lanitochka17

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.0.89-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers): applausetester+100106kh@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to 1:1 DM
  3. Click + > Split expense > Manual
  4. Enter amount > Next

Expected Result:

Individual split amount field will be aligned correctly

Actual Result:

Individual split amount field is not aligned correctly

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence
Bug6722068_1737658465189.20250124_025235.mp4

View all open jobs on GitHub

Activity

  1. melvin-bot commented on Jan 23, 2025

    @melvin-bot

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

  2. melvin-bot commented on Jan 23, 2025

    @melvin-bot

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

  3. github-actions commented on Jan 23, 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.
  4. arosiclair commented on Jan 23, 2025

    @arosiclair
    Contributor

    Reproduced in staging v9.0.89-2 and not in prod v9.0.88-7

    Image

  5. arosiclair commented on Jan 23, 2025

    @arosiclair
    Contributor

    Looks like #55343 is the root cause. Reverting it fixes the issue. cc @Kicu @rayane-djouah @luacmartins

  6. Kicu commented on Jan 24, 2025

    @Kicu
    Contributor

    Thank you for catching this bug, here is a proper fix: #55711

  7. 1 remaining item

  8. arosiclair commented on Jan 24, 2025

    @arosiclair
    Contributor

    Thanks! Fix is no staging so closing this out

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 28, 2025
  10. changed the title [-]Split - Individual split amount field is not aligned correctly[/-] [+][HOLD for payment 2025-02-04] Split - Individual split amount field is not aligned correctly[/+] on Jan 28, 2025
  11. melvin-bot commented on Jan 28, 2025

    @melvin-bot

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

  12. melvin-bot commented on Jan 28, 2025

    @melvin-bot

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

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

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

    • @Kicu does not require payment (Contractor)
  13. changed the title [-][HOLD for payment 2025-02-04] Split - Individual split amount field is not aligned correctly[/-] [+][HOLD for payment 2025-02-05] [HOLD for payment 2025-02-04] Split - Individual split amount field is not aligned correctly[/+] on Jan 29, 2025
  14. melvin-bot commented on Jan 29, 2025

    @melvin-bot

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

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

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

    • @Kicu does not require payment (Contractor)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions