-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
NewPipe becomes unresponsive when sharing YouTube videos/shorts #11147
Comments
bacevs
added
bug
Issue is related to a bug
needs triage
Issue is not yet ready for PR authors to take up
labels
Jun 14, 2024
Some things to try:
|
opusforlife2
added
the
waiting for author
If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed.
label
Jun 15, 2024
Works from within newpipe. Issue is when sharing to newpipe. Appreciate the suggestion for Seal, sounds like exactly what I want. |
github-actions
bot
removed
the
waiting for author
If the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed.
label
Jun 16, 2024
Then let's close this. If it turns out to be more common we can reopen. |
opusforlife2
removed
bug
Issue is related to a bug
needs triage
Issue is not yet ready for PR authors to take up
labels
Jun 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Affected version
0.27.0
Steps to reproduce the bug
Expected behavior
NewPipe should immediately provide the download link after sharing the video or short from YouTube without becoming unresponsive.
Actual behavior
NewPipe becomes unresponsive for about 20 seconds and shows the "NewPipe isn't responding" message. After tapping "Wait" multiple times, it eventually provides the download link.
Screenshots/Screen recordings
Video demonstrating the issue: YouTube Video
Logs
No response
Affected Android/Custom ROM version
Android 14
Affected device model
Google Pixel 8 Pro
Additional information
No response
The text was updated successfully, but these errors were encountered: