Regular crashes playing Soundcloud playlists

[ChemoCosmo]

Checklist

• I am able to reproduce the bug with the latest version.
• 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.25.0

Steps to reproduce the bug

1. Start Playlist, for example https://soundcloud.com/user-428882203/sets/grim-dark-warhammer-40k-40000
2. Wait a couple of songs
3. Music stops
4. Look at Error message

Expected behavior

Playlist should be played without interruptions and errors

Actual behavior

NewPipe throws an error playing Soundcloud playlists. Observed with at least 3 different playlists. NewPipe plays multiple songs until it suddenly stops after one song and shows an error notification. This happens constantly after 10-30 minutes.

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://soundcloud.com/graham-plowman/for-the-emperor-warhammer-40k
• Content Country: DE
• Content Language: de-DE
• App Language: de_DE
• Service: SoundCloud
• Version: 0.25.0
• OS: Linux Android 10 - 29

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:632)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:604)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loop(Looper.java:214)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403
	at com.google.android.exoplayer2.upstream.DefaultHttpDataSource.open(DefaultHttpDataSource.java:404)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:258)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:786)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:599)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.source.ProgressiveMediaPeriod$ExtractingLoadable.load(ProgressiveMediaPeriod.java:1005)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	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:919)

---

Affected Android/Custom ROM version

Android 10 - e/OS 1.5q

Affected device model

Fairphone 3

Additional information

No response

[av01d1ngx4]

Your internet connection could be the root of the problem. I attempted to replicate your issue, but nothing occurred.

[ChemoCosmo]

I'll try with mobile data (instead of wifi) next and let you know if the issue doesn't occur anymore.

[ChemoCosmo]

Problem also occurs with mobile data, which is usually very reliable.

InvalidResponseCodeException: Response code: 403 doesn't really sound like a timed out connection to me.

I will update my OS in the next days. Maybe that does the trick...

[ChemoCosmo]

Came back to tell, that an update to Android 11 did not fix the issue.

[opusforlife2]

Response code: 403

This has nothing to do with timing out, as you say. It's the server saying you're forbidden to access the resource, for whatever reason. Happens on YT as well.

[absurdlylongusername]

This is a bug I've also been experiencing for a while, also getting basically the exact same stack trace too. Idk if I get it for YT videos as I mostly have soundcloud in my playlists, but it happens multiple times a day.

[opusforlife2]

403 errors tend to be temporary on YT. Don't know about SC.

[ChemoCosmo]

In that case it would be nice if Newpipe would just resume the playlist in case one song is not accessible.

[opusforlife2]

Newpipe does skip to the next song in the queue. It won't work if your queue has only one song, though.

[simonai1254]

For me this issue occurs as well, regardless if on WiFi or mobile data, multiple times a day. I mostly listen in the background, not sure if it happens in the normal mode as often/at all.

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://soundcloud.com/samfeldt/sam-feldt-x-lucas-steve-feat-wulf-summer-on-you-1
• Content Country: GB
• Content Language: en-GB
• App Language: en_GB
• Service: SoundCloud
• Version: 0.27.0
• OS: Linux samsung/p3sxxx/p3s:14/UP1A.231005.007/G998BXXUAGXDA:user/release-keys 14 - 34
• Device: Samsung Galaxy S21 Ultra / One UI 6.1 - Android 14

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:644)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:616)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:230)
	at android.os.Looper.loop(Looper.java:319)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 403
	at com.google.android.exoplayer2.upstream.DefaultHttpDataSource.open(DefaultHttpDataSource.java:413)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:263)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:796)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:609)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.source.hls.HlsMediaChunk.prepareExtraction(HlsMediaChunk.java:495)
	at com.google.android.exoplayer2.source.hls.HlsMediaChunk.feedDataToExtractor(HlsMediaChunk.java:468)
	at com.google.android.exoplayer2.source.hls.HlsMediaChunk.loadMedia(HlsMediaChunk.java:437)
	at com.google.android.exoplayer2.source.hls.HlsMediaChunk.load(HlsMediaChunk.java:394)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	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:1012)

---

Newpipe does skip to the next song in the queue.

This is correct, but to some degree annoying, especially since going back to the song before and continuing where it crashed usually works fine.