[HOLD for payment 2024-02-20] [$500] LHN - Unable to navigate to workspace settings from bottom tab and from Workspace listing page

[izarutskaya]

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

---

Version Number: 1.4.36-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause-Internal Team
Slack conversation:

Action Performed:

Precondition: a few workspaces should be created

1. Open app
2. Tap on the "Expensify" icon on top left corner
3. Tap on any listed workspace
4. Tap on back button
5. Tap on Chat tab on bottom nav panel
6. Tap on Back button
7. Tap on Settings icon in bottom navigation page
8. Tap on back button
9. Tap on Workspace icon on top left corner
10. Tap on "Expensify"
11. Tap on any listed workspace

Expected Result:

Step 7 and 11: user should be navigated to the workspace

Actual Result:

Step 7 and 11: user navigated on the workspace overview page

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop
• iPad Pro 11" 2020/iPadOS 17.2

Screenshots/Videos

Bug6366118_1706979333594.RPReplay_Final1706941919.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~017b82db16dc264309
• Upwork Job ID: 1753896928387526656
• Last Price Increase: 2024-02-03

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~017b82db16dc264309

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts (External)

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @thienlnam (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[mountiny]

cc @adamgrzybowski Not a blocker, there is a bunch of issues related to ipad specifically, tracking them here https://expensify.slack.com/archives/C036QM0SLJK/p1707137489876029

[jliexpensify]

@mountiny is @adamgrzybowski working on these iPad issues? Should we remove the Help Wanted?

[mountiny]

Yep this is addressed, thanks!

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.40-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [Wave 8] [Ideal Nav] Fix iPad navigation #35845

If no regressions arise, payment will be issued on 2024-02-20. 🎊

For reference, here are some details about the assignees on this issue:

• @allroundexperts requires payment through NewDot Manual Requests

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@allroundexperts] The PR that introduced the bug has been identified. Link to the PR:
• [@allroundexperts] 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:
• [@allroundexperts] 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:
• [@allroundexperts] Determine if we should create a regression test for this bug.
• [@allroundexperts] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@jliexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[jliexpensify]

@allroundexperts does the checklist need to be completed here? Thanks!

[mountiny]

No I think we do not need it here

[mountiny]

Additionally, there is nothing to pay here actually