mWeb/Safari - Chat - Nothing happens when "Add attachment" option is tapped

[lanitochka17]

If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributimWeb - Chat - Nothing happens when "Add attachment" option is tappedcom to request to join our Slack channel!

---

Version Number: 9.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/4887449
Email or phone of affected tester (no customers): applausetester+vd_mweb082224@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Pre-requisite: issue seems to only affect mWeb on iOS/Safari

1. Go to https://staging.new.expensify.com/
2. Log in
3. Go to any chat
4. Tap on the "+" button on compose box
5. Select "Add attachment"

Expected Result:

The options menu to select an attachment should be displayed

Actual Result:

Nothing happens when "Add attachment" option is tapped

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

Bug6579532_1724350898451.Rpreplay_Final1724349613.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

[lanitochka17]

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

[lanitochka17]

Production:

241111.mp4

[arosiclair]

Reproduced with the latest changes in dev.

[arosiclair]

Reverting #47341 fixes the issue

[arosiclair]

Pinged @zfurtak to take a look here

[arosiclair]

Revert is prepped here. Giving @zfurtak a chance to respond before moving forward.

[war-in]

@arosiclair FYI @zfurtak will respond on Monday (she is OOO this week). Feel free to revert the PR for now and we will handle reported bugs next week 🙏

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[techievivek]

Let's proceed with the revert since there are other blockers linked to the above PR. I've already pinged the app deployers in Slack to see if anyone is available to help with the CP: https://expensify.slack.com/archives/C07J32337/p1724404593705399

[arosiclair]

Revert fixed it!

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.