Expense - Initial value of formula field created offline changes on report when online again

[lanitochka17]

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.23-0
Reproducible in staging?: Y
Reproducible in production?: new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #71790
Email or phone of affected tester (no customers): ibellicotest+1886@gmail.com
Issue reported by: Applause - Internal Team

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. Navigate to "Workspaces" and open the workspace where the expense was created.
5. Tap on "Reports" and enable report fields.
6. Upgrade the workspace level if necessary.
7. Turn off internet connection.
8. Tap on "Add Field"
9. Add any name to the field.
10. Select "Formula" as type of field.
11. Navigate to workspace chat again and open the expense created on step 3.
12. Note that below the formula field´s name, "{report:id}" is displayed.
13. Turn on internet connection again.
14. Reopen expense report.
15. Note that now, the report field code, is displayed below the field´s name.

Expected Result:

Initial value of formula field created while offline, shouldn´t change on expense report when recovering internet connection.

Actual Result:

When creating a formula field while offline, "{report:id}" can be seen as initial value on expense report, below field´s name, and when recovering internet connection it changes to the report field´s code.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6964399_1759549395239.Value.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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]

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

[melvin-bot]

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

[github-actions]

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

[ikevin127]

🔄 I ran Vector¹ on this deploy blocker issue and here are the top 5 possible offending PRs based on semantic similarity²:

• #71371: fix(report-paylist): prevent empty state after paying report offline
  • semantic similarity 57.8%
• #71444: fix: Error is not removed from the report preview after paying an expense with empty field
  • semantic similarity 55.6%
• #71190: Fix - "This report has no expenses" briefly shown in Reports after clearing cache
  • semantic similarity 55.5%
• #71790: Add translations for report field formula type
  • semantic similarity 55.3%
• #69291: Fix - Expense - Paying the expense removed the amount violation, but it re-appeared later
  • semantic similarity 54.0%

Please drop a 👍 (correct) or 👎 (incorrect) as feedback regarding the results.

Note

PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.

Footnotes

1. Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results. ↩

2. Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩

[lakchote]

I don't think this is a blocker but that it is expected actually.

The root cause is #71790

Offline tests weren't completed there.

But it is said that the initial value is {report:id} (like in the video with the offline test):

As a result I'm demoting it from being a blocker cc @iwiznia