Skip to content

[$500] mweb/Chrome - Expense - App returns to LHN when tapping back button after refreshing request page #35084

Closed

Description

@lanitochka17

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.31-2
Reproducible in staging?: Y
Reproducible in production?: Y
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:

Issue found when executing PR #34236

Action Performed:

  1. Go to workspace chat
  2. Create a manual request
  3. Go to request details page
  4. Refresh the page
  5. Tap on the back button

Expected Result:

App returns to expense report

Actual Result:

App returns to LHN

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

Add any screenshot/video evidence

Bug6353492_1706117862008.1000009580.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0183615511eed125fe
  • Upwork Job ID: 1750220362340155392
  • Last Price Increase: 2024-02-14

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 24, 2024
  2. melvin-bot commented on Jan 24, 2024

    @melvin-bot
  3. changed the title [-]mweb/Chrome - Expense - App returns to LHN when tapping back button after refreshing request page[/-] [+][$500] mweb/Chrome - Expense - App returns to LHN when tapping back button after refreshing request page[/+] on Jan 24, 2024
  4. melvin-bot commented on Jan 24, 2024

    @melvin-bot

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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 24, 2024
  6. melvin-bot commented on Jan 24, 2024

    @melvin-bot

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

  7. FitseTLT commented on Jan 24, 2024

    @FitseTLT
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Expense - App returns to LHN when tapping back button after refreshing request page

    What is the root cause of that problem?

    It is because ROUTES.HOME is our fallback here

    onBackButtonPress={() => Navigation.goBack(ROUTES.HOME, false, true)}
    />

    What changes do you think we should make in order to solve the problem?

    We should give the parentReport route as a fallback

                        onBackButtonPress={() => Navigation.goBack(ROUTES.REPORT_WITH_ID.getRoute(parentReport.reportID), false, true)}
    
    

    What alternative solutions did you explore? (Optional)

  8. parasharrajat commented on Jan 24, 2024

    @parasharrajat
    Member

    Hmm! These kinds of issues are always a headache.

    @FitseTLT Can you try playing around with different ways of navigation and see what is expected from this button in those cases.

    It would be great if you can present that list here.

  9. FitseTLT commented on Jan 24, 2024

    @FitseTLT
    Contributor

    different ways of navigation

    ????

  10. parasharrajat commented on Jan 24, 2024

    @parasharrajat
    Member

    Try navigating to expense reports in different ways.

    1. Directly via URL.
    2. On Large screens Web.
    3. ON smaller screens.
    4. Via deeplink.

    etc.

  11. FitseTLT commented on Jan 24, 2024

    @FitseTLT
    Contributor
    1. Directly via URL - It should go back to the parent report
    2. On Large screens Web - It doesn't display so no worries here
    3. ON smaller screens - It applies to small screens only 👍
    4. Via deeplink ( I assume the link was a message on another report chat) - it should go back to the original report from which the link was clicked.

    The only odd case is (4). If we should consider achieving that we need to pass as a fallback route the previous screen/route and if it doesn't exist (in the case of refreshing the page ) we will fallback to the parent report.

  12. 15 remaining items

  13. melvin-bot commented on Feb 7, 2024

    @melvin-bot

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

  14. melvin-bot commented on Feb 8, 2024

    @melvin-bot

    @sonialiap, @parasharrajat 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  15. ishpaul777 commented on Feb 8, 2024

    @ishpaul777
    Contributor
  16. removed their assignment
    on Feb 8, 2024
  17. ishpaul777 commented on Feb 9, 2024

    @ishpaul777
    Contributor

    I think we should hold for #36050, maybe this PR resolves the issue

  18. melvin-bot commented on Feb 12, 2024

    @melvin-bot

    @sonialiap Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  19. melvin-bot commented on Feb 14, 2024

    @melvin-bot

    @sonialiap this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

  20. melvin-bot commented on Feb 14, 2024

    @melvin-bot

    @sonialiap Eep! 4 days overdue now. Issues have feelings too...

  21. melvin-bot commented on Feb 14, 2024

    @melvin-bot

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

  22. sonialiap commented on Feb 15, 2024

    @sonialiap
    Contributor

    I cannot reproduce. I think #36050 may have solved this. Please reopen if you can reproduce

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

Metadata

Metadata

Assignees

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions