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
[Due for payment 2025-04-30] [$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in #59688
Version Number: Reproducible in staging?: Reproducible in production?: If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@aldo-expensify Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Do a manual request from userA to userB
Make userB mark the request as paid elsewhere
The request from userA's perspective should look like the screenshot (there is a section userA -> userB )
Log out userA and log back in
Go to the money request preview
Expected Result:
Requester -> Payer section displayed after user login
Actual Result:
Requester -> Payer section not displayed after user login
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
changed the title [-]DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/-][+][$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/+]on Apr 8, 2025
changed the title [-][$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/-][+][Due for payment 2025-04-30] [$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/+]on Apr 23, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.31-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dominictb@adelekennedy@dominictb The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
tableReportView beta enabled
Test:
Submit an expense on WS chat
Verify that on WS chat, the money request preview doesn't show From/To fields
Do a manual request from userA to userB in DM
Make userB mark the request as paid elsewhere
Verify From/To fields show in money request preview
Log out userA and log back in
Go to the money request preview
Verify From/To fields show in money request preview
Activity
melvin-bot commentedon Apr 4, 2025
Triggered auto assignment to @adelekennedy (
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.MelvinBot commentedon Apr 4, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
dominictb commentedon Apr 8, 2025
I can reproduce with the steps provided in OP:
@adelekennedy Please assign me as C+ as per this Slack post.
melvin-bot commentedon Apr 8, 2025
@adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Apr 8, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021909642168327029806
[-]DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/-][+][$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/+]22 remaining items
[-][$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/-][+][Due for payment 2025-04-30] [$250] DEV- Requester -> Payer section goes missing from payed money request preview after logging out and logging back in[/+]melvin-bot commentedon Apr 23, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Apr 23, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.31-3 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-04-30. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 23, 2025
@dominictb @adelekennedy @dominictb The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
adelekennedy commentedon Apr 30, 2025
Payment Summary
Contributor: @nkdengineer paid $250 via Upwork
Contributor+: @dominictb paid $250 via Upwork
adelekennedy commentedon Apr 30, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
adelekennedy commentedon Apr 30, 2025
Payment made - just checklist above
dominictb commentedon May 5, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/57614/files#r2073860760
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: NA
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
tableReportViewbeta enabledTest:
Do we agree 👍 or 👎