[HOLD #11768] Navigating Back takes the user to the home screen on the web - reported by @parasharrajat

[mvtglobally]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Action Performed:

1. Open the app from the home URL (https://staging.new.expensify.com/).
2. Opening a new Chat from RHN (SearchPage)
3. Navigate to another chat from RHN (SearchPage).
4. Go Back.

Expected Result:

The user should not leave the app.

Actual Result:

User is taken out of the app.

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.1.88-10
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @parasharrajat
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1659433336320769

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @conorpendergrast (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

[Beamanator]

This looks like almost an exact duplicate of #10507 - I think we can close this since #10507 has more details

[parasharrajat]

This is different based on the Reproduction steps. Both have different navigation actions. I mentioned that on slack.

[melvin-bot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.

[marcaaron]

Putting this one on HOLD.

[marcaaron]

Let's leave it open for now we won't be accepting any proposals just yet. Agree it seems similar to the other issue, but it's good to have the different test cases.

[melvin-bot]

Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

10 days overdue. I'm getting more depressed than Marvin.

[parasharrajat]

On Hold.

[melvin-bot]

12 days overdue now... This issue's end is nigh!

[Beamanator]

Not overdue, will demote to weekly

[JmillsExpensify]

Still on hold for navigation.

[JmillsExpensify]

Still on hold for navigation. No ETA.

[JmillsExpensify]

Same same

[JmillsExpensify]

Still on hold.

[JmillsExpensify]

Still on hold

[JmillsExpensify]

Coming off hold very soon!

[JmillsExpensify]

Working on testing this week.

[JmillsExpensify]

Still trying to make time. Low priority.

[JmillsExpensify]

The user should not leave the app.

Re-tested and I can confirm this no longer happens.

[JmillsExpensify]

Payout summary: $250 to @parasharrajat for issue reporting

[JmillsExpensify]

I'm going to close this issue, though please make sure to send a request via NewDot!

[parasharrajat]

Payment requested as per #10506 (comment)

[JmillsExpensify]

$250 payment approved for @parasharrajat based on summary above.