Skip to content

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

Open

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): [email protected]
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: @brunovjk

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
    Contributor

    👋 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. 9 remaining items

  8. mukhrr commented on Sep 21, 2026

    @mukhrr
    Contributor

    Agreed, the LHN filename behavior is pre-existing,

    @lakchote do you think we can keep this open and fix separately?

  9. lakchote commented on Sep 21, 2026

    @lakchote
    Contributor

    Yes, we can. @mukhrr can you include the fix in your PR?

  10. mukhrr commented on Sep 21, 2026

    @mukhrr
    Contributor

    I did

  11. removed their assignment
    on Sep 21, 2026
  12. JS00001 commented on Sep 21, 2026

    @JS00001
    Contributor

    Looks like the PR authors are handling this

  13. mukhrr commented on Oct 1, 2026

    @mukhrr
    Contributor

    we decided to handle this in a separate PR here #101717 (comment)

  14. brunovjk commented on Oct 20, 2026

    @brunovjk
    Contributor

    Update: PR still under review.

  15. removed their assignment
    on Oct 26, 2026
  16. changed the title [-]Attachment-File becomes misaligned after renaming; LHN shows renamed file name[/-] [+][Due for payment 2026-11-03] Attachment-File becomes misaligned after renaming; LHN shows renamed file name[/+] on Oct 27, 2026
  17. melvin-bot commented on Oct 27, 2026

    @melvin-bot

    @brunovjk

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.23-3 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 2026-11-03. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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 no checklist is needed for this issue, you can click: [no checklist button]

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

Metadata

Metadata

Labels

BugSomething 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