-
Notifications
You must be signed in to change notification settings - Fork 257
mobileclient.search() returns an empty 'playlist_hits' list #614
Comments
I tested this on my accounts and see the same thing. It looks like Google just isn't returning playlist results. They still show up in the app, so my bet would be they moved that functionality clientside. If that's the case, we should probably just remove the result type from the call. |
Playlists are still returned in the call response. My library is showing this behavior as well. Will report back after diagnosing what has changed. |
FYI, I broke out my old phone to capture a search call to find it had a different response format. But when I make the same call through my library, it returns the same format as we have always used sans the playlist responses. So, I'm digging into it. |
Alright, there's a new URL param. I'll put something together soonish; it's dinner time. |
So, the new response format looks like so:
Genre cluster is returned always but empty. |
Just an update. Started this, partially just re-familiarizing myself with the code. Got busy with other things for a few days. Will finish over weekend and submit PR on Monday most likely. |
Update search call for new response format [Closes #614]
I am probably missing something here. I still can't see the playlist results. This is what I get with 'develop':
|
No, I'm seeing this now, too, in both gmusicapi and my own library. But I definitely got results before the weekend. Just checking on it quick, I'm getting two separate station clusters. Wondering if one of those is full of playlists. And since I changed things to use the type from the cluster instead of each individual result, maybe that's throwing things off. Will report back. |
I was searching an artist, and the two different station clusters is expected as they do separate 'Featuring' result section from other radio station results. |
Should also be noted that playlist hits aren't tested in the tests specifically because they have been proven inconsistent in the past. Which is why the tests passed. |
Well, this is seemingly a result of Google Music handling the Not sure if we should give this a couple days to see if its temporary or just change the @juanrubio Just for confirmation. If you set |
@thebigmunch Good find!. Yes, with
|
Alright then, it's up to @simon-weber whether he wants me to submit a PR changing the default right away, documenting the new behavior for those that want to get more than 100 results of certain types and don't care about playlist/situation hits, or wait to see if the behavior reverts. |
Nice find. I think we should probably just change the default to 100 -- my guess is that the previous behavior was unintended anyway. |
Are there plans for a new release? |
I was hoping to resolve the login issues before releasing, but haven't had a chance to look at it lately. I suppose I should just release anyway. |
Understood. If there are login issues currently being fixed, I can definitely wait for that. Just for reference, what is the issue number? |
#620 is the most relevant (it's breaking CI as well). |
Hi,
Sorry if this has been asked before, but I've noticed that mobileclient.search() now doesn't return any playlist hits. I'm sure this used to return playlist results some time ago. Any idea of what is going on?
I'm using gmusicapi 11.0.3 and a GMusic paid subscription.
The text was updated successfully, but these errors were encountered: