mirror of
https://github.com/spotipy-dev/spotipy.git
synced 2026-04-27 00:25:54 +03:00
[GH-ISSUE #1033] Querying Spotify for song details is not returning with the 'Track ID'. #618
Labels
No labels
api-bug
bug
dependencies
documentation
duplicate
enhancement
external-ide
headless-mode
implicit-grant-flow
invalid
missing-endpoint
pr-welcome
private-api
pull-request
question
spotipy3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotipy#618
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Artholos on GitHub (Oct 18, 2023).
Original GitHub issue: https://github.com/spotipy-dev/spotipy/issues/1033
Describe the bug
Querying Spotify for song details is not returning with the 'Track ID'. Here's my code to search for popular songs in various genres. I need three details about each track: Name, artist, and track ID. But the track ID is not being returned. According to the documentation on https://developer.spotify.com/documentation/web-api/reference/search shows that the track ID located in: 'tracks > items > id'
Here's my function that returns list of top 10 songs in a genre:
Expected behavior
I expect that the track ID would be returned so it can be used later in other Spotify API calls.
Output
Environment:
@dieser-niko commented on GitHub (Nov 3, 2023):
Generally a good idea. I think it would be best to use JSON schemas and have them as python objects.
But I'm not sure if the OpenAPI definition from Spotify is actually representing the API correctly. If I'm not mistaken, there is/was actually a flaw in the definition, but I'll have to check that again sometime.
Edit: found a related issue: https://github.com/spotipy-dev/spotipy/issues/975
@dieser-niko commented on GitHub (May 23, 2024):
I'm currently going through some issues and I'm realizing that I probably commented on the wrong issue. Do you still need help or can we close this here?
@Artholos commented on GitHub (May 23, 2024):
Oh heyo, I'm so sorry, I totally forgot. I couldn't find a work around to the issue so I gave up and went to do something else. It looks like you found the related problem, so I think we're good to close this issue.
Thanks so much!
@dieser-niko commented on GitHub (May 23, 2024):
Yeah no, that's the thing. The related issue doesn't seem to be related to your issue.
@Artholos commented on GitHub (May 23, 2024):
Alright then, I've dug up the program and the issue is still happening, probably because I haven't changed anything yet. What do you suggest?
@dieser-niko commented on GitHub (May 23, 2024):
I've spotted two issues. The first one is here:
It seems that you've filtered out the ID.
The second one here:
I think that one's self explanatory.
@Artholos commented on GitHub (May 23, 2024):
おh thank you! I can't believe I missed those haha! I suppose a second set of eyes really makes all the difference. I'm getting a completely new error now down in the database part. Looks like I have a project again! Thank you so much for your help :D