[Hold for #46324] Search - Draft message inside the composer disappears in expense details page

[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.0.16-0
Reproducible in staging?: Y
Reproducible in production?: Y
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): bezawitgebremichael+112211@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Navigate to staging.new.expensify.com
2. Create an expense
3. Go to search
4. Click on an expense from the expense list
5. Write something inside the composer
6. Go back to inbox
7. Observe that the text inside the composer is visible
8. Click on chat where the expense is submitted from the LHN
9. Open the expense details page by clicking on the preview

Expected Result:

The drafted message inside the composer should be present

Actual Result:

The draft message inside the composer disappears and the composer gets empty

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6554984_1722117649352.4_5848162808948069384.mp4

View all open jobs on GitHub

[melvin-bot]

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

[lanitochka17]

We think that this bug might be related to #vip-vsp

[lanitochka17]

@sonialiap FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[FitseTLT]

Same root cause as #45408
Tagging @luacmartins

[sonialiap]

@luacmartins do you think this issue will be, or can be covered by #45408?

[luacmartins]

Yea, this issue should be fixed once #46324 is merged.

[melvin-bot]

@sonialiap, @luacmartins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@sonialiap, @luacmartins Huh... This is 4 days overdue. Who can take care of this?