Skip to content

[Due for payment 2025-10-01] Expense- Reject system messages disappear after going back to online #70621

Closed

Description

@mitarachim

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: v9.2.14-4
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: #62787
Email or phone of affected tester (no customers): applausetester+ndk20@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 11/iOS 18.6/ Safari
App Component: Money Requests

Action Performed:

Precondition: Use WS admin and create 1 single expense report

  1. Open https://staging.new.expensify.com/
  2. Navigate to single expense report
  3. Go offline
  4. Submit the expense
  5. Tap on 'More' > 'Reject'
  6. Enter a reason and tap on 'Reject expense'
  7. Tap on 'Mark as resolved'
  8. Repeat Step 4 - Step 6
  9. Go back online

Expected Result:

System msgs should be shown fully

Actual Result:

Reject system msgs disappears after going back online. In Web, msgs are listed in wrong order. Navigate away and back will solve it.

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

Bug6945540_1757984557412.System_Msg_Disappears.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @garrettmknight

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Sep 16, 2025
  2. melvin-bot commented on Sep 16, 2025

    @melvin-bot

    Triggered auto assignment to @twisterdotcom (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 Sep 16, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 16, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 16, 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. 12 remaining items

  7. mananjadhav commented on Sep 23, 2025

    @mananjadhav
    Collaborator

    PR is reviewed.

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 24, 2025
  9. changed the title [-]Expense- Reject system messages disappear after going back to online[/-] [+][Due for payment 2025-10-01] Expense- Reject system messages disappear after going back to online[/+] on Sep 24, 2025
  10. melvin-bot commented on Sep 24, 2025

    @melvin-bot

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

  11. melvin-bot commented on Sep 24, 2025

    @melvin-bot

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

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

    • @mananjadhav requires payment through NewDot Manual Requests
    • @truph01 requires payment (Needs manual offer from BZ)
  12. melvin-bot commented on Sep 24, 2025

    @melvin-bot

    @mananjadhav / @truph01 @garrettmknight 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. mananjadhav commented on Sep 27, 2025

    @mananjadhav
    Collaborator

    I think it's safe to close this one out now.

  14. garrettmknight commented on Sep 29, 2025

    @garrettmknight
    Contributor

    Tested, closing

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.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions