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
Reports - "Pay" button changes size after paying expense for the first time. #65130
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:
Open the Expensify app.
Navigate to "Workspaces" and create a new workspace.
Open "Workflows" and disable delayed submissions and approvals.
Navigate to workspace chat.
Submit a manual expense.
Navigate to "Reports"
Check the size of the "Pay" button.
Return to chat and mark the expense as paid.
Open the expense and cancel the payment.
Return to "Reports"
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.
👋 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.
@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.
Activity
melvin-bot commentedon Jun 28, 2025
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.melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 28, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 28, 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:
nlemma commentedon Jun 28, 2025
@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.
hungvu193 commentedon Jun 28, 2025
I will handle this one. It came from my previous PR. I'll prepare a PR soon.
joekaufmanexpensify commentedon Jun 30, 2025
Closing as we are reverting 👍
melvin-bot commentedon Jun 30, 2025
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.
melvin-bot commentedon Jun 30, 2025
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.
IuliiaHerets commentedon Jun 30, 2025
Issue is not reproducible on Windows 11/ Chrome in v9.1.72-9
65130.mp4
getusha commentedon Jul 2, 2025
Noting this is expected @IuliiaHerets