Skip to content

[Due for payment 2025-10-22] [$250] Expense - Track expense is moved to Self DM again after being submitted to WS while offline. #72079

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.27-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/2219752/test-runs/TR-1187/folder/13176877/41237365/940181942
Email or phone of affected tester (no customers): ibellicotest+1897@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 a Self DM.
Prerequisite 2: Account has at least one workspace.

  1. Open the Expensify app.
  2. Turn off internet connection.
  3. Create a manual expense and submit it to Self DM.
  4. Once redirected to chat, tap on "Submit it to someone"
  5. Select any workspace and complete creation flow.
  6. Tap on the back button on the top left corner to return to Self DM.
  7. Note that expense submitted to workspace, is still visible but with a strikethrough.
  8. Navigate to the workspace where expense was submitted.
  9. Open the expense report.
  10. Turn on internet connection.
  11. Note that infinite loading is displayed.
  12. Tap on back button on the top left corner to return to chat.
  13. Note that report is now displayed empty.
  14. Return to Self DM.
  15. Note that expense is displayed again on Self DM.
  16. Open expense.
  17. Note that system message about expense being moved to report on workspace, is still visible.

Expected Result:

Track expense submitted to workspace while offline, should remain on the workspace when recovering internet connection.

Actual Result:

When user moved a track expense to a workspace while offline and recovers internet connection on report, infinite loading is displayed, and also, when returning to chat, expense disappears from report and is moved to Self DM again automatically.

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021975902085754834153
  • Upwork Job ID: 1975902085754834153
  • Last Price Increase: 2025-10-16
Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

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

    @melvin-bot

    Triggered auto assignment to @stephanieelliott (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 8, 2025

    @melvin-bot

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

  4. melvin-bot commented on Oct 8, 2025

    @melvin-bot

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

  5. github-actions commented on Oct 8, 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. lakchote commented on Oct 8, 2025

    @lakchote
    Contributor

    That's a very specific edge case and not a core flow. Demoting.

  7. self-assigned this
    on Oct 8, 2025
  8. 28 remaining items

  9. melvin-bot commented on Oct 15, 2025

    @melvin-bot

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

  10. melvin-bot commented on Oct 15, 2025

    @melvin-bot

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

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

    • @eh2077 requires payment through NewDot Manual Requests
  11. melvin-bot commented on Oct 15, 2025

    @melvin-bot

    @eh2077 @stephanieelliott 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. melvin-bot commented on Oct 16, 2025

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  13. melvin-bot commented on Oct 22, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @eh2077 owed $250 via NewDot

    BugZero Checklist (@stephanieelliott)

    • (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/1975902085754834153/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. stephanieelliott commented on Oct 23, 2025

    @stephanieelliott
    Contributor

    Payment Summary

    Contributor: N/A internal
    Contributor+: @eh2077 due $250 via NewDot

  15. garrettmknight commented on Nov 21, 2025

    @garrettmknight
    Contributor

    $250 approved for @eh2077

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions