-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-12-09] [HOLD for payment 2024-12-07] Search - Group chat preview shows "Group" (email for 1:1 DM) instead of latest message #53291
Comments
Triggered auto assignment to @aldo-expensify ( |
💬 A slack conversation has been started in #expensify-open-source |
Triggered auto assignment to @jliexpensify ( |
👋 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:
|
Reproduced in staging, confirmed that in production it doesn't happen |
App/src/libs/OptionsListUtils.ts Lines 443 to 445 in 03639a9
Seems like Stack: |
I believe this may have been caused by: #52568 |
@Kicu @SzymczakJ are you around for taking a look at this? 🙏 |
I'm not sure if the solution could be simply as #53293 or if that would break something |
@hannojg / @ahmedGaber93 , since you worked here in something very related #53056, would you happen to know if this change #53293 makes sense to fix this? 🙇 |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Probably the same root cause as #53289 |
Made the PR ready for review: #53293 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-07. 🎊 |
@aldo-expensify @jliexpensify @aldo-expensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
No payment or checklist needed here, correct @aldo-expensify? |
Correct |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.69-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-09. 🎊 |
@aldo-expensify @jliexpensify @aldo-expensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
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.68-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+kh1211006@applause.expensifail.com
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Group chat preview will show the latest message.
Actual Result:
Group chat preview shows "Group" instead of latest message.
For 1:1 DM, it shows the user email instead of the latest message.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6679497_1732827030222.20241129_044843.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: