Thread - In offline mode, clicking on reply thread directs to page keeps on loading

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Issue found when executing PR #26602

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Tao on any admin room
3. Send a message
4. Long press the message sent, to open reply in thread
5. Send a message
6. Turn off mobile data
7. Tap on header profile icon
8. Tap Leave thread
9. Open the thread again from main report by tapping on " reply" thread

Expected Result:

In offline, tapping on reply thread must direct to not found page

Actual Result:

In offline, tapping on reply thread directs to page which keeps on loading showing "U" profile icon on header

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• Windows / Chrome
• MacOS / Desktop

Version Number: 1.3.71-5

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6205317_threadmweb26602.mp4

Bug6205317_26602.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

👋 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.

[melvin-bot]

Triggered auto assignment to @tylerkaraszewski (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[chiragsalian]

So even though the user left the thread. Once they click on the thread again they should be able to get access to it. So while offline showing Page not found is not correct when the user wants to join a thread IMO.

The functionality should be the same as clicking into a new thread when offline which currently shows the report loader. So in this issue, if on staging we're showing a report loader then IMO that's good and consistent with regular threads so closing out this deploy blocker.

If i have misunderstood anything feel free to correct me.