Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rapidly Tapping Skip Back Button Results in App Skipping Forward #1950

Closed
1 task done
thabotswana opened this issue Jul 26, 2024 · 0 comments · Fixed by #2041
Closed
1 task done

Rapidly Tapping Skip Back Button Results in App Skipping Forward #1950

thabotswana opened this issue Jul 26, 2024 · 0 comments · Fixed by #2041
Labels
playback Issues related to playback [Type] Bug Used for issues where something is not functioning as intended.

Comments

@thabotswana
Copy link

Description

Rapidly and repeatedly tapping the "skip back" button to go back actually results in the app skipping forward. This was reported in 8529645-zd-a8c.

Slack discussion: p1721757368412189-slack-C02A333D8LQ

Step-by-step reproduction instructions

I'm unable to reproduce.

The user confirmed they have "trim silence" set to "medium", the playback speed is set to 1x, and the volume boost is not activated.

  1. Open the full screen player.
  2. Tap the play button.
  3. Tap the "skip back" button in rapid succession.

Screenshots or screen recording

IMG_0.MOV

Did you search for existing bug reports?

  • I have searched for existing bug reports.

Device, Operating system, and Pocket Casts app version

iPhone14,2, iOS 17.5.1, Pocket Casts 7.68

@thabotswana thabotswana added the playback Issues related to playback label Jul 26, 2024
@pachlava pachlava added the [Type] Bug Used for issues where something is not functioning as intended. label Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
playback Issues related to playback [Type] Bug Used for issues where something is not functioning as intended.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants