[GH-ISSUE #480] get_artist returns different channelId for some artists #357

Closed
opened 2026-02-27 23:00:21 +03:00 by kerem · 5 comments
Owner

Originally created by @Schtenk on GitHub (Nov 28, 2023).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/480

You missunderstand me in both #477 and #479.
What im saying is and that the channelId parsed from the get_artist response is the wrong one so if used again in with get_artist no songs are returned, as the links clearly shows.

sorry for trying to help, I wont make more issues.

Originally created by @Schtenk on GitHub (Nov 28, 2023). Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/480 You missunderstand me in both #477 and #479. What im saying is and that the channelId parsed from the get_artist response is the wrong one so if used again in with get_artist no songs are returned, as the links clearly shows. sorry for trying to help, I wont make more issues.
kerem 2026-02-27 23:00:21 +03:00
Author
Owner

@sigma67 commented on GitHub (Nov 28, 2023):

You know you can just reopen the issue or comment below.

If you followed the issue template it would be much easier to reproduce your issue. Here it is again:

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Additional context
Add any other context about the problem here, such as a code sample.

<!-- gh-comment-id:1829710917 --> @sigma67 commented on GitHub (Nov 28, 2023): You know you can just reopen the issue or comment below. If you followed the issue template it would be much easier to reproduce your issue. Here it is again: **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Additional context** Add any other context about the problem here, such as a code sample.
Author
Owner

@Schtenk commented on GitHub (Nov 28, 2023):

Tried to comment but for some reason I couldn't.
It isn't necessarily a bug depending on what channel id you want, which is why I didn't create a bug report specifically.

I just wanted to point out based on the comment in the code:
if 'musicShelfRenderer' in results[0]: # API sometimes does not return songs in mixin/browsing.py row:235
that using the channelId saved in the code:
artist['channelId'] = subscription_button['channelId'] in in mixin/browsing.py row:224
with get_artist will not return any songs, and that it may be the answer why the issue the comment refers to happens.

<!-- gh-comment-id:1829746658 --> @Schtenk commented on GitHub (Nov 28, 2023): Tried to comment but for some reason I couldn't. It isn't necessarily a bug depending on what channel id you want, which is why I didn't create a bug report specifically. I just wanted to point out based on the comment in the code: `if 'musicShelfRenderer' in results[0]: # API sometimes does not return songs` in mixin/browsing.py row:235 that using the channelId saved in the code: `artist['channelId'] = subscription_button['channelId']` in in mixin/browsing.py row:224 with get_artist will not return any songs, and that it may be the answer why the issue the comment refers to happens.
Author
Owner

@sigma67 commented on GitHub (Dec 18, 2023):

I mean yes, I guess this is a valid issue.

On the other hand, when you're calling get_artist you already have the channelBrowseId. So isn't it more useful to return the channelId from the subscribeButton in that case?

<!-- gh-comment-id:1861481909 --> @sigma67 commented on GitHub (Dec 18, 2023): I mean yes, I guess this is a valid issue. On the other hand, when you're calling `get_artist` you already have the `channelBrowseId`. So isn't it more useful to return the `channelId` from the subscribeButton in that case?
Author
Owner

@Schtenk commented on GitHub (Dec 18, 2023):

Sure, may just be a naming/documentation issue where both are called channelId. It should rarely be a problem but if a user saves the subscribe one for later thinking they are the same, may then lead to the issue occuring.

Only the channelId under the subscribe button can be used for subscribing if i remember correctly, so it is usefull.

<!-- gh-comment-id:1861666992 --> @Schtenk commented on GitHub (Dec 18, 2023): Sure, may just be a naming/documentation issue where both are called `channelId`. It should rarely be a problem but if a user saves the subscribe one for later thinking they are the same, may then lead to the issue occuring. Only the `channelId` under the subscribe button can be used for subscribing if i remember correctly, so it is usefull.
Author
Owner

@sigma67 commented on GitHub (Dec 19, 2023):

Renaming the key is difficult since it would break backwards compatibility. In light of this subscriptionChannelId would be the better name. I think we can add it to the docstring?

<!-- gh-comment-id:1862335194 --> @sigma67 commented on GitHub (Dec 19, 2023): Renaming the key is difficult since it would break backwards compatibility. In light of this `subscriptionChannelId` would be the better name. I think we can add it to the docstring?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ytmusicapi#357
No description provided.