There were some issues with the Spotify Play button on our website since the Spotify Web player appeared.
There are 3 problems that I have noticed so far:
1) You need to double click to play the track
Pressing the play button (when the web player does not exist) is used to start playing the song in the background. Now, by clicking on the button, it first starts the web player (this is good), but does not automatically start playing music. He imports the playlist, but all that he does. It only works if the user manually presses the play button on the web player / clicks the button a second time (poorly in terms of ease of use - leaving our users confused). Along with this, to confuse users, the “Play” button indicates that “The track cannot be played” when this happens. However, if you click on this track again (either from the play button or from the actual web player), it works fine and the message disappears. Tested in Chrome (OSX and Windows 7), Safari (OSX) Here you can replicate: http://partysen.se/event/5/tanmays-awesome-party/
2) Invalid OAuth Token
Perhaps a related issue that has occurred since the web player started up is the play button that said “Invalid OAuth token” when trying to play something. I don’t have much more information to replicate, except that it started to happen on Mac OSX after starting the web player, and I also installed the mac spotify application. Tested on Chrome (OSX and Windows 7), Safari (OSX)
3) The button asks to install the application
Another problem: when you click the play button on the spotify web page, the application installation is requested. Also discussed here: https://stackoverflow.com/questions/16348049/spotify-play-button-not-working-in-google-chrome
This is only noted on Chrome on Mac OSX.
Questions
Can I fix it if the button uses Desktop or Web Player apps on average?
Can I get more information about the OAuth error described above?
source share