[INTERNAL] Thread - Unexpected error shown in removed receipt thread page

[jponikarchuk]

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.2.28-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-1222/folder/13177078/41237898/941909864
Email or phone of affected tester (no customers): Slottwo1 ployee@gmail.com
Issue reported by: Applause Internal Team
Device used: Redminote 10s android 13 phone
App Component: Money Requests

Action Performed:

1. Launch app
2. Open workpace chat
3. Create 2 expenses. (One with receipt)
4. Open the expense with receipt
5. Delete the receipt
6. Go to reports
7. Open thread page for removed receipt

Expected Result:

Unexpected error must not be shown in removed receipt thread page.

Actual Result:

Unexpected error shown in removed receipt thread 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

11.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021976512888442780963
• Upwork Job ID: 1976512888442780963
• Last Price Increase: 2025-10-10

Issue Owner

Current Issue Owner: @dominictb

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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 @tylerkaraszewski (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 3 possible offending PRs based on semantic similarity²:

• #71808: Create report from reported expens
• #72224: revert-fix-Android-Multi-scan-App-closes-when-scanning-multiple-receipt-at-once
• #70026: fix: Android - Multi scan - App closes when scanning multiple receipt at once

Please drop a 👍 (correct) or 👎 (incorrect) as feedback regarding the results (will use to fine-tune the reranking model).

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 -> perform reranking -> get final 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. ↩

[m-natarajan]

Issue reproducible in staging on all the platforms

Recording.59.2.mp4

09.10.2025_16.21.04_REC34.mp4

ScreenRecording_10-09-2025.16-14-45_1.MP4

az_recorder_20251009_161704.mp4

Retest.-.Android.Issue.72167.mp4

ScreenRecording_10-09-2025.16-09-52_1.MP4