Skip to content

[$250] Offline created report field updates after navigating or refreshing #61277

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.1.39-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #61225
Email or phone of affected tester (no customers): testpayment935@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10 /Chrome, Samsung Galaxy s10/ Chrome, Samsung Galaxy s10/ Android 12
App Component: Other

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Create a new workspace (or open WS without report fields)
  3. Go to More Features and enable Report Fields
  4. Turn offline
  5. Create a new report field ( note your input values)
  6. Create a money request on the workspace chat
  7. Open the expense report
  8. Change the report filed input (note you input)
  9. Go online

Expected Result:

The updated input in step 8 is shown when going online.

Actual Result:

The report field show input in step 5 and updated to step 8 after navigating to another chat or refreshing the page

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

Bug6819014_1746140040327.bandicam_2025-05-02_01-43-09-058.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021920569516934570335
  • Upwork Job ID: 1920569516934570335
  • Last Price Increase: 2025-05-15
Issue OwnerCurrent Issue Owner: @aldo-expensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @greg-schroeder (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 May 1, 2025

    @melvin-bot

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

  4. github-actions commented on May 1, 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.
  5. melvin-bot commented on May 1, 2025

    @melvin-bot

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

  6. aldo-expensify commented on May 2, 2025

    @aldo-expensify
    Contributor

    Investigating this now...

  7. aldo-expensify commented on May 2, 2025

    @aldo-expensify
    Contributor

    I think we can't see this problem in production because the custom Report field doesn't show up optimistically:

    Screen.Recording.2025-05-03.at.2.03.01.AM.mov

    Also, I noticed that the command Report_SetFields doesn't return onyx data, maybe this is part of the problem:

    Image

    It probably should return data setting the report's field value in onyx.

  8. 58 remaining items

  9. aldo-expensify commented on Jul 4, 2025

    @aldo-expensify
    Contributor

    Same, including deploying web

  10. aldo-expensify commented on Jul 15, 2025

    @aldo-expensify
    Contributor

    I'll try to get back to this tomorrow or Wednesday

  11. aldo-expensify commented on Jul 15, 2025

    @aldo-expensify
    Contributor
  12. melvin-bot commented on Aug 7, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @greg-schroeder, @jayeshmangwani, @aldo-expensify eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  13. aldo-expensify commented on Aug 7, 2025

    @aldo-expensify
    Contributor
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.EngineeringInternalRequires API changes or must be handled by Expensify staffJuly2025CleanupMonthlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions