Skip to content

[Due for payment 2026-10-22] Expense - Add receipt message is missing and system message reorder. #102537

Open
Open
[Due for payment 2026-10-22] Expense - Add receipt message is missing and system message reorder.#102537
Assignees
arosiclairmallenexpensifyflaviadefariadukenv0307truph01
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Description

@applause-bot
applause-bot
bot
opened on Sep 29, 2026

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.95-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #100801
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: Money Requests

Action Performed:

  1. Launch app
  2. Open workspace chat
  3. Toggle on forced offline
  4. Create a manual expense entering Merchant
  5. Open the expense and add the receipt via camera image
  6. Note add receipt message is shown
  7. Remove the receipt and verify remove receipt message is shown
  8. Add receipt via choose file and note add receipt message is shown
  9. Now delete receipt
  10. Toggle off forced offline

Expected Result:

Add receipt message must not be missing and system message must not reorder.

Actual Result:

Add receipt message is missing and system message reorder.
Note : Totally 2 add receipt message must be shown but one message disappear after removing receipt second time.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7272491_1790681860617.Screenrecorder-2026-09-29-16-57-53-210.mp4

View all open jobs on GitHub

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

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot
    added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 29, 2026
  2. gleitebr
    added this to #expensify-bugson Sep 29, 2026

  3. applause-bot commented on Sep 29, 2026

    @applause-bot
    applause-botBot
    on Sep 29, 2026
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/13d508b65d5dd38f56401e5002f827d24051b29560047c491d4e0ecc8ddcf48f

  4. melvin-bot
    assigned
    arosiclair
    on Sep 29, 2026

  5. melvin-bot commented on Sep 29, 2026

    @melvin-bot
    melvin-botBot
    on Sep 29, 2026 – with Melvin Bot

    You have been assigned to this deploy blocker because you recently merged this PR: #100801

  6. github-actions
    added
    Engineering
    HourlyKSv2
    on Sep 29, 2026
  7. melvin-bot
    assigned
    flaviadefaria
    on Sep 29, 2026

  8. github-actions commented on Sep 29, 2026

    @github-actions
    github-actionsBot
    on Sep 29, 2026 – with 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.
  9. melvin-bot
    assigned
    truph01
    on Sep 29, 2026

  10. melvin-bot commented on Sep 29, 2026

    @melvin-bot
    melvin-botBot
    on Sep 29, 2026 – with Melvin Bot

    @arosiclair @flaviadefaria @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #100801

  11. melvin-bot
    assigned
    dukenv0307
    on Sep 29, 2026

  12. melvin-bot commented on Sep 29, 2026

    @melvin-bot
    melvin-botBot
    on Sep 29, 2026 – with Melvin Bot

    @dukenv0307 you have been assigned to this deploy blocker because you authored the offending PR: #100801

  13. melvin-bot commented on Sep 29, 2026

    @melvin-bot
    melvin-botBot
    on Sep 29, 2026 – with Melvin Bot

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

  14. 24 remaining items

  15. melvin-bot commented on Oct 15, 2026

    @melvin-bot
    melvin-botBot
    on Oct 15, 2026 – with Melvin Bot

    @truph01

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.9-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 2026-10-22. 🎊

    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]

  16. truph01 commented on Oct 20, 2026

    @truph01
    truph01
    on Oct 20, 2026
    Contributor

    You have been assigned to this deploy blocker because you recently merged this PR: #100801

    It is a preexisting issue based on #102537 (comment), not the regression from #100801

  17. melvin-bot
    removed
    Overdue
    on Oct 20, 2026

  18. truph01 commented on Oct 20, 2026

    @truph01
    truph01
    on Oct 20, 2026
    Contributor

    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:
      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:

    Test:

    Test case 1:

    1. Submitter submit an expense without receipt
    2. Submitter or admin add new receipt
    3. Verify that the message added a receipt is created
    4. Replace the receipt
    5. Verify that there're 2 messages: Removed a receipt & Added a receipt

    Test case 2:

    1. Submitter submit an expense without receipt
    2. Submitter or admin add new receipt
    3. Verify that the message added a receipt is created
    4. Remove the receipt
    5. Observe the message removed a receipt is shown
    6. Reset cache and restart
    7. Observe the message removed a receipt is preserved

    Test case 3:

    1. Launch app
    2. Open workspace chat
    3. Toggle on forced offline
    4. Create a manual expense entering Merchant
    5. Open the expense and add the receipt via camera image
    6. Note add receipt message is shown
    7. Remove the receipt and verify remove receipt message is shown
    8. Add receipt via choose file and note add receipt message is shown
    9. Now delete receipt
    10. Toggle off forced offline
    11. Verify that: Add receipt message must not be missing and system message must not reorder.

    Test case 4:

    1. Launch app
    2. Create a manual expense in self dm entering Merchant
    3. Open the expense and add a receipt via camera image
    4. Note added a receipt system message is shown
    5. Tap receipt and delete it
    6. Verify that: Remove receipt system message must be shown in self dm on removing the receipt.

    Do we agree 👍 or 👎

  19. melvin-bot
    added
    WeeklyKSv2
    DailyKSv2
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    DailyKSv2
    WeeklyKSv2
    on Oct 20, 2026
  20. melvin-bot
    assigned
    mallenexpensify
    on Oct 21, 2026

  21. melvin-bot commented on Oct 21, 2026

    @melvin-bot
    melvin-botBot
    on Oct 21, 2026 – with Melvin Bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  22. melvin-bot commented on Oct 21, 2026

    @melvin-bot
    melvin-botBot
    on Oct 21, 2026 – with 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
  23. melvin-bot
    added
    Overdue
    on Oct 23, 2026

  24. mallenexpensify commented on Oct 24, 2026

    @mallenexpensify
    mallenexpensify
    on Oct 24, 2026
    Contributor
    Image

    @truph01 plz complete the full checklist.

    This looks like it was a regression from the PR you reviewed and that the bug is also on production so it was pre-existing. If so, provide details and links. Thx

  25. melvin-bot
    removed
    Overdue
    on Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions