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-06-27] [$250] The RHN modal is dismissed after clicking incomplete button in task #61907
Version Number: 9.1.44-6 Reproducible in staging?: Y Reproducible in production?: Y 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:@dukenv0307 Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Go to Reports page
Go to Tasks page
Click on completed task
Note that RHN modal is still displayed
On RHN, click on task title > Mark as incomplete button
Expected Result:
The RHN modal is still displayed
Actual Result:
The RHN modal is dismissed
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidencebug.movRecording.1220.mp4
changed the title [-]The RHN modal is dismissed after clicking incomplete button in task[/-][+][$250] The RHN modal is dismissed after clicking incomplete button in task[/+]on May 13, 2025
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
Nope
What alternative solutions did you explore? (Optional)
I'm not sure but opening the detail screen could be a better alternative.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
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: Not a regression. Seems to be very old code and we might not have noticied this issue.
[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: N/A
[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:
Go to Reports page
Go to Tasks page
Click on completed task
Note that RHN modal is still displayed
On RHN, click on task title > Mark as incomplete button
Activity
melvin-bot commentedon May 13, 2025
Triggered auto assignment to @maddylewis (
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.m-natarajan commentedon May 13, 2025
Proposal by @dukenv0307
Proposal
Please re-state the problem that we are trying to solve in this issue.
The RHN modal is dismissed
What is the root cause of that problem?
We dismiss the modal after marking as incompleted. It leads all RHP modals are closed.
App/src/pages/ReportDetailsPage.tsx
Lines 545 to 548 in 12e6cb3
What changes do you think we should make in order to solve the problem?
We should use
Navigation.goBack(backTo);like the way we did withunapproveaction hereApp/src/pages/ReportDetailsPage.tsx
Lines 545 to 548 in 12e6cb3
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None, Navigation issue
What alternative solutions did you explore? (Optional)
[-]The RHN modal is dismissed after clicking incomplete button in task[/-][+][$250] The RHN modal is dismissed after clicking incomplete button in task[/+]melvin-bot commentedon May 13, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021922282923967120988
melvin-bot commentedon May 13, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 (
External)AQIB-NAWAB commentedon May 17, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
The RHN modal is getting closed after clicking on the "Mark as incomplete" button.
What is the root cause of that problem?
The problem is in action function in which we call navigator class function to close the modal.
App/src/pages/ReportDetailsPage.tsx
Lines 513 to 522 in e7f78df
What changes do you think we should make in order to solve the problem?
Instead of calling dismissed function we should call the route back.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
Nope
What alternative solutions did you explore? (Optional)
I'm not sure but opening the detail screen could be a better alternative.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
melvin-bot commentedon May 19, 2025
@abdulrahuman5196 Huh... This is 4 days overdue. Who can take care of this?
31 remaining items
melvin-bot commentedon Jun 27, 2025
Payment Summary
Upwork Job
BugZero Checklist (@maddylewis)
abdulrahuman5196 commentedon Jun 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: Not a regression. Seems to be very old code and we might not have noticied this issue.
[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: N/A
[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 👎
abdulrahuman5196 commentedon Jun 30, 2025
@maddylewis Checklist is complete
melvin-bot commentedon Jun 30, 2025
@maddylewis Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 30, 2025
@maddylewis Whoops! This issue is 2 days overdue. Let's get this updated quick!
maddylewis commentedon Jun 30, 2025
Payment Overview + Final To-Dos:
JmillsExpensify commentedon Jul 14, 2025
$250 approved for @abdulrahuman5196
quinthar commentedon Sep 15, 2025
Approved $250 to @dukenv0307