Expense - Destination report is not highlighted when submitting scan expense via native share

[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.3.60-1
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #87142
Email or phone of affected tester (no customers): soidnjsoidjoisjdiosj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

Precondition:

• Workspace has at least two reports in draft state.

1. Share a photo from device gallery to Expensify app.
2. Go to Submit tab.
3. Select workspace that has at least two reports in draft state.
4. Tap Show more.
5. Tap Report.

Expected Result:

The destination report will be highlighted.

Actual Result:

The destination report is not highlighted when submitting scan expense via native share.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7131500_1776353638713.Screen_Recording_20260416_232916_Expensify.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @TaduJR

[melvin-bot]

@marcochavezf recently merged #87142, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @luacmartins (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.

[OSBotify]

Investigation Summary: Classification: Frontend bug. Causing PR: #87142 (fix: Add updated automatic/scan flow to native share sheet creation flow by @TaduJR, High confidence). Related Issues: #86027. Recommendation: REVERT. PR #87142 introduced the Report field and multi-draft-report selection into the native share submission flow, but the selectedReportID used to highlight the current destination report is not correctly wired through. Assigned: @TaduJR (PR author), @hoangzinh and @marcochavezf (approving reviewers). Labels: DeployBlockerCash kept (frontend App bug), no changes made. Root cause: initMoneyRequest sets transaction.reportID to the policy expense chat reportID. IOURequestStepReport looks up outstanding IOU/draft expense reports using transaction.reportID, but the policy expense chat is not an outstanding report itself - its child iouReportID is. The ReportField navigates with the child IOU report ID but IOURequestStepReport computes a different selectedReportID, causing the destination report to not be highlighted when the workspace has two or more draft reports.