Videos not playing anymore #192

Semuria · 2025-01-17T11:52:10Z

Checklist

I am able to reproduce the bug with the latest version.
I am not able to reproduce the bug with the latest version of vanilla NewPipe.
I made sure that there are no existing issues - open or closed - which I could contribute my information to.
I have read the FAQ and my problem isn't listed.
I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
This issue contains only one bug.
I have read and understood the vanilla NewPipe contribution guidelines.

Affected version

0.27.2

Steps to reproduce the bug

Try to play any video on Tubular from today

Expected behavior

Playing video

Actual behavior

Message: Something wen't wrong

Screenshots/Recordings

Exception

User Action: requested stream
Request: https://www.youtube.com/watch?v=T3uLD9pywJs
Content Country: DE
Content Language: de-DE
App Language: de_DE
Service: YouTube
Version: 0.27.2
OS: Linux Android 15 - 35

Crash log

org.schabi.newpipe.extractor.exceptions.ExtractionException: IOS player response is not valid
	at org.schabi.newpipe.extractor.services.youtube.extractors.YoutubeStreamExtractor.fetchIosMobileJsonPlayer(YoutubeStreamExtractor.java:967)
	at org.schabi.newpipe.extractor.services.youtube.extractors.YoutubeStreamExtractor.onFetchPage(YoutubeStreamExtractor.java:823)
	at org.schabi.newpipe.extractor.Extractor.fetchPage(Extractor.java:60)
	at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:97)
	at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:89)
	at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:123)
	at org.schabi.newpipe.util.ExtractorHelper.$r8$lambda$vk-P1AIrAksLBYlI0isZpDsAT7I(ExtractorHelper.java:0)
	at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda11.call(R8$$SyntheticClass:0)
	at io.reactivex.rxjava3.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:43)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
	at io.reactivex.rxjava3.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
	at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5377)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.drain(MaybeConcatArray.java:153)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray$ConcatMaybeObserver.request(MaybeConcatArray.java:78)
	at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onSubscribe(FlowableElementAtMaybe.java:66)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeConcatArray.subscribeActual(MaybeConcatArray.java:42)
	at io.reactivex.rxjava3.core.Flowable.subscribe(Flowable.java:16144)
	at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
	at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5377)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4855)
	at io.reactivex.rxjava3.internal.operators.single.SingleSubscribeOn$SubscribeOnObserver.run(SingleSubscribeOn.java:89)
	at io.reactivex.rxjava3.core.Scheduler$DisposeTask.run(Scheduler.java:644)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:65)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:56)
	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:347)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1117)

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

It works only very very seldom anymore & on luck

The text was updated successfully, but these errors were encountered:

FollaKy · 2025-01-17T16:31:13Z

Same here.

KraXen72 · 2025-01-17T18:06:24Z

I'm having the same problem. @polymorphicshade can you please take a look at the cause of the problem?
Thanks.

flusteredcustard · 2025-01-17T19:43:39Z

The same thing is happening to me, but usually if I click the "retry" button several times it will eventually load.

EspWifi8266 · 2025-01-18T10:19:20Z

I also have the same problem, but I have also noticed that it changes based on where I am connected for example with mobile data videos always freeze while with WiFi it works and almost never freezes

Ao1Pointblank · 2025-01-18T14:26:08Z

It's 2 updates behind newpipe, that's probably the issue

longestmt · 2025-01-18T16:40:58Z

It's 2 updates behind newpipe, that's probably the issue

Yep. An upstream issue with Newpipe is typically the issue. The developer is usually pretty timely in fixing it.

Kind thanks to @polymorphicshade for the work you put into the project.

tuxayo · 2025-01-20T17:25:31Z

Upstream issue: TeamNewPipe/NewPipe#11934

Pending upstream patch: TeamNewPipe/NewPipeExtractor#1262

tuxayo · 2025-01-21T22:53:10Z

but usually if I click the "retry" button several times it will eventually load.

Anyone else not having this working anymore?

