-
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
Details - Instead of user name, incorrect title "Attachment" is shown #32514
Comments
👋 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:
|
Triggered auto assignment to @hayata-suenaga ( |
looking at this right now |
It's coming from #31467 which I think is being reverted. |
The revert PR was merged. Now fixed on main |
ah nice thanks for the info! 🙇 |
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: 1.4.8-0
Reproducible in staging?: Y
Reproducible in production?: N
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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
In profile page, user name / mail id must be displayed as title
Actual Result:
In profile page, instead of user name, incorrect title "Attachment" is shown
This issue occurs in individual chat, room chat, group chat, workspace in all profile pages, incorrect title "attachment" displayed instead of user name/mail id
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6302265_1701803666976.head.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: