bug(YouTube - Enable slide to seek): Including patch causes issues with clicking and double tapping the video player controls

[SeokHyeonLee]

Bug description

revanced-patches : v3.1.0 (also on v2.202.0)
revanced-integrations : v1.0.0
revanced-manager : v1.17.3
revanced-cli : v4.3.0

android version : 9.0(Galaxy Note 8), 11.0 (Galaxy S21U)

The YouTube player is having issues with the pause/play button (player menu buttons) and double-tapping to seek because the clicks are stuck when not zoomed in.
If you zoom 1.1x (but not 1.0x), then the pause/play button and double-tapping to seek will work as normal.

Error logs

No response

Solution

No response

Additional context

No response

Acknowledgements

• This issue is not a duplicate of an existing bug report.
• I have chosen an appropriate title.
• All requested information has been provided properly.

[oSumAtrIX]

Disable the slide to seek patch or it's option and check if that make a difference

[SeokHyeonLee]

Disable the slide to seek patch or it's option and check if that make a difference

already disable slide to seek and swipe controls
all combinations of settings related to interactions are stucked

[oSumAtrIX]

Follow this and report back:

[KobeW50]

I believe this has been confirmed by several users that it is indeed the Enable slide to seek patch which causes this, so the "waiting on author" can be removed and perhaps the title can be updated.

[LisoUseInAIKyrios]

To those having the issue, this can be 100% fixed by repatching and excluding Enable slide to seek (turning off the feature in the app settings is not enough).

This also can sometimes be fixed by clearing the app data and launching the app multiple times until the problem is gone.

The problem might be caused by an A/B installation setting that conflicts with the patch.

[oSumAtrIX]

The patch should be disabled with a warning or removed at this point in this case.

[LisoUseInAIKyrios]

This issue may be fixed by pull request #3629

The patch description will keep the side effect disclaimer since this bug is very difficult to reproduce, but otherwise it's likely the issue is fixed.