tuxayo · 2025-01-21T23:00:27Z

Mitigation for now: when wanting to play a video:

I share and open it with PipePipe (v4.0.2 from f-droid still work even if it's from December 21th)
when video is over, mark it played on Tubular (if caring about history)

That's how to cling as much as possible to Tubular. Due to being afraid of incompatibilities and data loss when migrating an export back and forth between Tubular and PipePipe. (because PipePipe is a diverging fork of NewPipe and Tubular is a very close fork)

GogoGet · 2025-01-21T23:08:51Z

but usually if I click the "retry" button several times it will eventually load.

Anyone else not having this working anymore?

i am too. it won't play anything at all no matter what i do.

UnoNYC · 2025-01-22T14:37:33Z

but usually if I click the "retry" button several times it will eventually load.

Anyone else not having this working anymore?

This doesn't work for me anymore either. Only if I choose "open in browser" does it work.

EspWifi8266 · 2025-01-22T14:43:16Z

Unfortunately, from today, me too... For the moment I use new pipe, but as soon as there is an update I will gladly return to tubular. I want to specify that I do not want to put pressure on the owner but rather I thank him for the excellent app he managed to create

HarriBuh · 2025-01-22T18:26:47Z

It's an ongoing, neverending story of any YouTube fork. The moment a developer manages to break through Google's latest security mechanism, Google is informed about it and fixes/blocks that exploit right away. There won't be a single fork that will work flawlessly for a greater amount of time anymore. It's completely fckd up.

EspWifi8266 · 2025-01-22T18:32:50Z

Yes of course but for example new pipe if you keep it updated at least I who use it a lot, almost every day, I have never had problems

MalakymR · 2025-01-22T22:50:17Z

It's an ongoing, neverending story of any YouTube fork. The moment a developer manages to break through Google's latest security mechanism, Google is informed about it and fixes/blocks that exploit right away. There won't be a single fork that will work flawlessly for a greater amount of time anymore. It's completely fckd up.

That's not entirely true, the gaps between them "fixing" the "exploit" is quite large. That and there is no exploit per se.

The upstream will normally fix it quicker because that's their focus. Downstream adding in extra features will obviously add delays - often smaller teams, less time etc.

The solution is to move upstream and lose features or wait longer. I am not going to say "submit code" as I think that attitude is slightly obtuse.

If you can't live a few days without this fork, or even upstream... might want to question your life choices. Touch grass.

As it stands - yes there are issues - its not to do with being commits behind newpipe either as tubular was working fine for months after the fact. You can get around a lot of this by just refreshing.

tuxayo · 2025-01-23T06:03:11Z

#192 (comment)

The moment a developer manages to break through Google's latest security mechanism, Google is informed about it and fixes/blocks that exploit right away. There won't be a single fork that will work flawlessly for a greater amount of time anymore

That doesn't match the last 5 years of using newpipe & co. We usually have many months of peace between the major breakages.

It's likely not even sabotage. It's just google changing the webpages as they develop youtube. Since newpipe & co are parsing the web version of youtube [1], google could with moderate work break it every two week which is not what's happening.

[1] vs the API for the apps that need to still work when the app are out of date by a few months on many people phones. So google can't change it without keeping compat for at least some months. But it might require authentication and defeat most of point of alternative clients.

#192 (comment)

You can get around a lot of this by just refreshing.

Not for this, right? Or is there still some workaround?

HarriBuh · 2025-01-23T06:06:26Z

@MalakymR I don't see anything new that I haven't said already except that I may have use the wrong term of "exploit".
The time between "find a breach to make a yt fork work" and "fix that breach to break that fork" is NOT long, mostly around a week or two..in my experience and I've tried almost every available fork on F-Droid already. Call it what you want, it won't change the fact that devs will always lose.

@tuxayo That may have been like that in the last, put Google catches up way quicker now. The last working version of this work here stopped working for me after ~ 2,3 weeks of usage.

tired-creating-those-usernames · 2025-01-23T07:17:51Z

The same thing is happening to me, but usually if I click the "retry" button several times it will eventually load.

Not anymore 😮‍💨

KraXen72 · 2025-01-23T08:12:07Z

use the alternative builds (lastpipebender) until fixed

HarriBuh · 2025-01-23T08:49:23Z

@KraXen72 that one stopped working too

lionblaze55 · 2025-01-23T11:45:30Z

the fork pipepipe works if you sign in. That seem to be it for now.

FollaKy · 2025-01-23T12:31:14Z

As per today upstream Newpipe 0.27.5 works for me. I sure get the whole discussion of find a hole, exploit the hole,.patch the hole.
I think the whole point here is that, despite having done a fantastic job in the past, @polymorphicshade hasn't been active on this fork for what seems to be a while now (or am I mistaken?). Understandably, people might have other priorities than patching a hobby project.

longestmt · 2025-01-23T14:57:30Z

As per today upstream Newpipe 0.27.5 works for me. I sure get the whole discussion of find a hole, exploit the hole,.patch the hole.
I think the whole point here is that, despite having done a fantastic job in the past, @polymorphicshade hasn't been active on this fork for what seems to be a while now (or am I mistaken?). Understandably, people might have other priorities than patching a hobby project.

He will get to it at some point. The app is more or less feature complete so I suspect that's why there aren't recent updates. I think the last update was to solve a similar problem. I would just use newpipe in the interim. It's hard to be too demanding of a hobbyist dev that's essentially working for free.

FollaKy · 2025-01-23T15:06:18Z

As per today upstream Newpipe 0.27.5 works for me. I sure get the whole discussion of find a hole, exploit the hole,.patch the hole.
I think the whole point here is that, despite having done a fantastic job in the past, @polymorphicshade hasn't been active on this fork for what seems to be a while now (or am I mistaken?). Understandably, people might have other priorities than patching a hobby project.

He will get to it at some point. The app is more or less feature complete so I suspect that's why there aren't recent updates. I think the last update was to solve a similar problem. I would just use newpipe in the interim. It's hard to be too demanding of a hobbyist dev that's essentially working for free.

Exactly my point, @longestmt . He's doing free work for his (and our) enjoyment, so the time schedule is as he sees fit.

tired-creating-those-usernames · 2025-01-23T15:08:13Z

As per today upstream Newpipe 0.27.5 works for me. I sure get the whole discussion of find a hole, exploit the hole,.patch the hole.
I think the whole point here is that, despite having done a fantastic job in the past, @polymorphicshade hasn't been active on this fork for what seems to be a while now (or am I mistaken?). Understandably, people might have other priorities than patching a hobby project.

He will get to it at some point. The app is more or less feature complete so I suspect that's why there aren't recent updates. I think the last update was to solve a similar problem. I would just use newpipe in the interim. It's hard to be too demanding of a hobbyist dev that's essentially working for free.

Exactly my point, @longestmt . He's doing free work for his (and our) enjoyment, so the time schedule is as he sees fit.

He must be not using his own app 😁

longestmt · 2025-01-24T00:17:26Z

As per today upstream Newpipe 0.27.5 works for me. I sure get the whole discussion of find a hole, exploit the hole,.patch the hole.
I think the whole point here is that, despite having done a fantastic job in the past, @polymorphicshade hasn't been active on this fork for what seems to be a while now (or am I mistaken?). Understandably, people might have other priorities than patching a hobby project.

He will get to it at some point. The app is more or less feature complete so I suspect that's why there aren't recent updates. I think the last update was to solve a similar problem. I would just use newpipe in the interim. It's hard to be too demanding of a hobbyist dev that's essentially working for free.

Exactly my point, @longestmt . He's doing free work for his (and our) enjoyment, so the time schedule is as he sees fit.

He must be not using his own app 😁

I hope it takes longer now.

lameventanas · 2025-01-24T12:42:37Z

The possible solutions to this longstanding problem are:

give full access to this project to trusted people who are actually using the app
get the patches merged into Newpipe

tuxayo · 2025-01-24T16:03:19Z

get the patches merged into Newpipe

That needs new well written arguments for including sponsorblock. And that address the existing counterarguments.

Maybe the recent Honey scandal that was sponsorship to basically make install malware that actually hurt creators would be a relevant new line of argumentation to have sponsorblock included (opt-in)

And maybe asking if the sponsorblock implementation by default highlighting the self promotion segments and funding option from description might make sponsorblock acceptable. (Detect links like liberapay, patreon, etc) and mention their existance in a small additionnal message when skipping a sponsor.

MalakymR · 2025-01-24T16:08:08Z

get the patches merged into Newpipe

That needs new well written arguments for including sponsorblock. And that address the existing counterarguments.

Maybe the recent Honey scandal that was sponsorship to basically make install malware that actually hurt creators would be a relevant new line of argumentation to have sponsorblock included (opt-in)

I think they've already declined, and I would agree their focus should be on the core. Either that or we separate the core down even further.

The other option is NewPipe creates a a plugin system (nothing stopping forks relying on this too).

Semuria · 2025-01-25T10:23:41Z

Hi @polymorphicshade We would please you to

The possible solutions to this longstanding problem are:

give full access to this project to trusted people who are actually using the app

get the patches merged into Newpipe

I would 100% agree. I hope he'll read about anything of this thread prior then it's unstared and trust is gone by to many.
If its not feasible for one (which here obviously is the case) then the only logical solution should be to let people with heart on this project participate. Otherwise I feel sorry for the community and the lost oppurtunitys.
But at the end he can decide. Lets hope he's fine and someone can continue very soon! @polymorphicshade hope you're doing great?

asandikci · 2025-01-25T22:21:48Z

Probably solved with latest release, request re-open if issue persist
Edit: again...

tired-creating-those-usernames · 2025-01-31T19:42:35Z

Anyone else?

rugk · 2025-01-31T20:41:14Z

Uhm just installed and opened 0.27.5 from F-Droid (fresh version) and it shows no data at all, i.e. even the home page does not work/show any videos.

Semuria · 2025-02-01T07:19:14Z

There we are again :( If that gets fixed in the same speed it will reoccur I better go to Newpipe honestly

tired-creating-those-usernames · 2025-02-01T07:22:47Z

There we are again :( So now again, waiting and hoping?

Newpipe has same problem, so it's a chain of waiting

asandikci · 2025-02-01T08:10:17Z

TeamNewPipe working on a fix. Until then you can try spamming Retry button 🥶

tuxayo · 2025-02-01T18:36:37Z

Well, that was a brief chill period. Yesterday back to spamming retry and today no reasonable amount of retries are enough ^^"

polymorphicshade · 2025-02-01T19:26:24Z

tuxayo · 2025-02-01T20:29:56Z

Upstream ticket:
TeamNewPipe/NewPipe#11980

today no reasonable amount of retries are enough ^^"

Turns out it depends on the video, it's not completely dead yet.

Somehow, Pipepipe 4.0.2 from mid December has an approach that still works. I hope that will help upstream.

tuxayo · 2025-02-01T20:37:40Z

Good to see you there @polymorphicshade 👋💀
Thanks for the last update. I hope the next one will not cause you too much headaches. (by the picture the previous looked painfull enough already 😋)

codeXXjs · 2025-02-01T21:31:15Z

Corpo cannot stop us

github3845 · 2025-02-02T02:01:51Z

Wild how I cannot pay YouTube to have no tracking, sponsorblock, dearrow, thumbs down, etc. and how NewPipe blocks ads, but does not want to be a gatekeeper, so now we are relying on various forks of forks maintained by anonymous benefactors until YouTube starts to encrypt their streams and introduces live channels, streaming sports events, subscription packages, 24 month subscription plans, and a plan that still contains ads, until the plan with 25 minutes of ads per hour is the only one that remains and we are back where we were with cable TV 30 years ago.

But until then I am thankful every day for what you do.

github3845 · 2025-02-02T21:28:07Z

Video playback working for me again even though I didn't change anything. (0.27.5)

xxxxme · 2025-02-03T13:08:42Z

0.27.5 works with retries on a few videos for me, but not most. FreeTube (completely different code) works for me, but I prefer a NewPipe fork on my phone.

Ao1Pointblank · 2025-02-04T09:30:47Z

Well, playback works when you long press a video and select "play in background" at least.

This comment has been minimized.

Sign in to view

ShnikeJSB mentioned this issue Jan 25, 2025

No videos load at all anymore mikooomich/Tubular#3

Closed

6 tasks

asandikci mentioned this issue Jan 25, 2025

Videos not loading #163

Closed

7 tasks

asandikci closed this as completed Jan 25, 2025

asandikci reopened this Jan 31, 2025

asandikci mentioned this issue Jan 31, 2025

Again #196

Closed

asandikci mentioned this issue Feb 2, 2025

Can't play videos #197

Closed

7 tasks

Videos not playing anymore #192

Videos not playing anymore #192

Comments

Semuria commented Jan 17, 2025

Checklist

Affected version

Steps to reproduce the bug

Expected behavior

Actual behavior

Screenshots/Recordings

Exception

Logs

Affected Android/Custom ROM version

Affected device model

Additional information

FollaKy commented Jan 17, 2025

KraXen72 commented Jan 17, 2025

flusteredcustard commented Jan 17, 2025

EspWifi8266 commented Jan 18, 2025

Ao1Pointblank commented Jan 18, 2025

longestmt commented Jan 18, 2025

tuxayo commented Jan 20, 2025

tuxayo commented Jan 21, 2025

tuxayo commented Jan 21, 2025

GogoGet commented Jan 21, 2025

This comment has been minimized.

UnoNYC commented Jan 22, 2025 • edited Loading

EspWifi8266 commented Jan 22, 2025

HarriBuh commented Jan 22, 2025 • edited Loading

EspWifi8266 commented Jan 22, 2025

MalakymR commented Jan 22, 2025

tuxayo commented Jan 23, 2025

HarriBuh commented Jan 23, 2025 • edited Loading

tired-creating-those-usernames commented Jan 23, 2025

KraXen72 commented Jan 23, 2025

HarriBuh commented Jan 23, 2025

lionblaze55 commented Jan 23, 2025

FollaKy commented Jan 23, 2025

longestmt commented Jan 23, 2025 • edited Loading

FollaKy commented Jan 23, 2025

tired-creating-those-usernames commented Jan 23, 2025

longestmt commented Jan 24, 2025

lameventanas commented Jan 24, 2025

tuxayo commented Jan 24, 2025 • edited Loading

MalakymR commented Jan 24, 2025

Semuria commented Jan 25, 2025

asandikci commented Jan 25, 2025 • edited Loading

tired-creating-those-usernames commented Jan 31, 2025

rugk commented Jan 31, 2025

Semuria commented Feb 1, 2025 • edited Loading

tired-creating-those-usernames commented Feb 1, 2025

asandikci commented Feb 1, 2025

tuxayo commented Feb 1, 2025

polymorphicshade commented Feb 1, 2025

tuxayo commented Feb 1, 2025

tuxayo commented Feb 1, 2025 • edited Loading

codeXXjs commented Feb 1, 2025

github3845 commented Feb 2, 2025

github3845 commented Feb 2, 2025

xxxxme commented Feb 3, 2025

Ao1Pointblank commented Feb 4, 2025

UnoNYC commented Jan 22, 2025 •

edited

Loading

HarriBuh commented Jan 22, 2025 •

edited

Loading

HarriBuh commented Jan 23, 2025 •

edited

Loading

longestmt commented Jan 23, 2025 •

edited

Loading

tuxayo commented Jan 24, 2025 •

edited

Loading

asandikci commented Jan 25, 2025 •

edited

Loading

Semuria commented Feb 1, 2025 •

edited

Loading

tuxayo commented Feb 1, 2025 •

edited

Loading