[Due for payment 2026-02-04] iOS- Video- Play/Pause button is unresponsive after adjusting speed or toggling sound

[vincdargento]

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.2.59-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #66793
Email or phone of affected tester (no customers): htad26+wryuyt@gmail.com
Issue reported by: Applause Internal Team
Device used: iOS 26.1 / iPhone 13
App Component: Chat Report View

Action Performed:

1. Open any 1:1 chat.
2. Tap on Add attachment > Select any video.
3. On the send attachment modal, tap on the sound button
4. Tap the Play/Pause button.

Expected Result:

The button should be responsive and the video should be paused

Actual Result:

The button is not responsive and the video is not paused. It is responsive after the second tap. The same issue happens when changing playback speed

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @twisterdotcom

[melvin-bot]

Triggered auto assignment to @twisterdotcom (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 @stitesExpensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

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