[SoundCloud] Tracks tab for some artists doesn't completely load all tracks

[IArnaut2]

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. Switch to SoundCloud frontend
2. Search for an artist
3. Enter artist's page
4. Tracks tab doesn't completely load all tracks
5. Few tracks load and then the spinner spins
6. Playlists and Albums tabs work normally

Expected behavior

All tracks to be loaded in Tracks tab.

Actual behavior

Only few tracks load and then the spinner spins.

Screenshots/Screen recordings

Logs

No response

Affected Android/Custom ROM version

Android 13

Affected device model

Xiaomi Redmi Note 11

Additional information

No response

[kj2900]

I reported the same issues but with subscription instead like you go to a channel few scrolls and it's the same thing like yours hoping for a fix very soon

[venkatchalapathi]

Issue with SoundCloud extractor (NewPipeExtractor v0.24.8) on Hurtbox:

After loading a few tracks (tested 4), the extractor returns InfoItemsPage objects with 0 items but a non-null nextPage token, causing the client to loop on empty pages.

Behavior:

• Initial load: 0 items + valid nextPage.
• First 4 “load more” calls: 1 item each + new nextPage.
• From 5th call onward: empty pages + valid nextPage.

Suspected Cause: SoundCloud extractor generates nextPage tokens even for empty/unparseable pages. Ideally, it should return null/empty to signal the end.

**Logs : **

2025-08-23 21:58:18.973 ChannelInfo.getInfo returned. Tabs count=4
2025-08-23 21:58:19.207 ChannelTabInfo.getInfo returned. Items=0, NextPage=Page@2069b8a
2025-08-23 21:58:19.887 getMoreChannelTabItems returned. Items=1, NextPage=Page@2004bc4
2025-08-23 21:58:20.744 getMoreChannelTabItems returned. Items=1, NextPage=Page@cd00cd3
2025-08-23 21:58:20.933 getMoreChannelTabItems returned. Items=0, NextPage=Page@ae50d7d <-- empty page but non-null nextPage
2025-08-23 21:58:21.039 getMoreChannelTabItems returned. Items=2, NextPage=Page@905d0c3

Workaround:

• Detect consecutive empty pages client-side.
• Cleaner solution: fix the extractor to avoid returning tokens for empty pages.

[that1potato]

Hey, may I be assigned to work on this issue?

[absurdlylongusername]

@that1potato Done