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 - Nothing happens after tapping Mark as paid #65118
Version Number: 9.1.72-0 Reproducible in staging?: Yes Reproducible in production?: No 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):jsdonisjondjosd@gmail.com Issue reported by: Applause Internal Team Device used: Samsung Galaxy Z Fold 4 / Android 15 App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Tap Submit and Approve.
Go to Reports.
Tap Pay.
Select Mark as paid.
Expected Result:
Expense will be paid.
Actual Result:
Nothing happens after tapping Mark as paid.
This issue also happens when tapping Pay button on the second expense after marking as paid on the first expense.
👋 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.
Feat standardize pay button #56838: Completely refactors SettlementButton, IOU/Report payment logic and Mark-as-paid flow, making it the most likely cause of the button now doing nothing.
LoadingBar rendering improvements #63025: PR 63025 refactored MoneyRequestHeader (where the Pay → Mark as Paid menu lives), so its new loading-bar logic likely disrupted the Pay/Mark-as-paid action handler, resulting in no response when the option is tapped.
Activity
melvin-bot commentedon Jun 28, 2025
Triggered auto assignment to @laurenreidexpensify (
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 @yuwenmemon (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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:
melvin-bot commentedon Jun 28, 2025
💬 A slack conversation has been started in #expensify-open-source
8 remaining items
BlameGPT commentedon Jun 30, 2025
Possible culprit PRs for this issue
If not above, check these
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.
luacmartins commentedon Jun 30, 2025
We reverted the offending PR #56838
IuliiaHerets commentedon Jun 30, 2025
Issue not repro on Xioami Poco X4 / A13 / Chrome, build v9.1.72-9
No mark as paid option, only
Payoption in ReportScreenrecorder-2025-06-30-13-06-34-711.mp4
puneetlath commentedon Jun 30, 2025
Great, closing!
fix Expensify#65118: fix unresponsive pay action on search