[$250] Handle the preExistingReportID for transaction threads

[mountiny]

As seen in this quality thread and some other cases over the past couple of weeks, the transaction threads and the single expense reports seem to not handle the preExistingReportID well, while the App should automatically navigate the user to the correct reportID that is returned by the BE, the user is instead stuck on the RBR stale report with error, that they can dismiss and move to the correct report manually. This is not the desired UX since the App should automatically clean up and move the user to the correct report.

Issue Owner

Current Issue Owner: @eVoloshchak

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022003230134067696919
• Upwork Job ID: 2003230134067696919
• Last Price Increase: 2025-12-22

[melvin-bot]

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

[rayane-d]

Draft PRs:

• https://github.com/Expensify/Auth/pull/18234
• Handle the preExistingReportID for transaction threads, message threads, and single expense reports #75101

[rayane-d]

PRs ready for review

• https://github.com/Expensify/Auth/pull/18234
• Handle the preExistingReportID for transaction threads, message threads, and single expense reports #75101

[rayane-d]

Weekly Update

• The solution was approved
• We determined that we need to deploy the App PR first because without it, If the childReportID is missing from the IOU action in the one expense report preview, the current App preExistingReportId logic will open the transaction thread report instead of the one expense report
• Auth PR was approved and it is now on hold on the App PR
• App PR is under C+ review and testing
• Updated the App PR test steps to use Onyx.update to simulate OpenReport command response and properly test the changes without the Auth PR

Next Steps

• C+ review of the App PR
• Get App PR merged and deployed to production
• Get Auth PR merged and deployed to production after that

ETA

• EOW / Early next week