Skip to content

Fix/92672 anon public room lhn#93048

Closed
yusufdeveloper2903 wants to merge 2 commits into
Expensify:mainfrom
yusufdeveloper2903:fix/92672-anon-public-room-lhn
Closed

Fix/92672 anon public room lhn#93048
yusufdeveloper2903 wants to merge 2 commits into
Expensify:mainfrom
yusufdeveloper2903:fix/92672-anon-public-room-lhn

Conversation

@yusufdeveloper2903

Copy link
Copy Markdown
Contributor

Explanation of Change

An anonymous session can only ever access public rooms, and such a room's notification preference defaults to hidden. In the LHN filter (shouldDisplayReportInLHN in SidebarUtils), a hidden report only survives when one of the shouldOverrideHidden conditions is true — and for an anonymous user the only one that ever applied was isFocused. So the public room stayed in the Inbox only while it was the focused report. The moment the anon user opened a thread inside the room, the thread became the focused report, the public room was no longer focused, isHidden && !shouldOverrideHidden became true, and the room was dropped from the Inbox — collapsing it to the "Woohoo! All caught up" empty state and leaving the anon user unable to return to the room.

This PR adds a new shouldOverrideHidden condition so a public room is never hidden from an anonymous user's LHN just because it isn't the focused report:

(isPublicRoom(report) && isAnonymousUser())

This pairs isPublicRoom with isAnonymousUser() exactly the way ReportUtils already gates anon-only public-room behaviour elsewhere (e.g. canLeaveChat). It is a display-only predicate — it does not mutate any report/Onyx data or notification preference — so there are no side effects on unread/GBR or leave-room logic. After sign-in isAnonymousUser() becomes false, the override no longer applies, and the existing flow (#91931) re-fetches the room with a real notification preference, so there is no regression and no double-handling.

Fixed Issues

$ #92672
PROPOSAL: #92672 (comment)

Tests

  1. Log out of the app so you are an anonymous user.
  2. Open a public room as the anonymous user (e.g. open the public room deep link / URL …/r/<publicRoomID>).
  3. Verify the public room appears in the Inbox/LHN.
  4. Inside the public room, open a thread (tap a message that has replies, e.g. "1 Reply").
  5. Verify the public room remains in the Inbox/LHN and the Inbox does not collapse to the "Woohoo! All caught up" empty state.
  6. Tap the public room in the LHN and verify you can navigate back to it.
  7. Sign in and verify the Inbox/LHN still behaves normally (no duplicate or stuck public room).
  • Verify that no errors appear in the JS console

Offline tests

This change is a purely client-side display predicate, so it behaves identically offline.

  1. As an anonymous user, open a public room and confirm it shows in the Inbox/LHN.
  2. Turn off your network connection.
  3. Open a thread inside the public room.
  4. Verify the public room is still present in the Inbox/LHN while offline.

QA Steps

  1. On staging, log out so you are an anonymous user.
  2. Open this public room link as the anonymous user: https://staging.new.expensify.com/r/1540486774487195
  3. Verify the public room appears in the Inbox.
  4. Open a thread inside the public room (tap a message with replies).
  5. Verify the public room remains in the Inbox and you do not see the "Woohoo! All caught up" empty state.
  6. Verify you can still navigate back to the public room from the Inbox.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Before fix:

Before-fix-android.mp4

After fix:

After-fix-android.mp4
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Before fix:

Before-fix.Chrome-mac.mp4

After fix:

After-fix.Chrome-mac.mp4

yusufdeveloper2903 and others added 2 commits June 9, 2026 13:58
An anonymous session can only access public rooms, whose notification
preference defaults to `hidden`. Previously a public room only survived
the LHN filter while it was the focused report, so opening a thread inside
the room (which steals focus) dropped the room from the Inbox, leaving the
anon user unable to return to it.

Add an override in `shouldDisplayReportInLHN` so a public room stays in the
LHN for anonymous users regardless of focus, mirroring how ReportUtils
already gates anon-only public-room behaviour (e.g. canLeaveChat).

Fixes Expensify#92672

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@yusufdeveloper2903 yusufdeveloper2903 requested review from a team as code owners June 9, 2026 11:33
@melvin-bot melvin-bot Bot requested review from brunovjk and flaviadefaria and removed request for a team June 9, 2026 11:33
@melvin-bot

melvin-bot Bot commented Jun 9, 2026

Copy link
Copy Markdown

@brunovjk Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot Bot requested review from a team and trjExpensify and removed request for a team June 9, 2026 11:33
@codecov

codecov Bot commented Jun 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/libs/SidebarUtils.ts 80.99% <100.00%> (+0.03%) ⬆️
...icialOwnerInfo/BeneficialOwnerDetailsFormPages.tsx 0.00% <0.00%> (ø)
... and 65 files with indirect coverage changes

function BeneficialOwnerDetailsFormPages({stepNames, policyID, onFinished, backTo}: BeneficialOwnerDetailsFormPagesProps) {
const {translate} = useLocalize();
const [reimbursementAccountDraft] = useOnyx(ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM_DRAFT);
const [reimbursementAccount] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-11 (docs)

useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT) subscribes to the entire reimbursement account object, but getCurrencyForNonUSDBankAccount only reads reimbursementAccount?.achData?.country (a single nested field). This causes the component to re-render whenever any field on the reimbursement account changes.

Use a selector to extract only the needed field:

const [reimbursementAccountCountry] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT, {
    selector: (account) => account?.achData?.[INPUT_IDS.ADDITIONAL_DATA.COUNTRY],
});

Then pass this value directly instead of the full object, or adjust getCurrencyForNonUSDBankAccount to accept the country string.


Reviewed at: e420185 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

const {translate} = useLocalize();
const [reimbursementAccountDraft] = useOnyx(ONYXKEYS.FORMS.REIMBURSEMENT_ACCOUNT_FORM_DRAFT);
const [reimbursementAccount] = useOnyx(ONYXKEYS.REIMBURSEMENT_ACCOUNT);
const [policy] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-11 (docs)

useOnyx(ONYXKEYS.COLLECTION.POLICY${policyID}) subscribes to the entire policy object, but getCurrencyForNonUSDBankAccount only reads policy?.outputCurrency (a single string field). This causes the component to re-render whenever any policy field changes.

Use a selector to extract only the needed field:

const [outputCurrency] = useOnyx(`${ONYXKEYS.COLLECTION.POLICY}${policyID}`, {
    selector: (policy) => policy?.outputCurrency,
});

Then pass this value directly instead of the full policy object, or adjust getCurrencyForNonUSDBankAccount to accept the currency string.


Reviewed at: e420185 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant