Advanced User Authentication

In order for the iOS SDK to control the Spotify app, they will need to authorize your app. The functionality to do this is built in and can be implemented directly inside of your AppDelegate.swift:

In order to handle auth, we need to add a SPTSessionManagerDelegate inside of your AppDelegate.swift:

This will require us to implement the following three methods:

At a class-level, we can define our Client ID, Redirect URI and instantiate the SDK:

The authentication process provides a refresh_token, which can be stored locally inside your app. This can be used, along with your Client ID, Client Secret and Redirect URL, to obtain an access_token that is valid for 60 minutes.

However, as we strongly discourage the use of Client Secrets in your iOS app code, we have written two well-documented web server examples that can do this for you:

• Glitch
• One-click deploy with Heroku

Once you have set them up, and have the tokenSwapURL and tokenRefreshURL we can set this up in our AppDelegate.swift in a class-level closure:

iOS requires us to define a playURI (as shown in the last step) in order to play music to wake up the Spotify main application. This is an iOS-specific requirement. There's two values self.configuration.playURI accepts:

An empty value: If empty, it will resume playback of user's last track. Example:

A valid Spotify URI: Otherwise, provide a Spotify URI. Example:

With SPTConfiguration and SPTSessionManager both configured, we can invoke the authorization screen. Notice the optional campaign parameter, which can be set for attribution purposes to help indicate where the account linking was initiated from:

Once a user successfully returns to your application, we'll need to notify sessionManager about it by implementing the following method:

Now, when a user authorizes, they should return to your application with the sessionManager(manager: SPTSessionManager, didInitiate session: SPTSession) method being successfully invoked.