mWeb/Safari - Group chat - Photo upload options not displayed when tapped on upload photo menu

[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: v9.0.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: https://expensify.testrail.io/index.php?/tests/view/4887343
Email or phone of affected tester (no customers): applausetester+ck822@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

Preconditions:

1. User has created new account
2. User has created group chat with few users with custom avatar & group name

Steps:

1. Navigate to staging.new.expensify.com
2. Open the created group chat
3. Click on the header of the conversation
4. Click on the avatar
5. Click on Upload photo menu

Expected Result:

Photo upload options (Photo Library, take photo & Choose file) should open & user able to change group avatar

Actual Result:

Photo upload options not displayed when tapped on upload photo menu in group chat details page

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6579763_1724366077675.RPReplay_Final1724366004.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @techievivek (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[IuliiaHerets]

Production - works well

RPReplay_Final1724389159.MP4

[ChavdaSachin]

This issue is similar to This Issue and was introduced after This pr.

[techievivek]

I see that a revert PR is already in progress. Let me check with the team to see if we can proceed with the merge and do a cherry-pick here.

[fedirjh]

cc @techievivek I think I have a quick fix for both bugs instead of just reverting the PR.