Soundcloud frequent crashing when playing songs on 0.27.6. 0.27.5 works fine

[davidasunmo]

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.27.6

Steps to reproduce the bug

1. Play a soundcloud playlist
2. Wait

Expected behavior

All songs play from start to finish

Actual behavior

It will frequently crash with Something went wrong error, and it will skip to the next song, or go back to the start of the song. The crashes seem to follow a pattern as often it will crash at the exact same part of a track every time depending on which track I start playing first. However, since this problem occurs only on 0.27.6 but not 0.27.5 I know this is a NewPipe issue, not a SoundCloud issue.

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/lusperae/avid-modv-sawanohiroyuki-nzk
• Content Country: GB
• Content Language: en-GB
• App Language: en_GB
• Service: SoundCloud
• Timestamp: 2025-02-24T20:29:33.506Z
• Package: org.schabi.newpipe
• Service: SoundCloud
• Version: 0.27.6
• OS: Linux Android 9 - 28

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.loop(Looper.java:214)
	at android.os.HandlerThread.run(HandlerThread.java:65)
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:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

---

Affected Android/Custom ROM version

Android 9

Affected device model

Samsung Galaxy S8

Additional information

This is NOT a duplicate of #9925. Although the repro steps are identical, that one happens occasionally, does not exhibit the same behaviour or patterns, and has been present for several years, so most likely does not have the same root cause or fix.

Whereas this problem only appeared on 0.27.6 and happens constantly, predictably, and annoyingly. Using 0.27.5 does not have the problem, but then of course I can't watch YT videos on 0.27.5 because it doesn't work :)

[Bimbo-Bungus]

I am having this same issue with the latest stable release, as well as on the latest stable release of Tubular. I think this error also occurs with enqueued Youtube videos, and also with auto-enqueue playlists. If you say that an earlier version doesn't have this issue, a temporary solution (or permanent, if you like the idea) might be to keep Soundcloud subscriptions and playlists on the older Newpipe and continue watching Youtube on the latest fork, like Tubular.