Skip to content

[Due for payment 2025-07-25] Expense - Remove from report is still shown when the expense is unreported in offline mode #66200

Closed

Description

@lanitochka17

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.81-4
Reproducible in staging?: Y
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: #64259
Email or phone of affected tester (no customers): sdbhodshdsui@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.expensify.com
  2. Go to workspace chat
  3. Submit an expense to the workspace chat
  4. Open the expense report
  5. Go offline
  6. Click Report field
  7. Click Remove from report
  8. Go to self DM
  9. Click on the expense preview
  10. Click Report field

Expected Result:

Remove from report will not be shown because the expense is now unreported

Actual Result:

Remove from report is still shown when the expense is unreported in offline mode

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6888776_1752603396028.20250716_020754.mp4

View all open jobs on GitHub

Activity

  1. github-actions commented on Jul 15, 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.
  2. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  3. melvin-bot commented on Jul 15, 2025

    @melvin-bot

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

  4. rushatgabhane commented on Jul 15, 2025

    @rushatgabhane
    Member

    @BlameGPT please confirm the cause

  5. BlameGPT commented on Jul 15, 2025

    @BlameGPT
    Contributor

    Lowkey sus PRs fr fr

    If not above, check these

  6. lanitochka17 commented on Jul 15, 2025

    @lanitochka17
    Author

    Production:

    Recording.3421.mp4
  7. blimpich commented on Jul 15, 2025

    @blimpich
    Contributor

    cc: @luacmartins @shubham1206agra @allgandalf

    Stems from this PR presumably: #64259

  8. luacmartins commented on Jul 15, 2025

    @luacmartins
    Contributor

    Looking

  9. self-assigned this
    on Jul 15, 2025
  10. luacmartins commented on Jul 15, 2025

    @luacmartins
    Contributor

    I got a PR up, but I'll hold it for now since I'm trying to decide if we should revert the offending PR still

  11. melvin-bot commented on Jul 16, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  12. luacmartins commented on Jul 16, 2025

    @luacmartins
    Contributor

    Fixed in staging

    Screen.Recording.2025-07-16.at.11.42.25.AM.mov
  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jul 18, 2025
  14. changed the title [-]Expense - Remove from report is still shown when the expense is unreported in offline mode[/-] [+][Due for payment 2025-07-25] Expense - Remove from report is still shown when the expense is unreported in offline mode[/+] on Jul 18, 2025
  15. melvin-bot commented on Jul 18, 2025

    @melvin-bot

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

  16. melvin-bot commented on Jul 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-7 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-07-25. 🎊

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

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions