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
We have a use case where we want to start Spotify music playback of a playlist at a pre-selected trackIndex.
This is possible when connected to the Spotify app through the app remote by using: SPTAppRemotePlayerAPI playItem:skipToTrackIndex:callback:.
However if the Spotify app isn't running in the background we need to launch it before connecting by calling SPTAppRemote authorizeAndPlayURI: or SPTSessionManager initiateSession. Here we can specify a playlist URI to initiate playlist playback when launching Spotify app, but we can't specify what playlist trackIndex we want to start playing when Spotify launches.
I would like to suggest additions to SPTAppRemote and/or SPTConfiguration to allow specifying skipToTrackIndex for associated playURI (if applicable) for when launching the Spotify app from the SDK.
Thanks for your time and consideration!
The text was updated successfully, but these errors were encountered:
Hi!
We have a use case where we want to start Spotify music playback of a playlist at a pre-selected trackIndex.
This is possible when connected to the Spotify app through the app remote by using:
SPTAppRemotePlayerAPI playItem:skipToTrackIndex:callback:
.However if the Spotify app isn't running in the background we need to launch it before connecting by calling
SPTAppRemote authorizeAndPlayURI:
orSPTSessionManager initiateSession
. Here we can specify a playlist URI to initiate playlist playback when launching Spotify app, but we can't specify what playlist trackIndex we want to start playing when Spotify launches.I would like to suggest additions to SPTAppRemote and/or SPTConfiguration to allow specifying skipToTrackIndex for associated playURI (if applicable) for when launching the Spotify app from the SDK.
Thanks for your time and consideration!
The text was updated successfully, but these errors were encountered: