Fix of SelfDM does not show the latest system msg on LHN

[elirangoshen]

Explanation of Change

This pr fixes the regression issue of improve ShouldReportBeInOptionList function

Fixed Issues

$#82612

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. Open https://staging.new.expensify.com/
2. Navigate to SelfDM
3. Create an expense
4. Navigate away SelfDM
5. Navigate back to SelfDM

Expected result:

What would you like to do with this expense? should be shown under SelfDM in LHN

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

fix.mp4

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

@FitseTLT 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]

[abdulrahuman5196]

@elirangoshen Could you kindly explain the fix you are making here? And how is that a regression from here - https://github.com/Expensify/App/pull/81551/changes

I don't see overlap of code between this fix pr and original pr.

[elirangoshen]

@elirangoshen Could you kindly explain the fix you are making here? And how is that a regression from here - https://github.com/Expensify/App/pull/81551/changes

I don't see overlap of code between this fix pr and original pr.

Both of them making code change in the same function.
I think the cause of it related to isSelfDMWithVisiblePreference
when lastMessageText is empty notificationPreference === HIDDEN (as with selfDM) and const this line would return false isSelfDMWithVisiblePreference = isSelfDM(report) && !isHiddenForCurrentUser(report);
and then the whole big conditions

if (
    excludeEmptyChats &&
    isEmptyChat &&                        
    isChatReport(report) &&            
    !isPolicyExpenseChat(report) &&   
    !isTripRoom(report) &&       
    !isSystemChatReport &&         
    !isSelfDMWithVisiblePreference &&  
    canHideReport                 
) {
    return null; 
}

return null.

The fix I added is checking the selfDM prior to not return null in this case.

[elirangoshen]

Hi @abdulrahuman5196 is there an update in this ?

[elirangoshen]

Hi @abdulrahuman5196 Is there any update ?

[abdulrahuman5196]

Hi, Sorry for delay, checking now

[abdulrahuman5196]

@elirangoshen I am not sure if your RCA and solution is correct and even if this is a regression.

Regardless i tested your PR and the fix is not working. And i see you have not added author's checklist, is the fix working for you?

[elirangoshen]

Do you think this issue is not caused by the regression ? as i'm not sure about it as well.
About that fix not working can you post video ?

[abdulrahuman5196]

Do you think this issue is not caused by the regression ? as i'm not sure about it as well. About that fix not working can you post video ?

@elirangoshen I think it should be the other way. The author would be required to provide RCA on the solution and the explanation for the fix as well. I don't see any working videos on the author's checklist as well. Could you kindly provide RCA on the solution and the appropriate fix?

[elirangoshen]

Do you think this issue is not caused by the regression ? as i'm not sure about it as well. About that fix not working can you post video ?

@elirangoshen I think it should be the other way. The author would be required to provide RCA on the solution and the explanation for the fix as well. I don't see any working videos on the author's checklist as well. Could you kindly provide RCA on the solution and the appropriate fix?

I posted video in android in the checklist.

[abdulrahuman5196]

I posted video in android in the checklist.

@elirangoshen In the video, your selfDM is not even present in the LHN. Could you kindly check on this? I doubt if the fix is working