Amazon service update broke Collections on Desktop app

Hard to say, there’s frequently no details given in their release notes, but I’d think at some point, it will just start working. I’d give it two or three updates, though, as I would think one or two releases are already ‘locked in’. But it also, I suspect, depends on how egregious the bug is considered, and how many folks it may be affecting. We’ll have to wait and see. 

Hello ​@controlav,

I’ve received confirmation that this issue has been resolved.

Feel free to reply here and let us know as well.

That sounds frustrating, especially if collections were working normally before the Amazon service update. If the desktop app is still able to play the tracks but the collections themselves are missing or inaccessible, it seems more likely to be an integration or metadata issue than a problem with the local library. Hopefully Sonos and Amazon can identify what changed and restore the previous collection behavior without requiring users to rebuild everything.

Can confirm that Collections in the Desktop app is working now, and I can access my Amazon Library.

Thanks

Almost: Collections works now, thank you, but there’s an issue with Library under that, the word “Albums” is missing:

Unrelated to this is that the Albums list itself has a lot of “Content Unavailable” (and the mobile app is the same). And the order of the Albums seens totally random.

I debugged the missing “Albums” item, it is because of this XML which getMetadata(“library”) returns:

There should not be a displayType on the “Albums” item.

Also all of the “Content Unavailable” albums have an id of “unauthorized” which seems suspicious.

Actually I misspoke: the presence of the displayType is not actually the problem, but the definitions of the DisplayTypes themselves. Amazon are using invalid StringId values, eg “Album Title”, “Artist Name” instead of tokens like “title”, “artist” etc. As they are invalid StringIds they “translate” to nothing and this causes problems downstream. The real fix is to correct the DisplayType definitions, the displayType attribute on the Albums container parent can stay once this is fixed and the word “Albums” will by magic reappear in the Library list.

Speaking from relative ignorance, isn’t that a change / correction that needs to be done by Amazon, not Sonos changing the SMAPI for all services? 

Normally yes, but it is my belief that a few of the SMAPI gateways may be at least partially owned by Sonos - I think Spotify one is, plus my request to get a fix in the Amazon SMAPI in this thread was granted, so it seems like I have the attention of the right folks here.