Supported Configurations for iOS
The Ooyala Mobile SDK for iOS supports:
- All devices with iOS 7 or later:
- iPhone 4 and later
- iPod Touch, 5th generation and later
- iPad 2 and later, iPad Mini (all generations), iPad Pro (all generations)
- MP4 and HLS streams
- HTTP Live Streaming (HLS)
- MP4 video container (subject to Apple's cautions and requirements)
- AirPlay for the following types of content:
Note: Content with Widevine Classic DRM is not supported in AirPlay mode.
- Content only
- Content with ads (Ooyala Pulse, FreeWheel, Google IMA, VAST)
- Secure content with and without ads (eHLS)
- We don’t recommend AirPlay for Widevine Classic because it causes playback issues and visual problems for the end user.
- Closed captions are also not supported for Widevine encrypted assets for AirPlay mode. Closed captions with AirPlay are only available for HLS files because this is what Apple TV supports natively.
- Google is deprecating Widevine Classic DRM. We recommend that you use eHLS as an alternative.
- Widevine Classic is no longer supported, which means that .wvm, .wv_mp4, and .wv_hls files are no longer supported.
- Objective-C and Swift-based applications
The Ooyala HTML5 Player V3 and Ooyala mobile SDK for iOS are now certified for iOS 9.
<key>NSAppTransportSecurity</key> <dict> <!-Include to allow all connections (DANGER)-> <key>NSAllowsArbitraryLoads</key> <true/> </dict>
Important Update for ATS and HTTPS
By the end of 2016, Apple will enforce HTTPS streaming for iOS. This means that by January 1, 2017 Apple will make App Transport Security (ATS) mandatory for all developers who want to submit their apps to the App Store.
What Does This Mean to you?
If you use the Ooyala iOS SDK and are planning an app resubmission after January 1, 2017, you will need to update your SDK to support ATS. Starting SDK version 4.18.0 (released September 20, 2016), the Ooyala SDK started shipping with default API requests through HTTPS. If you use iOS SDKs prior to 4.18.0, you will need to update your iOS client application if you plan an app update/resubmission after January 1, 2017. For Widevine and PlayReady DRM customers specifically, updating your iOS application also means reprocessing your assets to support the latest Ooyala DRM solution on mobile.
Impact and effort involved depends on your setup. Below’s a summary of the impact for DRM and Ad Monetization customers. For both cases, note that you must change the serving configuration to HTTPS. The most common cases (Clear or Encrypted HLS, which use Ooyala Ingestion and Ooyala CDNs) will be easily resolvable by TS, however more complicated cases (if you use your own CDN, or use remote streams) will need to be handled differently. For VoD HLS streams, Glowworm also applies and the serving configuration (VoD and live) must changed to HTTPS. For remote streams, we will have to ask all customers with iOS playback to ensure that their CDN is serving all manifests and TS files via HTTPS.
Everything within the VAST XML must be HTTPS, and this includes Ad Tracking URLs, video URLs, and static image URLs. This means that you may need to reach out to their ad provider to ensure that HTTPS is enforced. If you are using Backlot ‘Ad Sets’, the VAST parameters must be changed to HTTPS. For Pulse, IMA, and Freewheel, there will be a need to provide SSL network requests, and the SDK libraries must support SSL as well.
Contact Ooyala support for more information.
Customers using Widevine Classic and PlayReady mobile must migrate to FairPlay HLS and Widevine Modular. This requires asset reprocessing, app updates and resubmission to the App store. Widevine Classic is no longer a supported product of Google and is not ATS compliant, so if you use Widevine Classic, you must migrate to FairPlay HLS for iOS and Widevine DASH for Android.
The Ooyala SDKs have been shipping without the PlayReady DRM mobile library, so if you use a PlayReady HLS solution on mobile, you must transition to FairPlay HLS and Widevine Modular DASH using Ooyala SDK 4.18.0 to support updates to Apple ATS. Ooyala fully transitioned to FairPlay and Widevine Modular solution on mobile, and we have been shipping our SDKs without the VisualOn/Secure player. We have not updated our SDKs with the latest VisualOn/Secure player libraries. VisualOn's support of the SecurePlayer component to support PlayReady DRM on the Ooyala mobile SDKs have ceased as of August 11, 2016.
Contact Ooyala support for more information.