Skip to content

Reports - "Pay" button changes size after paying expense for the first time. #65130

Closed

Description

@nlemma

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.1.72-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - feature not available on prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #56838
Email or phone of affected tester (no customers): ibellicotest+1165@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome (mWeb - Hybrid App) / Windows 10 - Chrome
App Component: Search

Action Performed:

  1. Open the Expensify app.
  2. Navigate to "Workspaces" and create a new workspace.
  3. Open "Workflows" and disable delayed submissions and approvals.
  4. Navigate to workspace chat.
  5. Submit a manual expense.
  6. Navigate to "Reports"
  7. Check the size of the "Pay" button.
  8. Return to chat and mark the expense as paid.
  9. Open the expense and cancel the payment.
  10. Return to "Reports"
  11. Note that now, the "Pay" button has a bigger size than before.

Expected Result:

"Pay" button size on expense preview on "Reports" should always be the same.

Actual Result:

The size of the "Pay" button on expense preview on "Reports", changes size after paying an expense for the first time and cancelling the payment.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6872179_1751093554045.Size.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

    Triggered auto assignment to @strepanier03 (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 Jun 28, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jun 28, 2025

    @melvin-bot

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

  5. github-actions commented on Jun 28, 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. nlemma commented on Jun 28, 2025

    @nlemma
    Author

    @strepanier03 FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. hungvu193 commented on Jun 28, 2025

    @hungvu193
    Contributor

    I will handle this one. It came from my previous PR. I'll prepare a PR soon.

  8. joekaufmanexpensify commented on Jun 30, 2025

    @joekaufmanexpensify
    Contributor

    Closing as we are reverting 👍

  9. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  10. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. IuliiaHerets commented on Jun 30, 2025

    @IuliiaHerets

    Issue is not reproducible on Windows 11/ Chrome in v9.1.72-9

    65130.mp4
  12. getusha commented on Jul 2, 2025

    @getusha
    Contributor

    Noting this is expected @IuliiaHerets

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions