Skip to content

No Direct Seek Event & Inconsistent Current Time on Seek #1212

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

Open
tusharhatwar1997 opened this issue Apr 2, 2025 · 2 comments
Open

No Direct Seek Event & Inconsistent Current Time on Seek #1212

tusharhatwar1997 opened this issue Apr 2, 2025 · 2 comments

Comments

@tusharhatwar1997
Copy link

Problem Statement
The YouTube Android Player API does not provide a direct seek event, making it difficult to track when a user seeks to a different position in the video.

Current Behavior
The only way to track seek actions is through onCurrentSecond(), but this method is not reliable for detecting seeks because it updates continuously.

Additionally, there is an inconsistency in timestamps when seeking using the SeekBar UI:

If we fetch the timestamp immediately after seeking, it differs from the timestamp retrieved when pausing and playing at the same position.

@PierfrancescoSoffritti
Copy link
Owner

If the IFrame player does not provide a seek event, there is not much we can do. If they have it we should expose it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@PierfrancescoSoffritti @tusharhatwar1997 and others