fix: navigate back to thread after clicking on header

[daledah]

Explanation of Change

Fixed Issues

$ #54574
PROPOSAL: #54574 (comment)

Tests

1. Open self DM
2. Send a message
3. Long press the message -> Reply in thread
4. Press the link in report header to go back to self DM
5. Press browser/device back button
6. Verify that: we navigate back to thread

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Open self DM
2. Send a message
3. Long press the message -> Reply in thread
4. Press the link in report header to go back to self DM
5. Press browser/device back button
6. Verify that: we navigate back to thread

• 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
  • MacOS: Desktop
• 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
    • 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 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

Screen.Recording.2025-02-20.at.22.06.34.mp4

Android: mWeb Chrome

Screen.Recording.2025-02-20.at.22.10.46.mov

iOS: Native

Screen.Recording.2025-02-20.at.22.12.30.mov

iOS: mWeb Safari

Screen.Recording.2025-02-20.at.22.13.32.mov

MacOS: Chrome / Safari

Screen.Recording.2025-02-20.at.21.56.25.mp4

MacOS: Desktop

Screen.Recording.2025-02-20.at.22.14.11.mov

[melvin-bot]

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

[allgandalf]

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 tests pass on all platforms & I tested again on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• 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 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: Native

Screen.Recording.2025-02-25.at.1.07.40.PM.mov

Android: mWeb Chrome

Screen.Recording.2025-02-25.at.1.08.26.PM.mov

iOS: Native

Screen.Recording.2025-02-25.at.1.03.44.PM.mov

iOS: mWeb Safari

Screen.Recording.2025-02-25.at.1.07.10.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-02-25.at.1.01.56.PM.mov

MacOS: Desktop

Screen.Recording.2025-02-25.at.1.05.54.PM.mov

[allgandalf]

@puneetlath , lets wait for this comment to get addressed before merging though

[puneetlath]

@allgandalf @daledah can we take that conversation to Slack to get a faster resolution?

[allgandalf]

@daledah please ping them on slack and start a thread in #expensify-open-source

[daledah]

@allgandalf @puneetlath Asked in slack

[puneetlath]

Ok, it seems they are OOO or something. So what shall we do?

[rayane-d]

Sorry for the delay! replied here: #54574 (comment)

[daledah]

TESTS

Test 1: ✅

1. Go to chat.
2. Send a message.
3. Create a thread on the message.
4. Click on the parent "Thread" link.
5. Verify that the parent report is opened and the parent message is highlighted.

Screen.Recording.2025-03-03.at.15.13.16.mov

Screen.Recording.2025-03-03.at.15.15.01.mov

---

Test 2: ✅

1. Go to chat.
2. Go offline.
3. Send a message.
4. Create a thread on the message.
5. Click on the parent "Thread" link.
6. Verify that: The parent report is opened without skeleton loading

---

Screen.Recording.2025-03-03.at.15.54.43.mov

Test 3: ✅

1. Go to a room.
2. Create a task.
3. Leave the room.
4. Go to task report.
5. Click room link under header subtitle.
6. Pin the task to prevent disapear, then delete the task.
7. Open deleted task.
8. Click room link under header subtitle.
9. Verify that: Chat report is shown without not found page

Screen.Recording.2025-03-03.at.16.01.40.mp4

---

Test 4: ✅

1. Open any report
2. Send some messages (around 6-7 messages)
3. Hover over the 3rd or 4th parent message and click on Reply in the thread
4. Click on <<user's from>> link in header
5. Hover over the same parent message (which is already highlighted)
6. Click on reply in a thread
7. Go back to the main chat by the back button browser or the back button in the header
8. Verify that all parent messages are displayed in the main chat after going back from the thread by clicking the header back button or browser back button

Screen.Recording.2025-02-20.at.22.28.27.mp4

---

Test 5: ✅

1. Go to any chat
2. Send a message
3. Right-click on the message > Reply in the thread
4. Send a reply
5. Click on the link in the header subtitle to return to main chat
6. Send a message in the main chat
7. Verify that the new message in Step 6 will appear in the chat view

Screen.Recording.2025-02-20.at.22.29.30.mov

---

Test 6: ✅

1. Navigate to a report that has multiple messages
2. Mark a message at the bottom of the list unread
3. Scroll up to older message
4. Reply in the thread with one of the older messages
5. Click on the 'From' link on the thread header
6. Scroll up to older messages
7. 'New message' button should be displayed

Screen.Recording.2025-02-20.at.22.30.50.mov

---

Test 7: ✅

1. Send a message
2. Right click on the message > Reply in thread
3. Click on the header subtitle link
4. Delete the message
5. Verify that instead of not here page, we still show the report that contains the deleted message.

Screen.Recording.2025-02-20.at.22.57.24.mp4

---

Test 8: ✅

1. Go to chat
2. Send a message
3. Send a reply to the message in thread
4. Click on the header subtitle
5. Send a message
6. Note that user can send a message
7. Swipe right twice to return to the main chat but without highlight on the parent message
8. Send a message
9. Verify that the user is be able to send a message

Screen.Recording.2025-02-20.at.22.58.17.mp4

---

Test 9: ✅

1. Go to a DM
2. Send a message
3. Create a thread and reply to the message in thread
4. Tap on profile photo to open the user’s profile details
5. Tap back
6. Click on header subtitle
7. Go back. You’re not at root level thread
8. Verify that you can send a message

Screen.Recording.2025-02-20.at.23.07.29.mp4

---

Test 10: ✅

1. Go to FAB> Submit expense> Complete the flow
2. Go to thread transaction page
3. Go back to request page.
4. Expected Result:
5. There should be no loading spinner when open the request page
6. Send a message in request page
7. copy link to comment in a report
8. visit the link.
9. Send a new message in report.
10. Expected Result: No loading indicator at the bottom

Screen.Recording.2025-03-03.at.16.35.11.mp4

[daledah]

@allgandalf @rayane-d I uploaded the tests here^. Please help double check and verify the results. Thanks!

[OSBotify]

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

[github-actions]

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.1.9-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	success ✅

[github-actions]

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.1.9-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	success ✅

[github-actions]

🚀 Deployed to production by https://github.com/puneetlath in version: 9.1.9-8 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