IOU - User taken to camera view on refreshing page after adding receipt

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 1.4.24-0
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:

Issue found when executing PR #33562

Action Performed:

1. Login to ND with gmail account
2. Open a chat
3. Create a manual request thought the chat plus icon (not the FAB)
4. Enter an amount and Next
5. Click the three dots on the top, and attach a receipt
6. Refresh the page in this step

Expected Result:

The page will go back to the first step, auto-filled with the previous amount.

Actual Result:

User taken back to camera view asking for permissions again on refreshing page after adding receipt

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

Bug6337878_1704903237078.RPReplay_Final1704896874.mp4

View all open jobs on GitHub

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

[melvin-bot]

Triggered auto assignment to @srikarparsi (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[situchan]

This seems like new expected behavior after #33562.
@cristipaval can you please confirm?

[thienlnam]

This does look intended