Skip to content

Error: Network timeout from History #13367

Open

Description

@AnkurBambhrolia

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.
  • I have read and understood the AI policy. The content of this bug report is not generated by AI.

Affected version

0.28.4

Steps to reproduce the bug

  1. Go to history
  2. Click on video
  3. Play video
  4. Recieve timeout error

Expected behavior

To play the video

Actual behavior

The video does not play and I recieve a timeout error. This does not happen if I play a video from a Playlist or a new video from suggested videos. Only when I try to play a video from my history section

Screenshots/Screen recordings

No response

Logs

Exception

  • User Action: play stream
  • Request: Player error[type=ERROR_CODE_IO_NETWORK_CONNECTION_TIMEOUT] occurred while playing https://www.youtube.com/watch?v=74acAfkM8Wo
  • Content Country: US
  • Content Language: en-US
  • App Language: en_US
  • Service: YouTube
  • Timestamp: 2026-03-19T09:20:31.334-04:00
  • Package: org.schabi.newpipe
  • Service: YouTube
  • Version: 0.28.4
  • OS: Linux samsung/pa3qsqw/pa3q:16/BP2A.250605.031.A3/S938USQU5BYI3_OYN5BYI3:user/release-keys 16 - 36
Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:17)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:317)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:273)
	at android.os.Looper.loop(Looper.java:363)
	at android.os.HandlerThread.run(HandlerThread.java:85)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$HttpDataSourceException: java.net.SocketTimeoutException: Read timed out
	at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:303)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:161)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:3)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:277)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:130)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:11)
	at com.google.android.exoplayer2.source.chunk.InitializationChunk.load(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:40)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:35)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at java.lang.Thread.run(Thread.java:1119)
Caused by: java.net.SocketTimeoutException: Read timed out
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
	at java.net.SocketInputStream.read(SocketInputStream.java:173)
	at java.net.SocketInputStream.read(SocketInputStream.java:143)
	at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.readFromSocket(ConscryptEngineSocket.java:994)
	at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.processDataFromSocket(ConscryptEngineSocket.java:958)
	at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.-$$Nest$mprocessDataFromSocket(Unknown Source:0)
	at com.android.org.conscrypt.ConscryptEngineSocket.doHandshake(ConscryptEngineSocket.java:242)
	at com.android.org.conscrypt.ConscryptEngineSocket.startHandshake(ConscryptEngineSocket.java:224)
	at com.android.okhttp.internal.io.RealConnection.connectTls(RealConnection.java:196)
	at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:153)
	at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
	at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
	at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
	at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
	at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
	at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:411)
	at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:542)
	at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:106)
	at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:30)
	at org.schabi.newpipe.player.datasource.YoutubeHttpDataSource.open(r8-map-id-ce0307bac2c3f16e8dc2f832773b0599f307ee51c82b5550b73911d8a6d3ce37:51)
	... 10 more


Affected Android/Custom ROM version

One UI 8.0

Affected device model

Samsung Galaxy 25 Ultra

Additional information

I've tried using 2 different internet sources: my wifi and my ATT phone data. Both yield the same outcome

Activity

  1. added
    bugIssue is related to a bug
    needs triageIssue is not yet ready for PR authors to take up
    on Mar 19, 2026
  2. ShareASmile commented on Oct 26, 2026

    @ShareASmile
    Collaborator

    Have you tried to clear cache from settings?

  3. added
    waiting for authorIf the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed.
    on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue is related to a bugneeds triageIssue is not yet ready for PR authors to take upwaiting for authorIf the author doesn't respond, the issue will be auto-closed. Otherwise the label will be removed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions