[HOLD for payment 2022-12-05] New Chat - "Recents" contacts are NOT correctly ordered by the latest messages

[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. Go to URL https://staging.new.expensify.com/
2. Log with any account which have a lot of contacts
3. Go to New Chat or New Group
4. Verify there are 5 conversations displayed in "Recents" and that they are correctly ordered by the latest message

Expected Result:

Contacts should be correctly ordered by the latest messages in the "Recent" section

Actual Result:

"Recents" contacts are NOT correctly ordered by the latest messages

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Web
• iOS
• Desktop App
• Mobile Web

Version Number: 1.2.32.1

Reproducible in staging?: Yes

Reproducible in production?: No

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

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

[s77rt]

Unable to reproduce from my side

[mountiny]

I also cannot reproduce after a fresh sign in in production or in staging 🤷

[mvtglobally]

asking team to double check

[luacmartins]

I'm also unable to reproduce

[luacmartins]

@mvtglobally were you able to reproduce the issue?

[mvtglobally]

@luacmartins Team is still able to repro with High traffic account

Recording.1793.mp4

[mountiny]

This would have to be related to this PR, however, with the migration there, I am not sure if reverting would be best option.

Given the nature of this bug and the fact the PR is part of a broader initiative to fix way worse issue, I would vote for treating this as Bug but not as a deploy blocker

[luacmartins]

Fix here

[luacmartins]

Closing this issue since the PR was merged!

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.32-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Sort archived rooms using Unix epoch #13093

If no regressions arise, payment will be issued on 2022-12-05. 🎊

After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

• Merged PR within 3 business days of assignment - 50% bonus
• Merged PR more than 9 business days after assignment - 50% penalty