[$250] [Due for payment 2025-02-26] [Navigation] Subscription - Back button on subscription leads to settings when opened from Concierge chat

[IuliiaHerets]

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: 9.0.98-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): Ibellicotest+158@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola Moto G60 - Android 12 - Chrome
App Component: Other

Action Performed:

1. Open the Expensify app.
2. Open Concierge chat.
3. Tap on "Claim Offer" on the top of the screen.
4. Once redirected to "Subscription" tap on the back button on the top left corner.

Expected Result:

The user should land on Concierge chat again after using the back button.

Actual Result:

User lands on "Settings" when using back button on Subscription page, despite having entered from "Claim Offer" button on Concierge chat.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6741586_1739430814082.cfab8c5f-33a8-495e-a349-57eca5dc4a65.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @garrettmknight

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021892121047231484020
• Upwork Job ID: 1892121047231484020
• Last Price Increase: 2025-02-19

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[parasharrajat]

It may be related to new navigation changes