Content Unavailable

[zaniestp]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• 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 contribution guidelines.

Affected version

0.28.0

Steps to reproduce the bug

Open the search button
Key in https://youtube.com/shorts/g7u6xh0q69s?si=hcGRHHFb49wK4jNo
Hit search
The content cannot be found.
But it can be found on the browser

Expected behavior

Content Unavailable

Actual behavior

No response

Screenshots/Screen recordings

No response

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

[ABJ4403]

Will you give the log or at least confirm what the following error log that i also happen to get (happen so recently, someone reports it happen on him very early, but whatever it is now rolls out to evryyone now ): is the same exact ones you get:

Exception

• User Action: requested stream
• Request: Loading stream info: https://www.youtube.com/watch?v=EJzywDja5GU
• Content Country: ID
• Content Language: in-
• App Language: in_ID_#u-mu-celsius
• Service: YouTube
• Timestamp: 2025-10-18T21:10:57.209+07:00
• Package: org.polymorphicshade.tubular (yes its not actually NewPipe, its a fork of it called Tubular bcz i needed the sponsorblock and RYD lol, but i'll bet its the same with the original)
• Service: YouTube
• Version: 0.28.0
• OS: Linux Android 15 - 35

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:205)
	at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:101)
	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$2dkAz4sF5JerlwklOcqxZdlMoBU(ExtractorHelper.java:0)
	at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda7.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)

---

How to repro:

• Just open any video

Additional note:
Its quite hard to reproduce, at some point it hits, and other times it works as usual again, also changing IP didnt do anything, so whatever yt's doing is surely attempt to block 3rd party players from grabbing the video

[absurdlylongusername]

@zaniestp If you are getting an exception please provide the exception logs.

[sinonaluck-star]

Checklist

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

Affected version

0.28.0

Steps to reproduce the bug

Open the search button Key in https://youtube.com/shorts/g7u6xh0q69s?si=hcGRHHFb49wK4jNo Hit search The content cannot be found. But it can be found on the browser

Expected behavior

Content Unavailable

Actual behavior

No response

Screenshots/Screen recordings

No response

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

I hate error so much

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.