You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] Offline created report field updates after navigating or refreshing #61277
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:
Navigate to staging.new.expensify.com
Create a new workspace (or open WS without report fields)
Go to More Features and enable Report Fields
Turn offline
Create a new report field ( note your input values)
Create a money request on the workspace chat
Open the expense report
Change the report filed input (note you input)
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
👋 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:
Identify the pull request that introduced this issue and revert it.
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!
Activity
melvin-bot commentedon May 1, 2025
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.melvin-bot commentedon May 1, 2025
Triggered auto assignment to @aldo-expensify (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon May 1, 2025
👋 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:
melvin-bot commentedon May 1, 2025
💬 A slack conversation has been started in #expensify-open-source
aldo-expensify commentedon May 2, 2025
Investigating this now...
aldo-expensify commentedon May 2, 2025
I think we can't see this problem in production because the custom
Report fielddoesn't show up optimistically:Screen.Recording.2025-05-03.at.2.03.01.AM.mov
Also, I noticed that the command
Report_SetFieldsdoesn't return onyx data, maybe this is part of the problem:It probably should return data setting the report's field value in onyx.
58 remaining items
aldo-expensify commentedon Jul 4, 2025
Same, including deploying web
aldo-expensify commentedon Jul 15, 2025
I'll try to get back to this tomorrow or Wednesday
aldo-expensify commentedon Jul 15, 2025
Seems like this bug is coming from here: https://github.com/Expensify/Auth/pull/9909#discussion_r2208620705
melvin-bot commentedon Aug 7, 2025
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!
aldo-expensify commentedon Aug 7, 2025
This was solved by https://github.com/Expensify/Auth/pull/16223