[Bug] IOS/Android/Desktop - Messages are showing sent multiple times for sender

[kbecciv]

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. Launch App and login
2. Off WiFi
3. Send some messages to an account you have access too. (Preferably you're logged in on another device with)
4. On WiFi

Expected Result:

Messages sent without internet connection should be sent without any issues.

Actual Result:

Messages are sent twice for sender

Workaround:

Uknown

Platform:

Where is this issue occurring?

• iOS
• Android

Version Number: 1.1.89.0

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers): any

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5702689_20220824_113632.mp4

RPReplay_Final1661367712.MP4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[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 @srikarparsi (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[AndrewGable]

Few thoughts:

1. Agree I cannot reproduce on web
2. It seems(??) like a client side only issue since the double message is only seen on iOS and not on web
3. I think you have to leave and re-enter the page for the double message to show

[srikarparsi]

I agree, I wasn't able to reproduce this on web either. In the second video though, it looks like the message is rendering twice in the app without the user leaving the page.

[srikarparsi]

I'm un-assigning myself as I don't have much knowledge yet in ios/android and don't think I will be able to figure it out quick enough but will take a look back at the issue in the morning.

[AndrewGable]

OK we've decided to unblock this and move on. It requires a large-ish fix that is "moving backwards" in terms of where we want to go in terms of optimistic report action IDs/sequenceNumbers, so we are going to live with the bug for a little bit, then make sure it's fixed once we have removed sequenceNumbers.