You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling pause() on a valid SPTAppRemotePlayerAPI instance with an open connection properly pauses playback, but the callback never returns with a result or error object.
Also, once the playback has paused, the connection closes. Attempting to call connect() on the SPTAppRemotePlayerAPI object never reconnects. Alternatively, attempting to reauthorize also does not allow reconnection.
The text was updated successfully, but these errors were encountered:
Currently, when audio is paused the Spotify app is suspended in the background. This requires an app switch to resume playing music using the authorizeAndPlayURI: API. There is no player state callback after calling pause as the connection to the Spotify app has been terminated. Please see the included demo app and how it handles resuming playback after a pause. I also recommend checking out our Application Lifecycle Guide for more info on when to connect and disconnect App Remote.
This behavior is subject to change, so you should monitor connection states instead of assuming a pause will always result in a disconnect.
I'm wondering how is one meant to implement a Play/Pause button? Are we expected to call authorizeAndPlayURI after the user pauses music for any action (such as skip)? And if so why does the resume function exist.
Calling pause() on a valid SPTAppRemotePlayerAPI instance with an open connection properly pauses playback, but the callback never returns with a result or error object.
Also, once the playback has paused, the connection closes. Attempting to call connect() on the SPTAppRemotePlayerAPI object never reconnects. Alternatively, attempting to reauthorize also does not allow reconnection.
The text was updated successfully, but these errors were encountered: