DBus OpenUri issue...

[mattydaniels21]

For some reason I'm having a hard time with the DBus OpenUri command. It was working great and then I updated Spotify (I hadn't in a while) and it seems to play the appropriate song at first, and then when I issue the command to play a different song, the song appears on the Spotify browser but the song doesn't actually play. The returned message is "method return sender=:1.250 -> dest=:1.600 reply_serial=2", but I'm assuming that isn't telling me anything useful.

Any ideas?

[jooon]

It sounds like you are using OpenUri correctly, but unfortunately the behavior has changed with versions.

0.9.x started playing the track or the first track in an album/artist/playlist uri.

1.0.x up to 1.0.28 only shows the view of an album/artist/playlist uri and only starts playing a track if the client is paused

1.0.29 and later only shows the view of a track/album/artist/playlist uri

The reason is because the MPRIS OpenUri method was just connected to some internal uri opening method that has changed behavior. The change in the internal behaviour could be explained when you compare it with how the Spotify Play Button https://developer.spotify.com/technologies/widgets/spotify-play-button/ has evolved, but it is a regression of the MPRIS api. https://community.spotify.com/t5/Help-Desktop-Linux-Windows-Web/SOLVED-Linux-Spotify-DBus-MPRIS2-sup...

Since there is little reason for a remote control api to only show the view of an uri with no means of actually start playing anything, this is considered a bug which should be fixed.

[jooon]

The message you see "method return sender=:1.250 -> dest=:1.600 reply_serial=2" is debug output from the command you use to send the dbus message. It does mean that the message went through though. The OpenUri method does not return anything so that's why you don't see anything more than that.