You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-03] Attachment-File becomes misaligned after renaming; LHN shows renamed file name #101693
Version Number: V9.4.90-1 Reproducible in staging?: Yes Reproducible in production?: Unable to validate in Prod - Provide reasoning. If this was caught during regression testing, add the test name, ID and link from BrowserStack:#99385 Email or phone of affected tester (no customers):dreamnitethedragon+vegst@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Redmi note 10s android 13 App Component: Chat Report View
Action Performed:
Launch app
Open a chat
Send a attachment .csv file
Go to LHN
5.Note attachment is shown in lhn
Edit the file name via edit comment and save
Note attachment become misaligned
Go to LHN
Note chat shows renamed file name instead [attachment]
Expected Result:
After changing file name, attachment must show new file name without misalignment and LHN must show [attachment].
Actual Result:
After changing file name, attachment become misaligned without name and LHN shows renamed file name instead [attachment].
Note : After renaming, attachment is intact as on downloading file is downloaded with renamed filename. Only file looks misaligned. Since renamed attachment file exists intact, LHN must show [attachment].
👋 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:
Identify the pull request that introduced this issue and revert it.
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: Introducing PR could not be confirmed.
Link to the comment on the Issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Signed in with an accessible chat and a CSV file available.
Test:
Send the CSV without accompanying text. Verify the LHN preview shows [Attachment].
Edit the comment, rename the file, and save. Verify the card displays the new name without overlap and the LHN still shows [Attachment].
Edit again, adding text before the attachment. Verify the LHN shows that text followed by [Attachment].
Go offline, edit the text and filename again, and save. Verify the card remains aligned and the LHN preserves [Attachment].
Reconnect and reopen the chat. Verify the edited text, filename, card layout, and LHN preview persist.
Replace the attachment URL with https://example.com/file.csv. Verify it renders as an ordinary link and the LHN shows its label.
Regressions and follow-ups: No related regressions from #102746 found through 2026-11-03. The earlier attachment misalignment was fixed separately by #101717, already deployed to production.
Activity
applause-bot commentedon Sep 21, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/ff0812f42705aceeb7236b0001537df37b05af33a93c16332a3b1fcf61471cae
https://platform.applause.com/services/links/v1/external/c89499c6de079f1ad84b717b80ebc5dbf545d1050f968a5fd570aff12871b51d
melvin-bot commentedon Sep 21, 2026
@chuckdries recently merged #99385, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Sep 21, 2026
Triggered auto assignment to @JS00001 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Sep 21, 2026
👋 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:
melvin-bot commentedon Sep 21, 2026
@chuckdries @tgolen @brunovjk you have been assigned to this deploy blocker because you reviewed the offending PR: #99385
melvin-bot commentedon Sep 21, 2026
💬 A slack conversation has been started in #expensify-open-source
26 remaining items
melvin-bot commentedon Nov 2, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Nov 2, 2026
Payment Summary
Resolving PRs:
Show an edited file attachment as [Attachment] in the chat list #102746
Reviewer: @mukhrr owed $175 via NewDot
Reviewer: @brunovjk owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
mukhrr commentedon Nov 3, 2026
I think this is due $250? I didn't post proposal before
help wanted. We were brought and assigned. Thanks cc @mallenexpensifybrunovjk commentedon Nov 3, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: Introducing PR could not be confirmed.
Link to the comment on the Issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Signed in with an accessible chat and a CSV file available.
Test:
https://example.com/file.csv. Verify it renders as an ordinary link and the LHN shows its label.Do we agree 👍 or 👎
brunovjk commentedon Nov 3, 2026
Summary payment
Fix: Keeps edited file attachments labeled [Attachment] in the LHN instead of displaying the renamed filename (#102746).
People involved: @mukhrr — author; @brunovjk — C+ reviewer.
Production deployment: Deployed on 2026-10-27, confirmed here. Deployment checklist.
Regressions and follow-ups: No related regressions from #102746 found through 2026-11-03. The earlier attachment misalignment was fixed separately by #101717, already deployed to production.
Suggested payment: $250
cc: @mallenexpensify
melvin-bot commentedon Nov 5, 2026
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
mallenexpensify commentedon Nov 6, 2026
Payment Summary
Contributor: @mukhrr due $175 via NewDot
Contributor+: @brunovjk due $175 via NewDot
Pay is $175 cuz
Help Wantedwasn't added. We addHelp Wantedto more difficult issues that Melv is unable to fix. This is a followuptrjExpensify commentedon Nov 6, 2026
approved $175 for @brunovjk
flaviadefaria commentedon Nov 9, 2026
Approved: @mukhrr due $175 via NewDot