"ReconnectApp" isn't showing up in Chrome network tab when switching chats

[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!

---

Version Number: 9.0.44-0
Reproducible in staging?: Y
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #47913

Action Performed:

1. Navigate to https://staging.new.expensify.com/
2. Log in with a Gmail account
3. Press F12 and switch to the network tab
4. Navigate to Account settings - Troubleshoot
5. Enable "Simulate failing network requests"
6. Navigate to the LHN
7. Switch between different chats
8. Open a 1:1 DM and send some messages
9. Navigate to Account settings - Troubleshoot
10. Disable "Simulate failing network requests"
11. Input "ReconnectApp" to the Chrome network - Filter field
    12 Press CTRL + F
12. Input and search for "ReconnectApp" to the Chrome - network - search - Find field

Expected Result:

"ReconnectApp" should show up

Actual Result:

"ReconnectApp" isn't showing up in Chrome network tab when switching chats or sending messages

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6623381_1727970908688.1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

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

[jasperhuangg]

IIRC we don't call ReconnectApp unless you reload the page or go from offline => online. @yuwenmemon Can you confirm? We should probably be able to close this out.

cc @roryabraham since you reviewed #47913. I think the testing steps in the PR might be inaccurate.

[roryabraham]

Yeah, agreed those test steps aren't correct. The only time we intend to call ReconnectApp is if you go from offline => online. Thanks @jasperhuangg