Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playing an album track doesn't look like its playing in Spotify apps #832

Open
christosk92 opened this issue Jan 23, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@christosk92
Copy link

christosk92 commented Jan 23, 2024

I've attached a picture at the bottom of this post indicating the problem.

It seems that the context-resolve endpoint (context-resolve/v1/uri) sometimes returns the UID of a track.
It does not seem to return the uid for album tracks:
image
Therefeore the PlayerState's track_uid is empty, which I think the clients use to find which track is playing.

If we play the track using the official clients (desktop and web), uid is filled
image

But I have no idea where to find this UID. The only place I seem to be able to find it is if we do an album resolve (GraphQL endpoint). But the desktop app seems to also know this ID without doing such call (transfering state).
So it's making me believe this could be a computed property.

Does anyone know how ?
Is there even a relationship between the base62 id (spotify:track:2XkDm5m2vPowecEAAR5gmb) and this seeminly base16 id? (67d43c187351cea560aa)

image

@christosk92 christosk92 added the bug Something isn't working label Jan 23, 2024
@devgianlu
Copy link
Member

I have always wondered whether the UID can be figured out in some way. So far I have ignored it.

@christosk92
Copy link
Author

The UID of a track is the same in the following scenarios:

  1. Track in user's saved songs
  2. Track in an album
  3. Track in a user playlist IF the track only appears once

For 3. If the track appears more than once, or the playlist is spotify generated, the UID seems to be very random.
But playlists isnt' really a problem because they are returned with the context-resolve endpoint.

I will try and do more research...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants