[$500] Hold request - App crashes when saving a reason during hold request flow

[kavimuru]

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: 1.3.43-0
Reproducible in staging?: y
Reproducible in production?: new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applasue internal team
Slack conversation:

Action Performed:

1. Launch New Expensify app.
2. Create a manual request from any user.
3. Go to request details page.
4. Click 3-dot menu > Hold request.
5. Add a reason and save it.

Expected Result:

App does not crash.

Actual Result:

App crashes.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

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

Bug6385223_1708394496532.Screen_Recording_20240220_081809_New_Expensify.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0126f2cd8c5ade674d
• Upwork Job ID: 1759794310203371520
• Last Price Increase: 2024-02-20
• Automatic offers:
• shubham1206agra | Reviewer | 0
• mkhutornyi | Contributor | 0

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @joekaufmanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

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

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