-
Notifications
You must be signed in to change notification settings - Fork 41
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
Playback failed after one full video playback during second video #119
Comments
I am also having this issue. Thought it works be fixed in 0.27.1. I am on Android 14. |
This is a duplication of this bug upstream, which in turn is also waiting for the NewPipeExtractor (where all the YouTube extract magic happen) to update. We should wait patiently for NewPipe team to fix those issues, in the mean time consider download the video and watch with external player (note that there is no SponsorBlock there, but that's the price for not having Tubular working). |
PipePipe 3.5.1 (in a few hours in F-Droid official repo hopefully (build in progress), otherwise look of their other install options) has SponsorBlock and a fix for the error around the 1 minute mark. |
The first video playback after opening the app is fine. The second video playback fails after a minute. The title is accurate. |
error 403 is not handled properly Exception
Crash log
|
Same here, this has happened a lot within the last three days. I will let the program sit in the background and it won't load videos Here's the report. Exception
Crash log
|
Checklist
Affected version
0.27.1
Steps to reproduce the bug
Expected behavior
Videos just play
Actual behavior
Within one to two minutes on playback of the second video, playback stops, an error occured.
Attempting to continue playing the video at this states returns more errors.
Screenshots/Recordings
No response
Logs
Exception
Crash log
Affected Android/Custom ROM version
Android 12
Affected device model
Motorola Edge 20 Fusion
Additional information
It seems to happen more frequently in full screen.
I had reported this in 0.27.0 but was flagged as duplicate to another issue. It is however still occuring in this version.
The text was updated successfully, but these errors were encountered: