Please can anyone confirm that they can consistently receive calls to the delegate method appRemoteDidEstablishConnection after connecting with appRemote with the Spotify app v8.5.22 ??

Or confirm that they consistently can't, like it is my case.

Sometimes (rarely) appRemoteDidEstablishConnection gets called, but then the next time I run the app, it does not anymore.

Spotify app v8.5.22 seems to have broken something in the iOS Spotify SDK/API

This happens on my app and also on the latest NowPlayingView app from the demo projects.

Here’s my experience:

Noticed my app didn’t connect to the Spotify app on my iPhone.

Noticed the Spotify app got updated to v8.5.22 on my iPhone.

Tried to run my app on my iPad, it did connect.

Noticed that the Spotify app on my iPad had not been updated yet.

Updated the Spotify app on my iPad to version 8.5.22.

Now my app doesn't connect to the Spotify app on my iPad.

Spend the next 4 hours trying to find the bug. Can’t know exactly what’s happening but these are my findings so far:

The appRemote seem to connect, it logs AppRemote: Established a connection to the Spotify app.

But the delegate methods don’t get called: appRemoteDidEstablishConnection didFailConnectionAttemptWithError didDisconnectWithError, none of those methods ever get called.

Also, even after appRemote.isConnected returns true, appRemote.playerAPI appRemote.userAPI appRemote.imageAPI appRemote.contentAPI, all of those equal nil

Also tried to call appRemote.disconnect(), then appRemote.connect(), same situation

I’m running the latest NowPlayingView project with the latest SDK (just downloaded it a few hours ago), running iOS 12.4.1

Other users seem to have encountered the same problem: issues #149 (now closed but not solved) and #114 (down to the most recent comments).

Thanks for reading this long post!

The new release of Spotify was auto-loaded onto my phone overnight. Took me a couple hours to determine this broke the example. Can you please provide a working update.

Hi Spotify,

I'm having an issue with AppRemote.connect(). Sometimes after a successful SessionManager didInitiate I try to set the appremote.accesstoken and then appremote.connect but after redirecting to the Spotify and back to my app I receive this:

Spotify didFailConnectionAttemptWithError Optional(Error Domain=com.spotify.app-remote Code=-1000 "Connection attempt failed." UserInfo={NSLocalizedDescription=Connection attempt failed., NSUnderlyingError=0x282a1c0f0 {Error Domain=com.spotify.app-remote.transport Code=-2000 "Stream error." UserInfo={NSLocalizedDescription=Stream error., NSUnderlyingError=0x282a1c090 {Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, NSLocalizedRecoverySuggestion=Reconnect the transport to the Spotify app., NSLocalizedFailureReason=A stream error has occured in the transport.}}, NSLocalizedRecoverySuggestion=Ensure the Spotify app is installed, and try to reconnect., NSLocalizedFailureReason=Could not connect to the Spotify app.})

Even though I am currently listening to music in the Spotify App. I have set the configuration.playURI to "" and I have the requested scope to be: .appRemoteControl, .playlistReadPrivate. I'm testing with Xcode 10.2 and an iPhone X with 12.1.4

If I restart Spotify I am able connect again, and this only seems to happen once a day or so.

Any suggestions for further debugging or solutions would be greatly appreciated.

Thank you!

Issue Type: Bug Spotify iOS SDK Version: Beta 25 User Impact: Severe Reproducibility: 100% (first observed 9/11/2018 8:00am CDT)

When passing in a playlist URI given by a SPTPartialPlaylist object to a request for promotion to a PlaylistSnapshot object, a 401 error is returned and users cannot view their playlist tracks, play songs from their playlists, or add and remove tracks. Along with the 401, an error reason of "Invalid Playlist URI" is given.

Example of URI provided by SPTPartialPlaylist: "spotify:playlist:0tLwSYR5m7BxP9uxKHfhK1" Broken SDK method call: [SPTPlaylistSnapshot playlistWithURI: accessToken: market: callback: ]

Error output obtained in the callback block: Error Domain=com.spotify.ios-sdk Code=401 "Invalid Playlist URI" UserInfo={NSLocalizedDescription=Invalid Playlist URI}

Judging by the changes to this GitHub project, I can tell that no work continues on the 2014-2018 'iOS SDK'. However, this is still where developer.spotify.com points developers to to report issues with the existing iOS SDK (as well as the new Remote SDK). Any help resolving this would be appreciated– hundreds of active Premium users in production are potentially affected by this issue today.

Thanks in advance!

Currently trying to migrate to this SDK from the prev. streaming one. Having a lot of trouble figuring out a particular issue re: appRemote delegate. I followed the Quick Start guide, have verified that the session successfully inits, and also see these logs...

AppRemote: Connecting... AppRemote: Established a connection to the Spotify app.

...however none of the appRemote delegate methods are being called. I have set appRemote.delegate = self within my main AppDelegate, and have implemented all the req. delegate methods.

    func appRemoteDidEstablishConnection(_ appRemote: SPTAppRemote) {
        print("connected!", playerRemote != nil, playerRemote?.playerAPI != nil) // DOES NOT PRINT
        playerRemote?.playerAPI?.subscribe(toPlayerState: { (success, error) in
            print(success, error)
        })
    }
    
    func appRemote(_ appRemote: SPTAppRemote, didDisconnectWithError error: Error?) {
        print("disconnected!", error) // DOES NOT PRINT
        sptSessionManager?.renewSession()
    }
    
    func appRemote(_ appRemote: SPTAppRemote, didFailConnectionAttemptWithError error: Error?) {
        print("failed!", error.debugDescription) // DOES NOT PRINT
    }

For reference, here is the rest of the setup:

    // MARK: Application Delegate

    func initializeSpotify() {
        sptConfiguration = SPTConfiguration(clientID: "###", redirectURL: URL(string: "###")!)
        sptConfiguration!.tokenRefreshURL = URL(string: "###")!
        sptConfiguration!.tokenSwapURL = URL(string: "###")!
        sptConfiguration!.playURI = ""
        sptSessionManager = SPTSessionManager(configuration: sptConfiguration!, delegate: self)
        playerRemote = SPTAppRemote(configuration: sptConfiguration!, logLevel: .debug)
        **playerRemote!.delegate = self**
        
        let requestedScopes: SPTScope =  [.appRemoteControl] // .streaming?
        
        if #available(iOS 11.0, *) {
            sptSessionManager!.initiateSession(with: requestedScopes, options: .default)
        } else {
//            sptSessionManager!.initiateSession(with: requestedScopes, options: .default, presenting: <#T##UIViewController#>)
        }
    }

    func applicationDidBecomeActive(_ application: UIApplication) {
        if let _ = playerRemote?.connectionParameters.accessToken {
            // successfully reaches here and connects, resetting delegate to be extra sure (doesn't work either way)
            playerRemote!.delegate = self
            playerRemote?.connect()
        }
    }
    // MARK: SPTSessionManager Delegate
    
    func sessionManager(manager: SPTSessionManager, didInitiate session: SPTSession) {
        print("successfully init spt session", playerRemote != nil) // prints true
        playerRemote!.connectionParameters.accessToken = session.accessToken
    }
    
    func sessionManager(manager: SPTSessionManager, didFailWith error: Error) {
        print("failed to init spt session", error) // DOES NOT PRINT
        sptSessionManager?.renewSession()
    }
    
    func sessionManager(manager: SPTSessionManager, didRenew session: SPTSession) {
        print("renewed spt session", session) // DOES NOT PRINT
    }

My thoughts were maybe it had something to do with the way I was initializing the var globally? I am running this on Xcode 10.1 Beta on a physical iPhone X running iOS 12 with Spotify installed. Could this be an issue?

In the previous SDK we had fine control over Spotify's volume with SPTAudioStreamingController. I'm not sure if this is possible with the new Remote SDK?

I have been building a music app which integrates Spotify SDK in iOS. every thing is working fine but the problem is when I have to play a specific song from a playlist by clicking on that song I am unable to do that and song doesn't play, even I can retrieve information about that specific song but unable to play. I am using the Spotify iOS SDK version 1.0.2

With demo provide in the new SDK for objective-c if the phone has Spotify app install it works well but if the phone doesn't have the app Spotify installed I am having the error:

"INVALID_CLIENT: Invalid redirect URI"

the option is set to: SPTDefaultAuthorizationOption

On the dashboard Redirect URIs is set: spotify-login-sdk-test-app://spotify-login-callback

On the dashboard Bundle IDs is set: com.spotify.sdk.SPTLoginSampleApp

On the app static NSString * const SpotifyRedirectURLString = @"spotify-login-sdk-test-app://spotify-login-callback";

URL Schemes: spotify-login-sdk-test-app

ruby file CLIENT_CALLBACK_URL = "spotify-login-sdk-test-app://spotify-login-callback"

Did I forget something?

First off, just want to say that this SDK has been great to work with, and it's awesome that Spotify offers an SDK to build on top of an already great product! Appreciate all of the work that has gone into building & maintaining this.

