[Bug] Video not executed due to an app network error

[Grimst]

Checklist (Your issue will be automatically closed if you delete this part)

• I make sure that there are no existing issues - open or closed - which I could contribute my information to.

• I understand that issues with limited impact, such as those occurring on specific devices or under specific network conditions, will not be fixed.

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.

• I have attached the error report in the issue.

**Describe the bug
when I do a search and click in the video list to open it, the video window is black and there is a message at the bottom "network error" with 2 buttons "retry" and "report". Then I have to click on "retry" btn several times to have the video that can appear with the description.
Probably happens more when I am connected with the WIFI.

Frequency
Randomnly happened :((

Steps to reproduce the bug
0- try with mobile datas and/or with WIFI
1- do a video search via the field
2- click on a video in the list
3- video open (normal view) but screen remained black and a message "network error" with 2 boutons "retry" and "report"

Device (e.g. Pixel 9 Pro)
Xiaomi redmi 9C M2006C3MG
Android 11 RP1A200720.011

Error report

Exception

• User Action: searched
• Request: first time reaction
• Content Country: US
• Content Language: en
• App Language: en
• Service: YouTube (Anonymous)
• Version: 4.2.1
• OS: Linux Android 11 - 30

Crash log

java.io.EOFException
	at okhttp3.internal.http2.Http2Stream$FramingSource.receive$okhttp(Http2Stream.kt:446)
	at okhttp3.internal.http2.Http2Stream.receiveData(Http2Stream.kt:276)
	at okhttp3.internal.http2.Http2Connection$ReaderRunnable.data(Http2Connection.kt:650)
	at okhttp3.internal.http2.Http2Reader.readData(Http2Reader.kt:180)
	at okhttp3.internal.http2.Http2Reader.nextFrame(Http2Reader.kt:119)
	at okhttp3.internal.http2.Http2Connection$ReaderRunnable.invoke(Http2Connection.kt:618)
	at okhttp3.internal.http2.Http2Connection$ReaderRunnable.invoke(Http2Connection.kt:609)
	at okhttp3.internal.concurrent.TaskQueue$execute$1.runOnce(TaskQueue.kt:98)
	at okhttp3.internal.concurrent.TaskRunner.runTask(TaskRunner.kt:116)
	at okhttp3.internal.concurrent.TaskRunner.access$runTask(TaskRunner.kt:42)
	at okhttp3.internal.concurrent.TaskRunner$runnable$1.run(TaskRunner.kt:65)
	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:923)

---

Additional context
I have installed pipepipe via F-Droid Repository.
Pipe Pipe version used: 4.2.1

EDIT, following the dosubot answer

@dosu

When I disabled the media tunneling in settings I have the same problem (black video screen) but the crash log is different (see 👇)

Exception

• User Action: requested stream
• Request: https://www.youtube.com/watch?v=Co5yqLP6k-w
• Content Country: US
• Content Language: en
• App Language: en
• Service: YouTube (Anonymous)
• Version: 4.2.1
• OS: Linux Android 11 - 30

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:226)
	at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:109)
	at org.schabi.newpipe.extractor.stream.StreamInfo.getInfo(StreamInfo.java:88)
	at org.schabi.newpipe.util.ExtractorHelper.getNewStreamInfo(ExtractorHelper.java:132)
	at org.schabi.newpipe.util.ExtractorHelper.lambda$getStreamInfo$3(ExtractorHelper.java:127)
	at org.schabi.newpipe.util.ExtractorHelper.$r8$lambda$YTHJjScxCJNO1LTCqs3IKy35iyY(Unknown Source:0)
	at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda5.call(Unknown Source:4)
	at io.reactivex.rxjava3.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:43)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4813)
	at io.reactivex.rxjava3.internal.operators.single.SingleDoOnSuccess.subscribeActual(SingleDoOnSuccess.java:35)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4813)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeFromSingle.subscribeActual(MaybeFromSingle.java:41)
	at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5330)
	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:15868)
	at io.reactivex.rxjava3.internal.operators.flowable.FlowableElementAtMaybe.subscribeActual(FlowableElementAtMaybe.java:36)
	at io.reactivex.rxjava3.core.Maybe.subscribe(Maybe.java:5330)
	at io.reactivex.rxjava3.internal.operators.maybe.MaybeToSingle.subscribeActual(MaybeToSingle.java:46)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4813)
	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: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:923)

---

[dosubot]

Hello @Grimst! I'm here to assist you with any bugs, questions, or contributions you may have. Let's work together to solve this issue.

A similar issue was previously reported and closed. The suggested solution was to disable media tunneling in the app settings, which can help resolve the problem of the video window remaining black with a "network error" message, especially when connected to WiFi ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[InfinityLoop1308]

I believe it is #884 . When video failed to start, does it take longer time to load? If yes it is possible you reach the loading timeout. You can test if https://github.com/InfinityLoop1308/PipePipe/actions/runs/13747005804, this debug version will explicitly say if you are encountering timeout in the error report.

[Grimst]

👍