iOS Hold - App returns to Hold - reason page when tapping on back button after holding expense

[m-natarajan]

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

---

issue found when validating #44880
Version Number: 9.0.7-4
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:

1. Launch New Expensify app.
2. Go to workspace chat that has no unsettled expense.
3. Submit an expense.
4. Tap on the expense preview to go to expense report.
5. Tap on the report header.
6. Tap Hold.
7. Enter a reason and save it.
8. Tap on the back button on transaction thread.

Expected Result:

App will return to the previous page (main chat or expense report).

Actual Result:

App returns to Hold - reason page when tapping on back button after holding an expense.

NOTE: This issue only happens when there is only one expense in the combined report.

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

Screenshots/Videos

Bug6543364_1721089776683.RPReplay_Final1721089421.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @hayata-suenaga (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (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.

[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.

[dominictb]

The same RCA with #45443.

[hayata-suenaga]

looks like a PR was created and the issue is tracked here

removing the deploy blocker from this issue

[joekaufmanexpensify]

@hayata-suenaga if this issue has the same RCA as the other one and a PR is up, should we just close this one?

[joekaufmanexpensify]

Bump @hayata-suenaga for when you have a sec

[hayata-suenaga]

yes I think we can close this one 😄

[joekaufmanexpensify]

Sweet. TY!