Skip to content

[Due for payment 2026-01-23] [Unreported] Expense - Violations are only seen on preview when moving track expense to new report offline #71950

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.2.24-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 TestRail: #71778
Email or phone of affected tester (no customers): ibellicotest+1894@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has Self DM.
Prerequisite 2: Account has at least one workspace.

  1. Open the Expensify app.
  2. Tap on FAB and select "Create Expense"
  3. Create a manual expense and submit it to Self DM.
  4. Navigate to "Reports" > "Expenses"
  5. Turn off internet connection.
  6. Long tap on the just created expense.
  7. Tap on the dropdown menu and select "Move Expense"
  8. Tap on "Create Report"
  9. Navigate to "Inbox"
  10. Note that a RBR is displayed on preview of workspace chat where the report was created.
  11. Open workspace chat.
  12. Note that "Review Required" message is seen on expense preview.
  13. Open report.
  14. Note that no error message about any violation is seen inside report.
  15. Turn on internet connection.
  16. Note that violations now appear inside report.

Expected Result:

When a track expense is moved to a new report while offline, violations about missing merchant and category, should be seen on expense preview and also inside report.

Actual Result:

When a track expense is moved to a new report while offline, violations about missing merchant and category, are seen on expense preview but not inside report. Violations only appear on report after recovering internet connection.

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

11.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    and removed on Oct 7, 2025
  2. melvin-bot commented on Oct 7, 2025

    @melvin-bot

    Triggered auto assignment to @garrettmknight (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. melvin-bot commented on Oct 7, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 7, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 7, 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.
  6. self-assigned this
    on Oct 7, 2025
  7. 53 remaining items

  8. changed the title [-][Unreported] Expense - Violations are only seen on preview when moving track expense to new report offline[/-] [+][Due for payment 2026-01-23] [Unreported] Expense - Violations are only seen on preview when moving track expense to new report offline[/+] on Jan 16, 2026
  9. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  10. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.3-8 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-01-23. 🎊

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

    • @parasharrajat requires payment through NewDot Manual Requests
    • @koko57 does not require payment (Contractor)
  11. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    @parasharrajat @dylanexpensify 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]

  12. dylanexpensify commented on Jan 20, 2026

    @dylanexpensify
    Contributor

    payment coming up

  13. melvin-bot commented on Jan 23, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @parasharrajat owed $250 via NewDot
    • Contributor: @koko57 does not require payment (Contractor)

    BugZero Checklist (@dylanexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • 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
  14. dylanexpensify commented on Jan 24, 2026

    @dylanexpensify
    Contributor

    Part of larger payout

  15. moved this from MEDIUM or LOW to Done in [#whatsnext] #migrateon Jan 24, 2026
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