One thing that is critical to my use of this SDK that is missing, however, is the ability to work with specific playlists. In the application I'm building, I need to (1) display a (known) subset of playlists from the list of all the user’s playlists, and (2) when the user chooses a playlist, play that playlist starting at a particular song/index in that playlist. There are a couple of challenges with both tasks in the current SDK, and I’d love to request some features to help with this!

Challenge: Getting a list of user’s playlists is clunky

The best way that I’ve found so far to get a list of a user’s playlists requires traversing a tree of content items through 3 calls in succession of -fetchRootContentItemsForType:callback: and -fetchChildrenOfContentItem:callback:. Essentially, I start with a -fetchRootContentItemsForType with the default type, scan the results for a “Your Library” content item, use that item as the parameter for -fetchChildrenOfContentItem, scan those results for a “Playlists” content item, and then use that as the parameter for a final -fetchChildrenOfContentItem call. While this process does work, it feels a little risky because it depends on a predictable title and/or URI pattern for the “Your Library” and “Playlists” content items - if Spotify ever changes those, then the code that traverses the tree would break.

Alternatively, I could query the web API for playlists, but then I wouldn’t be able to take advantage of the offline functionality of this SDK, and also, that would not give me a full-fledged SPTAppRemoteContentItem object which is needed for the -playItem:skipToTrackIndex:callback: method.

Proposed Solution

Add a new -fetchContentItemsForType:callback: method spec to the SPTAppRemoteContentAPI protocol that can directly query lists of content items for things like playlists in a user’s library (but could also work for other types, such as albums/artists/podcasts in a user’s library, or the home/browse/recently played items). The SPTAppRemoteContentTypes can be expanded to support these additional types, or a new enum could be created for these queries.

Challenge: No way to get all of a user’s playlists

Even after following the above method to get a list of playlists, it only gets maximum 20 child content items from the user’s playlists, and it doesn’t seem like there’s a way to get more. If the specific playlists that I’m looking to display to the user are outside of their first 20 in their ordering, then there’s no way that I can display these playlists. Again, querying the web API isn’t an option for the same reasons as above.

Other issues referencing this: #109

Proposed Solution

Add a paging mechanism to the -fetchChildrenOfContentItem method. In simplest form, that could just be adding an offset parameter to the method.

Challenge: Playing an item from a particular index requires an SPTAppRemoteContentItem object

The -playItem:skipToTrackIndex:callback: method works great, but it requires passing in an SPTAppRemoteContentItem object as a parameter. Given the first 2 challenges, it’s clunky at best to get that object, and at worst it’s impossible for any playlist outside of a user’s first 20.

Alternatively, it’s possible to use the -play:callback: method using the playlist’s URI, but that doesn’t allow the capability to start at a specific index. I could follow the -play call with a bunch of -skipToNext calls until I’m at the right index, but that seems pretty clunky too... what if there are hundreds or thousands of songs on the playlist?

Other issues referencing this: #113, #63, #41

Proposed Solution(s)

If the first 2 challenges are addressed, then no solution would be needed here… these would still help though!

Add a -playURI:skipToTrackIndex:callback: method spec to the SPTAppRemotePlayerAPI protocol that can play a resource by URI starting at a particular track index.

Also, add a -fetchContentItemForURI: method spec to the SPTAppRemoteContentAPI protocol that can fetch a SPTAppRemoteContentItem object directly from a URI. This would allow for checks for whether the item is playable and/or available offline if needed.

I am getting the playlist and playing it, and simultaneously showing all the tracks in a collection view. I want user can select any track and play it. After the track ends, the next song should start playing which happens in Spotify APP, but no API exposed to make an app work like that using SPotify SDK.

To select a song I am enqueuing the selected track, and after getting the callback result calling playerAPI.skip(toNext:), this start playing the selected song but it's not the correct solution, as song ends it does not go to next song after that track.

Hi everyone,

I've downloaded the Spotify SDK, and am just trying to run the demo app, NowPlayingView Demo project out of the box, and am having trouble connecting to Spotify.

I do have Spotify premium, music is already playing when I build the app on XCode. I'm deploying my iPhone6. I'm able to see the "Spotify App Remote" view, but after tapping the "Play" button, it redirects me to my Spotify app, then redirects back and crashes. It fails on "didFailConnectionAttemptWithError."

