Not all songs in a playlist are actually added in Google Play
hoopahmadness opened this issue · 4 comments
Even though the playlist definition is catching all these songs, only a subset of those songs are actually being saved to the playlist in Google Music. I've consistently had 116 songs over the past few weeks. I am not able to find a pattern in what is being added or not added.
I'm willing to participate in debugging and troubleshooting. I'm using the free version so this is my only playlist.
Update: I've deleted the playlist from Google, expecting it to reappear when Autoplaylists syncs. It has not done so. I tried deleting the playlist in Autoplaylists and remaking it from scratch (same name) and it still is not syncing to Google.
Hm, that's odd. Is it possible that there are duplicates in the list shown by Autoplaylists? I think if you had uploaded and bought/matched/added-via-subscription the same track that Autoplaylists will show both but only add one, but that seems like a pretty out-there case.
Here's a handful of more general debugging ideas:
- try deleting the autoplaylist (not just Google's copy) and then recreating it: the local and remote state might have gotten out of sync after deleting Google's copy
- if that doesn't work, reload the extension, then manually trigger a sync ("sync now"): that'll fix up anything relating to the cache being corrupted
- if that still doesn't work, open your logs, clear them, manually trigger a sync, then export them to a file and email them to me
I've emailed you a log. While I'm waiting, I think I'll uninstall try to start from there.
update:
uninstalling and starting over has solved my issue. The playlist is back and it includes all the songs I expect. I guess I can't do any more trouble shooting, I hope my logs are fruitful.
Glad to hear it! I usually don't recommend reinstalling since that wipes out all your local state, but it was a good call in your case: the extension was rejecting syncs for that playlist since the remote playlist was gone. Someday I'll get around to improving that situation (it's tracked in #160).
No leads on why the problem happened originally, though. Definitely get back in touch if it happens again!