Newpipe: Couldn't get any stream / Could not play this stream (FIXED)

Created on 12 May 2020  Â·  32Comments  Â·  Source: TeamNewPipe/NewPipe

From Team NewPipe: Update to version 0.19.5.

Original report

Version

Version 0.19.3

Steps to reproduce the bug

1. Search anything you want, maybe something that includes livestreams.

  • Click the first result, and then the second till the 5th result.
  • Expected behavior


    Stream should normally show up.

    Actual behaviour


    Tried the exact same search 3 times.
    Stream doesn't show up, but instead the error below

    Logs

    Exception

    Crash log

    org.schabi.newpipe.extractor.stream.StreamInfo$StreamExtractException: Could not get any stream. See error variable to get further details.
        at org.schabi.newpipe.extractor.stream.StreamInfo.extractStreams(StreamInfo.java:192)
        at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:70)
        at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:62)
        at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:116)
        at org.schabi.newpipe.util.-$$Lambda$ExtractorHelper$5fJcha6Sq5APJBLdG6osaJby-mc.call(Unknown Source:4)
        at io.reactivex.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:44)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
        at io.reactivex.Maybe.subscribe(Maybe.java:4154)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.drain(MaybeConcatArray.java:153)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.request(MaybeConcatArray.java:78)
        at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onSubscribe(FlowableElementAtMaybe.java:66)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray.subscribeActual(MaybeConcatArray.java:42)
        at io.reactivex.Flowable.subscribe(Flowable.java:14479)
        at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
        at io.reactivex.Maybe.subscribe(Maybe.java:4154)
        at io.reactivex.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(SingleSubscribeOn.java:89)
        at io.reactivex.Scheduler$DisposeTask.run(Scheduler.java:578)
        at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
        at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)
    
    




    See the log here too https://haste.tchncs.de/icujifevuj.avrasm

    bug youtube

    Most helpful comment

    @eladkarako @pgenderson @jennyfromtheblockwiththegoodhair @allendema @suncatcher @ale5000 and @everyone having such issues, can you test this APK? NewPipe_3576-fix.zip.

    I used NewPipe extractor version TeamNewPipe/NewPipeExtractor#333 and NewPipe dev branch, it should fix it, when it's not about a recently ended live stream. The difference with the previous apk is I removed changes that seems like not fixing it, so that we are sure that TeamNewPipe/NewPipeExtractor#333 fixes it (it does for me at least).

    All 32 comments

    Sentry issue: NEWPIPE-3ZZ

    I could reproduce, but not everytime.
    Here are the steps: open a video, be unlucky and have this error (yeah, not easily reproduceable). Stypox encountered it too, see https://github.com/TeamNewPipe/NewPipeExtractor/pull/329

    I will see it

    @allendema: I can't fix it without having the page where it occurs. Could you reliably reproduce this issue? I've only seen it once myself. If you could reliably reproduce it, I could make an APK for you tomorrow that dumps the page in case of an error like this, which will allow me to fix it.

    Played with it again, now searched for “jazz“
    After selecting livestreams and pressing play, it loads for a while, then “stream couldn't be played” comes up.

    @allendema: Are you able to (semi-)regularly reproduce it? If so, could you download https://wb9688.stackstorage.com/s/bekYrunPaZ7Yff4, manually give it storage permission in Android settings, browse around until you find a video that gives that exception and wasn't a livestream or premiere, and give me the JSON it dumps in /sdcard/? The differences from dev in that APK is that it dumps YouTube's streams' JSON to /sdcard/, it has the additional regexes (i.e. TeamNewPipe/NewPipeExtractor#329) and recognizes DASH manifests in playerResponse.

    I'm afraid i can not do it right now.

    Exception

    Crash log

    org.schabi.newpipe.extractor.stream.StreamInfo$StreamExtractException: Could not get any stream. See error variable to get further details.
        at org.schabi.newpipe.extractor.stream.StreamInfo.extractStreams(StreamInfo.java:192)
        at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:70)
        at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:62)
        at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:116)
        at org.schabi.newpipe.util.-$$Lambda$ExtractorHelper$5fJcha6Sq5APJBLdG6osaJby-mc.call(Unknown Source:4)
        at io.reactivex.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:44)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
        at io.reactivex.Maybe.subscribe(Maybe.java:4154)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.drain(MaybeConcatArray.java:153)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.request(MaybeConcatArray.java:78)
        at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onSubscribe(FlowableElementAtMaybe.java:66)
        at io.reactivex.internal.operators.maybe.MaybeConcatArray.subscribeActual(MaybeConcatArray.java:42)
        at io.reactivex.Flowable.subscribe(Flowable.java:14479)
        at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
        at io.reactivex.Maybe.subscribe(Maybe.java:4154)
        at io.reactivex.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
        at io.reactivex.Single.subscribe(Single.java:3438)
        at io.reactivex.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(SingleSubscribeOn.java:89)
        at io.reactivex.Scheduler$DisposeTask.run(Scheduler.java:578)
        at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
        at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
    
    



    Can someone reproduce this:
    Version 0.19.3 / Android 10

    1. Search for “jazz” or “piano live”.
    2. Click on any livestream (sometime also happens on normal videos too)

    Couldn't play stream shows up.

    I don't belive this happend on 0.19.0

    @lbrunkho says in duplicate (#3615)

    Title: Music videos - could not parse website
    Content:
    I cant seem to open any video that's related to music. It starts to load the comments but then fails to load the actual video, and gives me this dump.

    _He posted a crash log_

    I think this might have to do with the YouTube music implementation bc its just in this version (0.19.3) that im having this issue with and all other videos work fine.

    I did encounter this bug on some random videos in trending or in my subscription feeds that were not music. But indeed it was more frequent when opening music videos.

    These reddit posts probably have the same issue

    https://reddit.com/comments/gmh5g6
    https://reddit.com/comments/gn3crn

    same here, many videos crashing.

    @wb9688

    Here the JSON: initialAjax1590606270929.zip

    Edit: Also if I click on "report error via e-mail" it just show the privacy message but there isn't any button to actually report the error.

    Edit 2: Also the privacy message cannot be closed without clicking on the link (annoying).

    @ale5000-git: Thanks for the JSON, however that's a recently ended livestream, which isn't supported and a different issue from this one. The problem with recently ended livestreams is that they're temporarily still in the livestream format instead of the normal video format, and we only support the livestream format for actual (still live) livestreams.

    When you click agree in that dialog, it should allow you to choose an e-mail app. Does it not do that?

    I don't see "agree" at all.

    @ale5000-git: Interesting, could you show a screenshot of that dialog?

    I see it like this:
    Screenshot_2020-05-27-21-53-53

    @ale5000-git: This is what it should look like in Italian (which I normally don't use, as I don't speak it, but I wanted to check whether it's a language specific bug):

    Screenshot_20200527-220058_NewPipe Debug

    I think it is related to the screen size.

    @ale5000-git: Do you see the accept button then when you increase minimum width in Android's developer settings? For me it's still visible at 320 dp, which is the lowest I could go.

    @wb9688: I don't have the option to change it (stock ROM, Android 5.1.1).

    The command adb shell wm density return Physical density: 240.

    @ale5000-git: Are you sure? I haven't seen phones where you couldn't change it, though a minimum width of 240 dp is really low.

    Screenshot_20200528-073630_Settings

    Create a new issue @wb9688 @ale5000-git

    @eladkarako @pgenderson @jennyfromtheblockwiththegoodhair @allendema @suncatcher @ale5000 and @everyone having such issues, can you test this APK? NewPipe_3576-fix.zip.

    I used NewPipe extractor version TeamNewPipe/NewPipeExtractor#333 and NewPipe dev branch, it should fix it, when it's not about a recently ended live stream. The difference with the previous apk is I removed changes that seems like not fixing it, so that we are sure that TeamNewPipe/NewPipeExtractor#333 fixes it (it does for me at least).

    Yup the abovementioned apk fixed the issue... Just cross tested it with the current main release and it fixed 2 out of 2 videos I tried!

    Yes! It works perfectly thank you!

    great fix(s).

    @TobiGr can we have an emergancy release for this?

    @theScrabi It is planned for later today once I am done with my lectures

    @theScrabi @TobiGr #3670

    hello team

    about the last version 0.19.4 is not worked on the most phone as Huawei and Samsung that have version android 10 the major problem the old version are nt still worked also .

    hope find solution as soon as possible

    WhatsApp Image 2020-05-30 at 17 14 52 (2)
    WhatsApp Image 2020-05-30 at 17 41 29

    @cesarmoi: For above issue, see #3686. Below issue is probably not our problem, unless you could prove that www.youtube.com doesn't say "Content unavailable" at the same time for that video when set to the same locale, etc.

    Was this page helpful?
    1 / 5 - 1 ratings

    Related issues

    ghost picture ghost  Â·  3Comments

    Knowbody42 picture Knowbody42  Â·  3Comments

    Hunter9888x picture Hunter9888x  Â·  3Comments

    f242 picture f242  Â·  3Comments

    tty4242 picture tty4242  Â·  3Comments