Amazon service update broke Collections on Desktop app

If you reauthorize Amazon does it help? Fixed my Amazon issues here.

https://en.community.sonos.com/controllers-and-music-services-229131/amazon-mising-from-search-6934526

That’s odd, I’ve always thought data collection was at the product (speaker) level, and the resulting data was pushed to the controller for display. But you would know better than I. 

The only thing I could assume, under that scenario, is the data format has changed in some way, that the desktop client can’t understand…but we’re getting way out of my comfort zone, and you’re much more equipped to understand any changes that may have been made in the data. 

Did some more testing: “Collections” returns zero items for Desktop, and also the root enumerator is returning .svgs for the top level item graphics instead of bitmaps (the Desktop controller can’t render svgs). Seems like someone forgot to test the updated Amazon endpoint against the desktop controllers.

Sadly made no difference.

​@controlav, Did you try resetting the Desktop Controller (under “Help”).

No, as I can see exactly where the API is failing (in my own apps) and have zero need to “reset” the Sonos app (which does nothing for this).

I debugged this further: Amazon’s root json object includes 3 children from “container”, and the mobile apps (and SonoPhone) use this, and it works.

However, the SMAPI call getMetadata(“container”) returns 0 children, and the Desktop apps (and my apps too) use this, and don’t work.

If Sonos/Amazon want the Desktop apps to still work correctly then the SMAPI server needs to be fixed. It seems that Sonos themselves might own this code, and not Amazon, but it’s not entirely clear to me.

I mostly use the desktop app, so not being to access the User Playlists is ‘unhelpful’.  wasn’t sure what the issue was, until I found this topic - thanks ​@controlav for debugging this and hope for a fix soon.

I also mostly use the desktop app, and not having Amazon Music collections available makes Sonos pretty useless. I’ve uninstalled and reinstalled Sonos and deleted and re-added Amazon Music, and now see that I’m not the only one with this problem. Will there be a notice from Sonos with this is resolved?

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.