[HOLD] New messages does not show up - not calling ReconnectApp on web?

[kavimuru]

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

---

Action Performed:

1. Log in with user A in desktop and iOS
2. Send a message from user B to user A

Expected Result:

Mobile and Desktop will receive notification and new message should appear

Actual Result:

Message is not showing up in Desktop, error is shown in console

Workaround:

unknown

Platforms:

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

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

Version Number: v1.2.88-1
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
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:

Expensify/Expensify Issue URL:
Issue reported by: @mallenexpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679676356651229

View all open jobs on GitHub

[MelvinBot]

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

[MelvinBot]

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

[johncschuster]

@kavimuru, can you clarify the reproduction steps?

I followed the steps above with these users:

User A: jschuster@expensifail.com
User B: jschuster@expensify.com

Log in with user A in desktop and iOS
Send a message from user B to user A

I saw no error, and the message was received.

Does either of these users need to be brand new users? Or do they need to not have an existing chat between them?

[mallenexpensify]

@johncschuster I highly doubt you'll be able to reproduce, it's annoying to have a bug like this that likely can't be reproduced by others. Per the SO, you can close now unless you want to go down a 🐰🕳

If you’re unable to reproduce the bug:

Add the Needs reproduction label.

• Comment on the issue outlining the steps you took to try to reproduce the bug, your results and tag the issue reporter and the Applause QA member who created the issue. Ask them to clarify reproduction steps and/or to check the reproduction steps again. Close issue.

[MelvinBot]

@johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick!

[johncschuster]

Thanks for the ping, @mallenexpensify! I'll go ahead and close this one out for now.