iOS FairPlay SDK

The VUDRMFairPlay SDK is available for iOS. This documentation describes the steps to integrate and use the VUDRMFairPlay SDK on this platform.

Current release: v0.0.1 (105)

  • Overview
  • Requirements
  • Xcode integration
  • Information about Application Transport Security (ATS)
  • Example framework usage
  • Limitations
  • Known Issues
  • Release Notes


VUDRMFairPlay SDK enables Apple’s AVPlayer from AVFoundation to securely request licenses from Vualto’s VUDRM cloud based DRM platform using an extended instance of AssetResourceLoaderDelegate.

Three deployment scenarios exist, being Online Playback / Download and Offline Playback using an associated rental or persist token and two legacy methods which are restricted to Online Playback and use an associated rental token.

Make use of Apple’s AVPlayer and AVPlayerViewController to present users with the platform default skins, with DRM content. Or create your own video player based on AVPlayer.

This SDK has a number of key benefits:

  • Complete control over the entire AVPlayer lifecycle
  • Numerous optimisations to enable faster playback
  • Bitcode support
  • Support for building/linking against the simulators

The SDK is fully supported in both Objective-C and Swift applications.

A demo application written in Swift is available on request. Please contact to request a download of the SDK.


  • Minimum iOS deployment target of 9.x or higher
  • Xcode 11
  • Swift 5

Xcode Integration

  1. Copy the vudrmFairPlay.framework into your application’s project directory
  2. Navigate to your target and add vudrmFairPlay.framework to your ‘Embedded Binaries’. You should see that vudrmFairPlay.framework also now appears under ‘Linked Frameworks and Libraries’:

Information about application transport security (ATS)

iOS/tvOS 9 introduces Application Transport Security (ATS) which restricts the use of insecure HTTP. In order to permit playback of content over insecure HTTP exemptions need to be added into your application’s Info.plist. For example to disable ATS for any connection you would add the following into your application’s Info.plist:

        <key>NSAllowsArbitraryLoads</key> <true/>

More information about ATS can be found in Apple’s TechNote:


Before you can use the demo project or framework in your own project, for each instance you will require a URL to correctly prepared content, a content ID for the content (also referred to as assetID in previous versions), and a VUDRM token which must be correctly generated for the type of instance you wish to create. Example VUDRM token type templates available are:

  • Fairplay Rental {"type": "r","duration_rental": 3600}
  • Fairplay Rental tokens may only be used to stream online content to devices running iOS 9.x or higher.
  • Fairplay Persist {"type": "p","duration_persist": 3600}
  • Fairplay Persist tokens may be used to stream online content and play offline (downloaded) content to devices running iOS 10.x or higher.

For further information about VUDRM please contact us, or refer to our documentation:

Example framework usage

  • Import the VUDRMFairPlay module into your view controller:

    import vudrmFairPlay

  • Initialise an instance of VUDRMFairPlay:

Online Playback / Download and Offline Playback:

This method will request a license for the content from the license server based on the type of token presented for each instance of VUDRM FairPlay. The tokens may be FairPlay Rental or FairPlay Persist. FairPlay Rental token license requests will be provided a streaming content key, which may be used for online streaming only. FairPlay Persist token license requests will provide a persistent content key, which may be used for both online streaming, and offline playback of downloaded content.

When a download of an asset has been completed with a persist token policy, further playback requests will use the downloaded asset and associated content key, even when online.

There are significant limitations using AirPlay to stream any content that has been downloaded to the users device to an Apple TV. Please see the Limitations section for further information.

To initialise an instance, create an AVURL asset with your asset URL, and pass that in to the initialiser with the asset ID and a valid token.

Our example uses a single dynamically assigned instance. It would be expected that your application will manage the applications offline assets, including their ID’s, locations and download status. This method uses AVAssetDownloadURLSession with a URLSessionConfiguration to create an AVAssetDownloadTask for each configured asset. The asset ID should be unique to each asset, as it is used to create a path to, and identify, offline assets and their associated content keys.

The current example initialises an AVAssetDownloadURLSession with a URLSessionConfiguration upon loading the ViewController:

backgroundConfiguration = URLSessionConfiguration.background(withIdentifier: "AssetDownloadConfigurationIdentifier")
assetUrlSession = AVAssetDownloadURLSession(configuration: backgroundConfiguration!,
assetDownloadDelegate: self, delegateQueue: .main)

The asset configuration is then assigned upon use of the download or play buttons. To play an asset we create the assetDownloadTask and then assign the associated urlAsset to a player:

let asset = AVURLAsset(url: assetURL!)
self.drm = vudrmFairPlay(asset: asset, contentID: contentID, token: token)
assetDownloadTask = assetUrlSession.makeAssetDownloadTask(asset: asset, assetTitle: contentID,
assetArtworkData: nil, options: nil)!
assetDownloadTask.taskDescription = contentID

let playerItem = AVPlayerItem(asset: assetDownloadTask.urlAsset)
let player = AVPlayer(playerItem: playerItem)
let playerViewController = AVPlayerViewController()
playerViewController.player = player
present(playerViewController, animated: true) {

And to download, instead of assigning the asset to a player, call:


To cancel a download, call:


Legacy methods:

These are the originally provided methods which are for online playback use only, and are provided for ease of upgrade for legacy users. These methods now also require an asset ID in the initialiser to be compatible with the new framework.

  • Legacy method 1: Pass in a reference to your AVPlayer instance, the token to be used, and the asset ID when retrieving a license.
let player = AVPlayer(url: assetURL!)
self.drm = vudrmFairPlay(player: player, token: token, contentID: contentID)
  • Legacy method 2: Pass in a reference to your stream URL and the token to be used when retrieving a license. An AVAsset will be created by VUDRMFairPlay and this can be used to create your player.
self.drm = vudrmFairPlay(url:assetURL! as NSURL, token: token, contentID: contentID)
let playerItem = AVPlayerItem(asset: (drm?.asset)!)
let player = AVPlayer(playerItem: playerItem)

Finally, present your player:

self.player = player
let playerController = AVPlayerViewController() 
playerController.delegate = self as? AVPlayerViewControllerDelegate
self.present(playerController, animated: true, completion: nil)
playerController.view.frame = self.view.frame
playerController.player = self.player


With the VUDRMFairPlay framework installed, the example demo application can be initialised either via source code in the IDE, or using field entry on device.

  • To initialise via code in IDE, before running, simply replace the empty ViewController.swift values with your own valid values.
private var assetURL = URL(string: "")
private var token = ""
private var contentID = ""
  • To initialise via view controller on device, populate the URL, Token, and Asset Name fields with valid values. For ease of use, pasting into the URL field in the form URL + space + Token will auto populate both fields correctly. At runtime, any values in the URL and Token fields will override any hard coded values.


  • The current example application demonstrates a single instance of offline playback using an AVAssetDownloadURLSession with a URLSessionConfiguration to create an AVAssetDownloadTask for that asset. The example is not able to handle multiple assets. Users are expected to develop a method of mapping instances to assets within their application which will avoid multiple downloads of the same asset and will enable management of assets. The example includes legacy methods for online playback only. The use of these methods in conjunction with the default method may cause unexpected results and is not recommended.
  • The SDK does not support AirPlay of protected content after a persist content key has been persisted (content downloaded to device). Apple TV is never able to play protected offline/downloaded content with a persist content key. Attempting to do so may result in unexpected behaviours, crashes referring to the content key type, or the content may not load. Protected content may be transmitted with AirPlay before downloading content (and the content key has been persisted on the users device). Protected content may be transmitted with AirPlay using a streaming content key whenever the Apple TV has a network connection.
  • The SDK does not support playback of protected content when running in the iOS Simulator. Attempting to do so will result in an invalid KEYFORMAT error and the content will not load.

Known Issues

  • There is a known issue in iOS 11 where audio may not be correctly routed by the OS. This issue can be resolved by adding the following to viewDidLoad in your initial view controller:
do {
	if #available(iOS 10.0, *) {
		try AVAudioSession.sharedInstance().setCategory(.playback, mode: .default, options: [])
	} else {
		// Fallback on earlier versions
catch {
	print("Setting category to AVAudioSessionCategoryPlayback failed.")
  • If you believe you have found any further issues, please contact us at

Release notes

v0.0.1 (build 105) on 24/09/2019

  • Update required for XCode 11 / iOS 13

v0.0.1 (build 93) on 29/07/2019

  • Update license server DNS
  • Replaces instances of assetName and assetID with contentID to be consistent across DRM platform

v0.0.1 (build 85) on 27/03/2019

  • Update to Swift 5
  • Bug fixes and improvements

v0.0.1 (build 74) on 21/03/2019

  • Fix streaming content key handling
  • Bug fixes and improvements

v0.0.1 (build 70) on 15/01/2019

  • Update Persistable Offline framework to Swift 4.2

v0.0.1 (build 65) on 14/12/2018

  • Persistable Offline Release

v0.0.1 (build 58) on 05/11/2018

  • Update framework to Swift 4.2

v0.0.1 (build 44) on 09/04/2018

  • Bug fixes and improvements

v0.0.1 (build 15) on 05/04/2018

  • Update framework to Swift 4.1

v0.0.1 (build 11) on 27/03/2018

-Bug fixes and improvements

v0.0.1 (build 5) on 15/11/2017

  • Initial Release