Here's the console log: 2019-01-03 16:40:55.739977-0500 NowPlayingView[45496:1889155] AppRemote: Connecting... 2019-01-03 16:40:55.814105-0500 NowPlayingView[45496:1889155] AppRemote: Established a connection to the Spotify app. 2019-01-03 16:40:55.985353-0500 NowPlayingView[45496:1889155] AppRemote: Failed to authenticate with the Spotify app. 2019-01-03 16:40:55.987605-0500 NowPlayingView[45496:1889155] AppRemote: Failed to establish a sesssion with error: Error Domain=com.spotify.app-remote.wamp-client Code=-1001 "wamp.error.authorization_failed" UserInfo={details={ message = "No token provided."; }, NSLocalizedFailureReason=wamp.error.authorization_failed} didFailConnectionAttemptWithError 2019-01-03 16:40:59.247482-0500 NowPlayingView[45496:1889155] AppRemote: Disconnected with error: (null)

After extensive research, it looks like the access token is null, hence the failure to authenticate? I've also tried creating my own app in the developer portal, added in my own clientID and redirectURI.

What am I missing?

Thanks so much!

Shortly after going into the background my app is suspended by IOS At this point I have lost control over spotify playback Background mode capability is enabled in Xcode and the app store I have tried playing a silent audio using another audio package while playing tracks using the spotify SDK, making geolocation requests every 10 seconds, to no avail as the app is still suspended The spotify IOS SDK is not of use to me if I cannot control it while in the background This problem does not occur while using other audio streaming APIs. I would ask spotify to create a new streaming API to prevent this problem

import UIKit

/// Connection status view class ConnectionStatusIndicatorView : UIView {

enum State {
    case disconnected
    case connecting
    case connected
}

var state: State = .disconnected {
    didSet {
        self.setNeedsDisplay()
        if state == .connecting {
            if displayLink == nil {
                let selector = #selector(setNeedsDisplay as () -> Void)
                displayLink = CADisplayLink(target: self, selector:selector)
            }
            displayLink?.add(to: RunLoop.main, forMode: RunLoopMode.commonModes)
        } else {
            displayLink?.remove(from: RunLoop.main, forMode: RunLoopMode.commonModes)
            displayLink = nil;
        }
    }
}

var displayLink: CADisplayLink?

override func didMoveToSuperview() {
    super.didMoveToSuperview()
    self.clearsContextBeforeDrawing = true;
    self.backgroundColor = UIColor.clear
}

override func draw(_ rect: CGRect) {
    guard let context = UIGraphicsGetCurrentContext() else {
        return

In the use case I am most interested in the user is actually using their phone to stream to another device (i.e. home stereo). If I set my spotify client up to be playing to that device and I try to authorize my iOS app I get the following error:

TCP Conn 0x2838780b0 Failed : error 0:61 [61] 2022-12-06 16:51:08.709121-0800 Cyclops[1788:131885] AppRemote: Failed connection attempt with error: Error Domain=com.spotify.app-remote.transport Code=-2000 "Stream error." UserInfo={NSLocalizedDescription=Stream error., NSUnderlyingError=0x28012d2f0 {Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, NSLocalizedRecoverySuggestion=Reconnect the transport to the Spotify app., NSLocalizedFailureReason=A stream error has occured in the transport.}

The Spotify app then resets the device to the local device. Ideally I'd love to have the devices exposed in through the SDK but at the very least I'd like to not change the playback device and have the phone continue to provide playback. Is there a way to accomplish this?

When I get the access token and there is internet connection, I get a URL back in the following format

my-app-name//spotify-login-callback/?spotify_version=8.7.84.360#access_token=ReallyLongAccessToken&token_type=Bearer&expires_in=3600

If I run the same flow without internet connection, I get back the same thing, sans token.

my-app-name://spotify-login-callback?spotify_version=8.7.84.360

I was under the impression that as long as I have authenticated before on the device, I would be able to then authenticate offline. Was the Spotify app made incompatible with the SDK? Or is there a different way to go about offline auth

I'm seeing a lot of logs from our app about failing to handle requests to open Spotify URLs. The URLs in question are mostly along the lines of:

• host://callback?error=user_canceled&error_description=user%20aborted&spotify_version=8.7.68.568
• host://callback?error=unknown_error&error_description=error%20domain%3dcom.spotify.connectivity....
• host://callback/?error=access_denied&spotify_version=8.7.68.568

And when passing them to sessionManager.application(application, open: url, options: options) we're getting a return value of false which is misleading as these are URLs Spotify should handle. As a result we are then subsequently feeding the same URLs to all our other URL handling code, and eventually returning false to the OS which seems incorrect.

Can someone verify if this is intended behavior, and if so why? And if it is not intended, is there a fix?