Skip to content

[Due for payment 2026-11-03] Attachment-File becomes misaligned after renaming; LHN shows renamed file name #101693

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


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:

  1. Launch app
  2. Open a chat
  3. Send a attachment .csv file
  4. Go to LHN
    5.Note attachment is shown in lhn
  5. Edit the file name via edit comment and save
  6. Note attachment become misaligned
  7. Go to LHN
  8. 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].

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7263818_1789806367999.Screenrecorder-2026-09-19-13-21-45-648.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7263818

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 21, 2026
  2. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    @chuckdries recently merged #99385, but they are OOO right now, so I'll auto-assign someone else.

  3. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    Triggered auto assignment to @JS00001 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Sep 21, 2026

    @github-actions

    👋 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.
  5. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    @chuckdries @tgolen @brunovjk you have been assigned to this deploy blocker because you reviewed the offending PR: #99385

  6. melvin-bot commented on Sep 21, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  7. 26 remaining items

  8. melvin-bot commented on Nov 2, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. melvin-bot commented on Nov 2, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  10. mukhrr commented on Nov 3, 2026

    @mukhrr

    I think this is due $250? I didn't post proposal before help wanted. We were brought and assigned. Thanks cc @mallenexpensify

  11. brunovjk commented on Nov 3, 2026

    @brunovjk

    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:

    1. Send the CSV without accompanying text. Verify the LHN preview shows [Attachment].
    2. Edit the comment, rename the file, and save. Verify the card displays the new name without overlap and the LHN still shows [Attachment].
    3. Edit again, adding text before the attachment. Verify the LHN shows that text followed by [Attachment].
    4. Go offline, edit the text and filename again, and save. Verify the card remains aligned and the LHN preserves [Attachment].
    5. Reconnect and reopen the chat. Verify the edited text, filename, card layout, and LHN preview persist.
    6. Replace the attachment URL with https://example.com/file.csv. Verify it renders as an ordinary link and the LHN shows its label.

    Do we agree 👍 or 👎

  12. brunovjk commented on Nov 3, 2026

    @brunovjk

    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

  13. melvin-bot commented on Nov 5, 2026

    @melvin-bot

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  14. mallenexpensify commented on Nov 6, 2026

    @mallenexpensify

    Payment Summary

    Contributor: @mukhrr due $175 via NewDot
    Contributor+: @brunovjk due $175 via NewDot

    Pay is $175 cuz Help Wanted wasn't added. We add Help Wanted to more difficult issues that Melv is unable to fix. This is a followup

  15. trjExpensify commented on Nov 6, 2026

    @trjExpensify

    approved $175 for @brunovjk

  16. flaviadefaria commented on Nov 9, 2026

    @flaviadefaria

    Approved: @mukhrr due $175 via NewDot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions