Skip to content

Export - Exported file not received when online again after exporting all data while offline #68082

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

Action Performed:

Prerequisite: Account has at least one workspace available.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create a manual expense.
  4. Open the just created expense.
  5. Turn off internet connection.
  6. Tap on "More" and select "Export"
  7. Tap on "All Data - expense level" or on "All Data - report level"
  8. Note that a modal with a "Export in progress. Concierge will send you the file shortly" message, appears.
  9. Tap on "Got It"
  10. Turn on internet connection.
  11. Navigate to Concierge chat.
  12. Note that no new message with the exported files is received.

Expected Result:

After exporting all data while in offline mode, the user should receive the exported files on "Concierge" chat when recovering internet connection.

Actual Result:

Exported files are not received on "Concierge" chat when recovering internet connection, after exporting with the "All Data" options while in offline mode.

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

Bug6909936_1754534632554.Export.mp4

View all open jobs on GitHub

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

    @melvin-bot

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

    @melvin-bot

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

  5. melvin-bot commented on Aug 7, 2025

    @melvin-bot

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

  6. mitarachim commented on Aug 7, 2025

    @mitarachim
    Author

    Issue not reproduce when Use Staging Server is ON

    screen-20250807-021455.mp4
  7. removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Aug 7, 2025
  8. mountiny commented on Aug 7, 2025

    @mountiny
    Contributor

    Discussed with @NikkiWines this is not main case flow so demoting

  9. NikkiWines commented on Aug 7, 2025

    @NikkiWines
    Contributor

    Issue not reproduce when Use Staging Server is ON

    This is weird cause nothing in the backend is pending / staging only right now but I'll take a look and try and repro

  10. parasharrajat commented on Aug 8, 2025

    @parasharrajat
    Member

    I tested this, and it was working fine. May be I was on staging server.

  11. MelvinBot commented on Aug 8, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  12. mitarachim commented on Aug 14, 2025

    @mitarachim
    Author

    QA team has confirmed that the issue is not reproducible in build v9.1.94-0

    screen-20250814-090931.mp4
  13. NikkiWines commented on Aug 14, 2025

    @NikkiWines
    Contributor

    Nice, let's close this out then

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringNeeds ReproductionReproducible steps neededWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions