Skip to content

[Due for payment 2026-01-07] Onboarding - RHP Opens Multiple Concierge Pages Instead of Existing Tab #78446

Closed

Description

@jponikarchuk

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: v9.2.87-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #78352
Email or phone of affected tester (no customers): sintayewhaylu01@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Critical User Impact
Device used: Windows 10 /Chrome
App Component: Other

Action Performed:

  1. Navigate to http://staging.new.expensify.com/r/6177391126570771
  2. Click Concierge.
  3. Sign in.
  4. Click Concierge in header again.
  5. Click RHP Sign in again.
  6. Click RHP back arrow 2 times.

Expected Result:

When RHP is clicked, it should open the first existing Concierge tab/page.

Actual Result:

When RHP is clicked, multiple Concierge pages open repeatedly instead of returning to the first open Concierge page.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

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

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78352

  3. melvin-bot commented on Dec 25, 2025

    @melvin-bot

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

  4. github-actions commented on Dec 25, 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.
  5. 30 remaining items

  6. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  7. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-01-07. 🎊

    For reference, here are some details about the assignees on this issue:

  8. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    @aimane-chnaif @trjExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  9. trjExpensify commented on Jan 7, 2026

    @trjExpensify
    Contributor

    👋 checklist time here, @aimane-chnaif.

  10. aimane-chnaif commented on Jan 7, 2026

    @aimane-chnaif
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/78352/changes#r2670331053

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Sign out of the app or open a fresh browser session
    2. Navigate to a public room via direct link (without signing in)
    3. Verify the help button is NOT visible
    4. Verify the RHP is NOT displayed
    5. Verify the RHP is closed by default

    Do we agree 👍 or 👎

  11. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@trjExpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. trjExpensify commented on Jan 9, 2026

    @trjExpensify
    Contributor

    Ah, @aimane-chnaif... are you being paid centrally for this sidepane project?

  13. aimane-chnaif commented on Jan 9, 2026

    @aimane-chnaif
    Contributor

    Not project but we can close this as I already got paid in #78505 for the same PR.

  14. trjExpensify commented on Jan 12, 2026

    @trjExpensify
    Contributor

    Okay cool, sounds good. Closing!

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions