Android - Reports - "It´s not here" on expenses report after backgrounding and reopening app

[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?: N
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-1145/folder/13176922/41237504/933089816
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the Expensify app
2. Sign up with a new account
3. Complete onboarding selecting "Track and budget expenses"
4. Once you land on "Inbox", tap on FAB and create first workspace
5. Navigate to workspace chat
6. Create two manual expenses
7. Navigate to "Reports" and open the report of the just created expenses
8. With report opened, background and reopen the app
9. Note that a "It´s not here" page appears when reopening app

Expected Result:

Expenses report should still be correctly displayed after backgrounding and reopening app

Actual Result:

"It´s not here" page is displayed when opening expenses report while on "Reports" and backgrounding and reopening app with report still opened

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

Bug6964437_1759555869096.Here.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @clarajones-expensify (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 @arosiclair (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²:

• #71190: Fix - "This report has no expenses" briefly shown in Reports after clearing cache
  • semantic similarity 60.3%
• #71371: fix(report-paylist): prevent empty state after paying report offline
  • semantic similarity 55.8%
• #71444: fix: Error is not removed from the report preview after paying an expense with empty field
  • semantic similarity 54.1%
• #69291: Fix - Expense - Paying the expense removed the amount violation, but it re-appeared later
  • semantic similarity 53.7%
• #71696: fix: IOU details are not visible preview on Search
  • semantic similarity 48.2%

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

[izarutskaya]

Issue is still reproducible on Samsung Galaxy A40/Android 11/App/Ad-hoc Build v9.2.23-0

mobizen_20251006_143301.mp4

Samsung M 52/Android 13

Screen.Recording.20251006.145501.Expensify.Adhoc.mp4