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
[HOLD for payment 2023-10-16] [$500] Chat - LHN disappears after leaving a thread #28087
LHN disappears, on mobile web, you can't go back to LHN
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.73.0 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 Notes/Photos/Videos: Any additional supporting documentation
Please re-state the problem that we are trying to solve in this issue.
LHN disappears, on mobile web, you can't go back to LHN
What is the root cause of that problem?
Here we're force-navigate to the report screen, which will replace the current Home screen and cause the LHN to disappear.
What changes do you think we should make in order to solve the problem?
We should move this block to above this block. Since we'll be navigating to the parent report screen anyway so no need to go back to home screen before that.
What alternative solutions did you explore? (Optional)
We can use push navigate here rather than force navigate.
A discussion in #expensify-bugs 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: This is an edge case with navigation, there isn't much we could do in terms of improving our checklists/processes besides more thorough testing
Determine if we should create a regression test for this bug.
Is it easy to test for this bug? Yes
Is the bug related to an important user flow? Yes
Is it an impactful bug? Yes
I think we should implement a regression test here, the bug is pretty severe
Activity
[-]Chat - LHN disappears after leaving a thread[/-][+][$500] Chat - LHN disappears after leaving a thread[/+]melvin-bot commentedon Sep 24, 2023
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Sep 24, 2023
Job added to Upwork: https://www.upwork.com/jobs/~012668216660b5477f
melvin-bot commentedon Sep 24, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)melvin-bot commentedon Sep 24, 2023
Triggered auto assignment to @dylanexpensify (
External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.melvin-bot commentedon Sep 24, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (
External)RichardPickman commentedon Sep 24, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
Left Handed Menu dissapears on "Leave thread" action.
What is the root cause of that problem?
There is no return statement, when code reaches on of the checks, thats the reason why code gets into second if statement
What changes do you think we should make in order to solve the problem?
Add return statement in file src/libs/actions/Report.js on line 1891:
Before return;
before_return.mp4
After return;
after_return.mp4
dukenv0307 commentedon Sep 25, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
LHN disappears, on mobile web, you can't go back to LHN
What is the root cause of that problem?
Here we're force-navigate to the report screen, which will replace the current
Homescreen and cause the LHN to disappear.What changes do you think we should make in order to solve the problem?
We should move this block to above this block. Since we'll be navigating to the parent report screen anyway so no need to go back to home screen before that.
What alternative solutions did you explore? (Optional)
We can use
pushnavigate here rather than force navigate.34 remaining items
dylanexpensify commentedon Oct 18, 2023
payment upcoming!
eVoloshchak commentedon Oct 19, 2023
Is it easy to test for this bug? Yes
Is the bug related to an important user flow? Yes
Is it an impactful bug? Yes
I think we should implement a regression test here, the bug is pretty severe
eVoloshchak commentedon Oct 19, 2023
Regression Test Proposal
reply in threadof this messageDetailsmenuDo we agree 👍 or 👎
melvin-bot commentedon Oct 23, 2023
@arosiclair, @eVoloshchak, @bfitzexpensify, @dylanexpensify, @dukenv0307 Whoops! This issue is 2 days overdue. Let's get this updated quick!
JmillsExpensify commentedon Oct 23, 2023
$750 approved for @eVoloshchak based on summary above.
bfitzexpensify commentedon Oct 24, 2023
Regression test steps look good, proposed they be added in https://github.com/Expensify/Expensify/issues/329592.
Payment made to @dukenv0307, just need to finalize payment for @bernhardoj for the reporter role.
bfitzexpensify commentedon Oct 27, 2023
OK, all done here, thanks everyone.