Skip to content

Improve ShouldReportBeInOptionList function#81551

Merged
mountiny merged 7 commits intoExpensify:mainfrom
callstack-internal:eliran/perf-improve-reportToBeInOptionList
Feb 15, 2026
Merged

Improve ShouldReportBeInOptionList function#81551
mountiny merged 7 commits intoExpensify:mainfrom
callstack-internal:eliran/perf-improve-reportToBeInOptionList

Conversation

@elirangoshen
Copy link
Contributor

@elirangoshen elirangoshen commented Feb 5, 2026

Explanation of Change

Fixed Issues

$#81900
PROPOSAL: ShouldReportBeInOptionList improve

This pr improve ShouldReportBeInOptionList performance by reordering the actions to create more cheap early exists and use caching for repeatable expensive operations

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console
  1. Basic LHN Visibility (Default / Most Recent Mode)

Open the app in Default mode (not Focus/GSD mode).
Verify that all expected chats appear: DMs, group chats, workspace rooms, policy expense chats, task reports, expense requests.
Verify the currently viewed report is always highlighted/visible in the LHN.
Navigate between different reports and confirm the LHN selection follows correctly.

  1. Focus Mode
    Switch to Focus mode
    Verify that only unread chats appear (and muted chats do NOT).
    Send a message in a chat from another account, then check that it appears as unread in Focus mode.
    Read the chat, and confirm it disappears from Focus mode.
    Verify that a brand new report that has never been read (no lastReadTime) appears as unread in Focus mode. (This is the isUnread change.)

  2. Currently Focused Report
    In Focus mode, navigate to a report that is read (not unread).
    Confirm it still appears in the LHN because it's the currently focused report.
    Navigate away from it, and confirm it disappears from the LHN (since it's read and no longer focused).

  3. Chat Threads
    Open a chat thread that has replies — it should appear in the LHN.
    Find an empty chat thread (no replies, just the parent message) — it should not appear in the LHN.
    Delete the parent message of a thread with no replies — the thread should not appear.
    Open a thread where the parent message is pending deletion — it should not appear.

  4. Pinned Reports
    Pin a report — confirm it appears in LHN in both Default and Focus modes.
    Unpin it — confirm normal visibility rules apply again.

  5. Reports with Drafts
    Start typing a message in a chat (create a draft) but don't send it.
    Confirm the report appears in the LHN (both modes) with the draft indicator.

  6. Self DM
    Verify the Self DM (chat with yourself) appears correctly in the LHN.

  7. System Chat
    If you have a system chat (notifications account), verify it appears correctly.

  8. Archived Reports
    Archive a report.
    In Default mode, confirm it still appears in the LHN.
    In Focus mode, confirm it only appears if unread.

  9. Empty Chats
    Create a new DM with someone but don't send any message.
    In Default mode with excludeEmptyChats, confirm the empty chat is hidden.
    Send a message — confirm it now appears.

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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 Screenshot_1770732173
Android: mWeb Chrome Screenshot_1770978975
iOS: Native Simulator Screenshot - iPhone 16 Pro - 2026-02-13 at 11 15 34
iOS: mWeb Safari Simulator Screenshot - iPhone 16 Pro - 2026-02-13 at 11 21 00
MacOS: Chrome / Safari Screenshot 2026-02-13 at 10 42 28

@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/ReportUtils.ts 74.95% <100.00%> (+0.05%) ⬆️
... and 86 files with indirect coverage changes

Comment on lines +9537 to +9539
if (report?.reportID === currentReportId) {
return CONST.REPORT_IN_LHN_REASONS.IS_FOCUSED;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
if (report?.reportID === currentReportId) {
return CONST.REPORT_IN_LHN_REASONS.IS_FOCUSED;
}
// Include the currently viewed report. If we excluded the currently viewed report, then there
// would be no way to highlight it in the options list and it would be confusing to users because they lose
// a sense of context.
if (report.reportID === currentReportId) {
return CONST.REPORT_IN_LHN_REASONS.IS_FOCUSED;
}

can we restore the comment you moved?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

restored

Comment on lines +9572 to +9580
let parentReportActionComputed = false;
let parentReportActionCache: OnyxEntry<ReportAction>;
const getParentReportAction = (): OnyxEntry<ReportAction> => {
if (!parentReportActionComputed) {
parentReportActionComputed = true;
parentReportActionCache = isThreadReport ? allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.parentReportID}`]?.[report.parentReportActionID] : undefined;
}
return parentReportActionCache;
};
Copy link
Contributor

Choose a reason for hiding this comment

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

I see you are doing some kind of caching here, but I don't think how this would make significant difference as we are basically just performing a lookup in allReportActions, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes you right so I reverted this one

Comment on lines 9127 to 9133
if (!report.lastReadTime) {
return !isEmptyReport(report, isReportArchived);
}

if (isEmptyReport(report, isReportArchived)) {
return false;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

In both ifs we check for isEmptyReport(report, isReportArchived), it looks like it can be even more simplified

Suggested change
if (!report.lastReadTime) {
return !isEmptyReport(report, isReportArchived);
}
if (isEmptyReport(report, isReportArchived)) {
return false;
}
if (isEmptyReport(report, isReportArchived)) {
return false;
}
if (!report.lastReadTime) {
return true;
}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

const isThreadReport = isThread(report);
let parentReportActionComputed = false;
let parentReportActionCache: OnyxEntry<ReportAction>;
const getParentReportAction = (): OnyxEntry<ReportAction> => {
Copy link
Contributor

Choose a reason for hiding this comment

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

i do not see that we use such kind on patter define function inside function.
I think it makes sense to move it out from here, pass need params and just use
const parentReportAction = getParentReportAction(parentReportActionComputed, isThreadReport, allReportActions)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I revert this function in my commit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

let parentReportActionCache: OnyxEntry<ReportAction>;
const getParentReportAction = (): OnyxEntry<ReportAction> => {
if (!parentReportActionComputed) {
parentReportActionComputed = true;
Copy link
Member

Choose a reason for hiding this comment

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

I think it is better to change it to true after the actual operation

At this case if smth will go wrong - we do not update the flag

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Im not using it in my new commit

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

Copy link
Contributor

@JKobrynski JKobrynski left a comment

Choose a reason for hiding this comment

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

Left one comment, other than that LGTM

const reportActionKeys = Object.keys(currentReportActions);

const isThreadReport = isThread(report);
const parentReportAction = isThreadReport ? allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.parentReportID}`]?.[report.parentReportActionID] : undefined;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const parentReportAction = isThreadReport ? allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.parentReportID}`]?.[report.parentReportActionID] : undefined;
const parentReportActions = allReportActions?.[`${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${report.parentReportID}`];
const parentReportAction = isThreadReport
? parentReportActions?.[report.parentReportActionID]
: undefined;

I would consider something like this, I think it makes it more readable

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure Fixed

const triggerUnreadUpdate = debounce(() => {
const currentReportID = navigationRef?.isReady?.() ? Navigation.getTopmostReportId() : undefined;
const draftComment = allDraftComments?.[`${ONYXKEYS.COLLECTION.REPORT_DRAFT_COMMENT}${currentReportID}`];
Timing.start(CONST.TIMING.GET_UNREAD_REPORTS_FOR_UNREAD_INDICATOR);
Copy link
Contributor

Choose a reason for hiding this comment

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

FYI the Timing module is getting deprecated here #81691

Copy link
Contributor

Choose a reason for hiding this comment

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

let's either not track this at all, or record regular Sentry spans

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ill modify my code. . btw there will be other local alternative or mostly with sentry ?

}

if (isSelfDM(report)) {
if (isSelfDMReport) {
Copy link
Contributor

Choose a reason for hiding this comment

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

what does Opus say about these changes, is there still some room for more improvement from a static analysis of hot paths?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Opus you mean the ai model right ? I used it to get the initial recommendations and while there was also more options It didn't make difference in performance and was more complex and risky than this minor changes.

@elirangoshen elirangoshen marked this pull request as ready for review February 10, 2026 10:22
@elirangoshen elirangoshen requested review from a team as code owners February 10, 2026 10:22
@melvin-bot melvin-bot bot requested review from thesahindia and removed request for a team February 10, 2026 10:22
@melvin-bot
Copy link

melvin-bot bot commented Feb 10, 2026

@thesahindia 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, abdulrahuman5196, joekaufmanexpensify and mountiny and removed request for a team February 10, 2026 10:22
@melvin-bot
Copy link

melvin-bot bot commented Feb 10, 2026

@abdulrahuman5196 @mountiny One of you needs to 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]

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8805b63ab1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Copy link
Contributor

@abdulrahuman5196 abdulrahuman5196 left a comment

Choose a reason for hiding this comment

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

@elirangoshen
The code looks good, I have posted a question, kindly have a look into it.

We have merge conflicts in the PR.

In the Author Checklist, we don't have the required Screenshots/Videos for the platforms, could you check on these and add.

// Include the currently viewed report. If we excluded the currently viewed report, then there
// would be no way to highlight it in the options list and it would be confusing to users because they lose
// a sense of context.
if (report?.reportID === currentReportId) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I see we moved this from the below to the top of functions. Could you kindly provide information of why we are doing this? And how would this improve the performance.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried to move it here to make early exit without executing more expensive operations after

@elirangoshen
Copy link
Contributor Author

elirangoshen commented Feb 12, 2026

@elirangoshen The code looks good, I have posted a question, kindly have a look into it.

We have merge conflicts in the PR.

In the Author Checklist, we don't have the required Screenshots/Videos for the platforms, could you check on these and add.

I added to android native do you want me to add to other platforms as well ?
Ill deal with the conflict later

@abdulrahuman5196
Copy link
Contributor

abdulrahuman5196 commented Feb 13, 2026

@elirangoshen the code looks good.

@elirangoshen The code looks good, I have posted a question, kindly have a look into it.
We have merge conflicts in the PR.
In the Author Checklist, we don't have the required Screenshots/Videos for the platforms, could you check on these and add.

I added to android native do you want me to add to other platforms as well ? Ill deal with the conflict later

@elirangoshen Ideally we should first resolve the conflicts and then take the required screenshots/videos for all the platforms in author's checklist

@elirangoshen
Copy link
Contributor Author

Sure I will look into it asap

@elirangoshen
Copy link
Contributor Author

@elirangoshen the code looks good.

@elirangoshen The code looks good, I have posted a question, kindly have a look into it.
We have merge conflicts in the PR.
In the Author Checklist, we don't have the required Screenshots/Videos for the platforms, could you check on these and add.

I added to android native do you want me to add to other platforms as well ? Ill deal with the conflict later

@elirangoshen Ideally we should first resolve the conflicts and then take the required screenshots/videos for all the platforms in author's checklist

Done, its ready now

@mountiny
Copy link
Contributor

@abdulrahuman5196 can you retest please

@abdulrahuman5196
Copy link
Contributor

checking now

@abdulrahuman5196
Copy link
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Screen.Recording.2026-02-14.at.12.23.29.AM.mov
Android: mWeb Chrome
Screen.Recording.2026-02-14.at.12.28.23.AM.mov
iOS: HybridApp
Screen.Recording.2026-02-14.at.12.14.49.AM.mov
iOS: mWeb Safari
Screen.Recording.2026-02-14.at.12.18.40.AM.mov
MacOS: Chrome / Safari
Screen.Recording.2026-02-13.at.11.49.46.PM.mov

Copy link
Contributor

@abdulrahuman5196 abdulrahuman5196 left a comment

Choose a reason for hiding this comment

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

Changes looks good and works well. Reviewers checklist is also complete.

All yours. @mountiny

🎀 👀 🎀
C+ Reviewed

@mountiny mountiny merged commit 065308b into Expensify:main Feb 15, 2026
31 checks passed
@github-actions
Copy link
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.20-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@jponikarchuk
Copy link

This PR failing because of a regression issue
This issue is reproducible in: All platforms

1.mp4

@nlemma
Copy link

nlemma commented Feb 17, 2026

Hey @elirangoshen, quick question, is it expected for archived workspaces not to appear on LHN? Step 9 seems a bit unclear. Thanks

@elirangoshen
Copy link
Contributor Author

Hey @elirangoshen, quick question, is it expected for archived workspaces not to appear on LHN? Step 9 seems a bit unclear. Thanks

I will double check it asap

@elirangoshen
Copy link
Contributor Author

Hey @elirangoshen, quick question, is it expected for archived workspaces not to appear on LHN? Step 9 seems a bit unclear. Thanks

I will double check it asap

whats the expected behaviour for the achieved workspaces, should it appear in LHN?

@mountiny
Copy link
Contributor

Archived workspace chats should appear in the LHN in the Most recent mode

@nlemma
Copy link

nlemma commented Feb 17, 2026

Hey @mountiny, I would also like to point you to this PR and issue comment in case those expectations are a bit old.

@mountiny
Copy link
Contributor

Maybe it could be marked as hidden, but you can still search for it

@elirangoshen
Copy link
Contributor Author

about regression I will deliver a fix asap , about the achieved chat, Im not aware of an issue related that but if you will find anything Id check it out

@elirangoshen
Copy link
Contributor Author

#82638

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.20-6 🚀

platform result
🕸 web 🕸 cancelled 🔪
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.20-6 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 cancelled 🔪

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.