Videos not playing anymore

[Semuria]

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

[FollaKy]

Same here.

[KraXen72]

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

[flusteredcustard]

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

[EspWifi8266]

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]

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

[longestmt]

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]

Upstream issue: TeamNewPipe/NewPipe#11934

Pending upstream patch: TeamNewPipe/NewPipeExtractor#1262

[tuxayo]

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

Anyone else not having this working anymore?

[tuxayo]

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]

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.

[asandikci]

Both PipePipe and upstream NewPipe has been solved this problem recently (NewPipe solved just now, publishing a new release soon) You can both use PipePipe or NewPipe. Or if you want to use Tubular with the latest upstream fixes maybe the fork that I've been trying to maintain can be suitable for you: https://github.com/MaintainTeam/LastPipeBender/releases

[UnoNYC]

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]

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]

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]

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