[BZ Check] [$250] onboarding-Concierge test drive task in Test drive receiver account directs to hmm not here

[mitarachim]

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.1.97-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): slottwo1+f@gmail.com
Issue reported by: Applause Internal Team
Device used: windows 10 chrome
App Component: Other

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Sign up with a new account - choose get paid back flow
   3.Complete the test drive with another fake user who you can log into
   4.Log into the test drive receivers account
   5.Open concierge
3. Click test drive task

Expected Result:

Concierge test drive task in Test drive receiver account must not direct to hmm not here page.

Actual Result:

Concierge test drive task in Test drive receiver account directs to hmm not here 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

Bug6862013_1750109708326.bandicam_2025-06-17_02-57-13-627.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021934985225189765472
• Upwork Job ID: 1934985225189765472
• Last Price Increase: 2025-06-17
• Automatic offers:
• thelullabyy | Contributor | 107738873

Issue Owner

Current Issue Owner: @ishpaul777

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

[thelullabyy]

Proposal

Please re-state the problem that we are trying to solve in this issue.

• When a concierge test drive task is viewed from the test drive receiver account, it incorrectly redirects to the "Hmm, not here" page.

What is the root cause of that problem?

• The taskReportID used in the navigation logic:
  

  App/src/components/ReportActionItem/TaskPreview.tsx

  Line 123 in 7ea0933

  onPress={() => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(taskReportID, undefined, undefined, undefined, undefined, Navigation.getActiveRoute()))}

  
  is undefined unless the task report has already been opened once. This causes the navigation to attempt opening r/undefined, resulting in the error page.

What changes do you think we should make in order to solve the problem?

• We should update the logic used to retrieve the taskReportID at:
  

  App/src/components/ReportActionItem/TaskPreview.tsx

  Line 85 in 7ea0933

  const taskReportID = taskReport?.reportID;

Currently, the code retrieves the taskReportID as follows:

const taskReportID = taskReport?.reportID;

We propose updating it to:

const taskReportID = taskReport?.reportID ?? getOriginalMessage(action).taskReportID;

This fallback ensures that even if taskReport data hasn't been fetched yet, the original message's taskReportID can be used to navigate to the correct report, which will then load its data as needed.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

• N/A

What alternative solutions did you explore? (Optional)

[dmkt9]

🚨 Edited by proposal-police: This proposal was edited at 2025-06-17 03:38:36 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Concierge test drive task in Test drive receiver account directs to hmm not here page.

What is the root cause of that problem?

• Because taskReport hasn’t been fetched yet, the taskReport passed to TaskPreview is undefined.
• When we click on the item, navigation happens here. Since taskReport is undefined, taskReportID also becomes undefined, causing this issue.
  

  App/src/components/ReportActionItem/TaskPreview.tsx

  Line 123 in 5b2de95

  onPress={() => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(taskReportID, undefined, undefined, undefined, undefined, Navigation.getActiveRoute()))}

What changes do you think we should make in order to solve the problem?

• We’ll retrieve taskReportID from the action the same way we did with taskTitle:
  

  App/src/components/ReportActionItem/TaskPreview.tsx

  Lines 85 to 86 in 5b2de95

  	const taskReportID = taskReport?.reportID;
  	const taskTitle = action?.childReportName ?? taskReport?.reportName ?? '';

const taskReportID = action?.childReportID ?? taskReport?.reportID;

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

NA

What alternative solutions did you explore? (Optional)

NA

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021934985225189765472

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (External)

[zanyrenney]

Broken workflow and quality issue.

[zanyrenney]

Hey @ishpaul777 would you be able to please review the proposal above?