Split Bill- Multiple tap of back button left to " Details", user navigated to "LHN"

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Tap Fab
3. Tap split bill
4. Enter amount
5. Tap Next
6. Select any 2 users
7. Tap next
8. Tap Split amount
9. Tap on header
10. Tap on the side, adjacent to each user, to note its profile page opening
11. Tap back button left to "details"

Expected Result:

On single tap of back button left to " Details" , user must be navigated to "conversation" page

Actual Result:

User has to tap many times the back button next to "details", then instead of navigating to conversation page, user is directly navigated 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.53.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug6161398_splitbill_header.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[sakluger]

I've seen several issues with navitaging back from a sub-menu. I'd like to check if this related to any of the following:

#23796
#23758
#23725

@mountiny on #23725, you mentioned looking at as a general solution as part of the navigation follow ups tracking project. Do you think this issue should go there too?

[mountiny]

@adamgrzybowski @WoLewicki Could you look into this one?

[adamgrzybowski]

I have a problem with reproducing this one. I am getting its not here page after splitting the bill on Stagin. Any idea what that may be? BTW I tested this on my local main and it works fine. Can't reproduce this bug locally.

[adamgrzybowski]

Okay I was able to open this on staging and still can't reproduce the bug

Screen.Recording.2023-08-16.at.19.55.24.mov

EDIT:
Also tested on physical android with the same results

[mountiny]

@lanitochka17 @kavimuru Could you reproduce again? Otherwise lets close this @sakluger

[sakluger]

I'm going to close for now since it doesn't seem to be reproduceable on the latest build.