Skip to content

[$250] Incorrect return navigation after inviting user when sharing with accountant #58204

Closed

Description

@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.1.11-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp https://expensify.testrail.io/index.php?/tests/view/5724916
Email or phone of affected tester (no customers): applausetester+ps309@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.3
App Component: Money Requests

Action Performed:

Precondition:

  • Account has self DM.
  1. Launch ND or hybrid app.
  2. Go to Settings.
  3. Go to Inbox.
  4. Go to self DM.
  5. Submit a manual expense to self DM.
  6. Tap Share it with my accountant.
  7. Select any workspace if there is existing workspace.
  8. Enter merchant and submit the expense.
  9. On invite page, select any user and invite.
  10. Tap app back buton.
  11. Note that app returns to share list.
  12. Tap app back button to return to workspace chat.
  13. Tap app back button to return to self DM.
  14. Tap app back button again.

Expected Result:

App will return to Inbox.

Actual Result:

App returns to Settings (from Step 2).

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6767240_1741687294049.ScreenRecording_03-11-2025_17-56-09_1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021899471330703030772
  • Upwork Job ID: 1899471330703030772
  • Last Price Increase: 2025-03-25
Issue OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 11, 2025
  2. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  3. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 11, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 11, 2025

    @github-actions
    Contributor

    👋 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.
  6. rlinoz commented on Mar 11, 2025

    @rlinoz
    Contributor

    Very specific flow, so I will remove the blocker.

  7. added and removed on Mar 11, 2025
  8. 26 remaining items

  9. melvin-bot commented on Mar 25, 2025

    @melvin-bot

    @rlinoz @abdulrahuman5196 @VictoriaExpensify this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  10. truph01 commented on Mar 25, 2025

    @truph01
    Contributor

    Maybe this PR fixed this issue

  11. abdulrahuman5196 commented on Mar 25, 2025

    @abdulrahuman5196
    Contributor

    Maybe this PR fixed this issue

    Sorry did you mean the question i asked or this issue is not reproducible anymore?

  12. melvin-bot commented on Mar 25, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  13. mvtglobally commented on Mar 26, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (First week)

  14. mallenexpensify commented on Mar 26, 2025

    @mallenexpensify
    Contributor

    Maybe this LOW, per the status options below. Bump up if you think it should be.

    • CRITICAL - UX Reliability, API Reliability and Performance bugs that are noticeable for a majority of users
    • HIGH -  UX Reliability, API Reliability and Performance issues that are part of main flows and affect a subset of users
    • MEDIUM - Debugging Tools to help make fixing existing bugs easier and getting fixes to customers faster and Architectural Improvements to the underlying framework and design of the app to improve performance, scalability, and maintainability
    • LOW - Not very noticeable UX Reliability, API Reliability or Performance issues that only affect a single user or subset of users
  15. rlinoz commented on Mar 27, 2025

    @rlinoz
    Contributor

    Yeah, I can't repro this anymore either.

  16. melvin-bot commented on Mar 31, 2025

    @melvin-bot

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

  17. rlinoz commented on Mar 31, 2025

    @rlinoz
    Contributor

    Closing because it is not reproducible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions