Skip to content

[Due for payment 2025-08-01] [Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open #66816

Closed

Description

@jponikarchuk

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: 9.1.84-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/folder/12015343/test-cases/39318327
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.5 Chrome, iPhone 15 iOS 18.5 Safari
App Component: Chat Report View

Action Performed:

  1. Sign in to ND with a gmail account
  2. Create a workspace
  3. Navigate to the workspace chat
  4. Click "+" button next to the composer, select "Create expense". Create a manual expense, do not open the expense details
  5. Click "+" button again, create one more expense (could be any)
  6. Observe the Report preview in the workspace chat

Expected Result:

Second expense preview is shown next to the first expense in the workspace chat

Actual Result:

Preview of the second expense is not shown in the report preview in the workspace chat until the report is opened. Reproducible also in 1:1 chats

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

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 Jul 21, 2025
  2. melvin-bot commented on Jul 21, 2025

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. github-actions commented on Jul 21, 2025

    @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.
  4. melvin-bot commented on Jul 21, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jul 21, 2025

    @melvin-bot

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

  6. rushatgabhane commented on Jul 21, 2025

    @rushatgabhane
    Member

    @BlameGPT find culprit PR

  7. BlameGPT commented on Jul 21, 2025

    @BlameGPT
    Contributor

    Suspects on the loose 🕵

    If not above, check these

  8. rushatgabhane commented on Jul 21, 2025

    @rushatgabhane
    Member

    in other DB, that cause is #65721

    so it's probably this

  9. 26 remaining items

  10. changed the title [-][Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/-] [+][Due for payment 2025-08-01] [Due for payment 2025-07-30] Report preview - Preview of the second expense is not shown in the chat until the report is open[/+] on Jul 25, 2025
  11. melvin-bot commented on Jul 25, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.85-5 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 2025-08-01. 🎊

    For reference, here are some details about the assignees on this issue:

  12. melvin-bot commented on Jul 25, 2025

    @melvin-bot

    @parasharrajat @mallenexpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]

  13. mallenexpensify commented on Jul 31, 2025

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @parasharrajat due $250 via NewDot on 8/1

    @parasharrajat plz complete the BZ checklist.

  14. parasharrajat commented on Jul 31, 2025

    @parasharrajat
    Member

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: wrap Onyx.set for derived values in a method #65721

    • [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: Not needed

    • [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.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Sign in to ND with a gmail account
    2. Create a workspace
    3. Navigate to the workspace chat
    4. Click "+" button next to the composer, select "Create expense". Create a manual expense, do not open the expense details
    5. Click "+" button again, create one more expense (could be any)
    6. Observe the Report preview in the workspace chat
    7. Verify both expenses are shown in the preview.

    Do we agree 👍 or 👎

  15. parasharrajat commented on Aug 1, 2025

    @parasharrajat
    Member

    We can close this issue, I will request later.

  16. melvin-bot commented on Aug 1, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  17. mallenexpensify commented on Aug 4, 2025

    @mallenexpensify
    Contributor

    We can close this issue, I will request later.

    K, @parasharrajat , ping me if/when needed.

    Test case created

  18. parasharrajat commented on Sep 3, 2025

    @parasharrajat
    Member

    Payment requested as per #66816 (comment)

  19. quinthar commented on Sep 15, 2025

    @quinthar
    Contributor

    Approved $250 to @parasharrajat

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions