Unable to submit distance expense to workspace when it is created from actionable whisper

[IuliiaHerets]

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.0.59-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+kh271000024@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a manual expense.
4. Click Categorize it from the actionable whisper.
5. Click New workspace (if there is existing workspace).
6. Select a category, enter merchant and submit it.
7. Go to workspace chat.
8. Submit a distance expense.

Expected Result:

The distance expense is submitted successfully.

Actual Result:

It shows error when submitting distance expense to a workspace that is created from the actionable whisper.
Error:
Unexpected error submitting this expense. Please try again later.
The selected rate has been deleted

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6658705_1731062915525.20241108_183618.mp4

View all open jobs on GitHub

[melvin-bot]

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

[FitseTLT]

This is a BE issue we are already dealing with it here Tagging @luacmartins

[kadiealexander]

@luacmartins should we close this as a dupe?

[luacmartins]

yea, we can close as a dupe.

[FitseTLT]

@luacmartins I am sorry but on a second thought I see that this is a different API CATEGORIZE_TRACKED_EXPENSE not ConvertTrackedExpenseToRequest so don't forget to handle that and also SHARE_TRACKED_EXPENSE API.