Skip to content

[$250] Group chat - User can return to group chat after leaving the group chat via back button #40474

Closed

Description

@m-natarajan

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.63-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: n/a
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 FAB > Start chat.
  3. Create a group chat.
  4. Tap on the chat header.
  5. Tap Leave.
  6. Tap on the back button twice.

Expected Result:

App will not return to the group chat after user leaves the group.

Actual Result:

App returns to the group chat which is now flickering in iOS
Skeleton view in Android
hmm it is not there page in web

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

Bug6453676_1713449035829.RPReplay_Final1713448827.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01fa7d2f8d25655a13
  • Upwork Job ID: 1781033856171855872
  • Last Price Increase: 2024-04-18
  • Automatic offers:
    • Ollyws | Reviewer | 0
    • neonbhai | Contributor | 0
    • eh2077 | Contributor | 0

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Apr 18, 2024

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

  4. github-actions commented on Apr 18, 2024

    @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.
  5. m-natarajan commented on Apr 18, 2024

    @m-natarajan
    Author

    @laurenreidexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  6. m-natarajan commented on Apr 18, 2024

    @m-natarajan
    Author

    We think this bug might be related to #vip-vsb

  7. neonbhai commented on Apr 18, 2024

    @neonbhai
    Contributor

    Proposal

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

    Group chat - User can return to group chat after leaving the group chat via back button

    What is the root cause of that problem?

    When navigating away from the group chat using navigateToMostRecentReport, we don't replace the last page from navigation history, allowing us to return on pressing back

    Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(lastAccessedReportID ?? ''));

    and
    Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(chat?.reportID));

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

    We should pass CONST.NAVIGATION.TYPE.UP as the second param when navigating away in navigateToMostRecentReport

    Note: navigateToMostRecentReport is called only leaveGroup and leaveRoom so navigation type need not be enabled by a prop

    Alternatively

    We may pass CONST.NAVIGATION.TYPE.FORCED_UP as the navigation type

  8. marcaaron commented on Apr 18, 2024

    @marcaaron
    Contributor

    Hmm this one looks bad and seems like a good Deploy Blocker. @thienlnam I can take this from you.

  9. 13 remaining items

  10. laurenreidexpensify commented on Apr 29, 2024

    @laurenreidexpensify
    Contributor

    Just to confirm - this was the PR right, #40563, and that went to prod on 22 April, so this is due for payment today 29 April? cc @marcaaron @neonbhai @Ollyws

  11. neonbhai commented on Apr 29, 2024

    @neonbhai
    Contributor

    @laurenreidexpensify yes, the PR was combined with another PR to get it CP'ed quick. And you're right, it is due for payment today

  12. Ollyws commented on Apr 29, 2024

    @Ollyws
    Contributor

    I didn't review this one though so no payment required for me.

  13. marcaaron commented on Apr 29, 2024

    @marcaaron
    Contributor

    It was reviewed by @eh2077 however so I'll add them here.

  14. assigned and unassigned on Apr 29, 2024
  15. melvin-bot commented on Apr 29, 2024

    @melvin-bot

    📣 @eh2077 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  16. laurenreidexpensify commented on May 7, 2024

    @laurenreidexpensify
    Contributor

    Payment Summary:

  17. laurenreidexpensify commented on May 7, 2024

    @laurenreidexpensify
    Contributor

    Apols for the delay here folks! Everyone is paid now

  18. laurenreidexpensify commented on May 7, 2024

    @laurenreidexpensify
    Contributor

    No regression test as caught by internal applause team, closing

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions