We have a significant issue with my dev team related to in app playback of music from user's connecting their Spotify account to our app. We are using the most recent Spotify iOS SDK (and Web API for some things too) and the devs say that this only allows for "remote-control" of the Spotify player. So if I play a song inside our app (Resonate) and then look at Spotify, same song is playing. And if I change song on Spotify player, then that changes what's playing in Resonate. This is a serious limitation that we do not want. But the devs say this is the only thing the iOS Spotify SDK allows ... which makes no sense to me as almost every other app I look at, including other apps like Vertigo Music, SoundShare, SoundHound, Shazam, etc all allow for in app music play that is separate from and independent of the Spotify player. We have a huge disconnect on this and my devs have basically given up. Some research I have done might indicate that the reason is Spotify's previous SDK allowed independent music play and perhaps apps are continuing to use Spotify's old SDK, but I have no idea if this is true.
Another related issue is that my devs say that in order to play a song through the SDK, it is necessary that the Spotify application is active and if the iOS system considers that Spotify is not open, then when song play is initiated my app is flipping back out to Spotify to re-authorize (and in fact if music is playing in Resonate and the Spotify app is closed, then the music stops playing). The re-authorization that I describe works but it makes no sense because no other apps that I have seen using Spotify connections seem to do this. Once a user connects their Spotify in the app, then to me frequent re-authorization should not be necessary.
Any relevant information would be most appreciated.