With the release of iOS9, it is required that each publisher update to our latest SDK, version 2.6, to compile for iOS 9.
To aid publisher compliance with App Transport Security (ATS) in iOS 9, AdColony is facilitating the transition for each attribution and tracking partner. Until this transition is complete, apps built against iOS 9 MUST disable ATS to allow video ads to run.
The AdColony SDK Wiki contains explicit instruction on how developers can disable ATS for the AdColony SDK, while still using it elsewhere in their app.
App Transport Security (ATS) requires apps to make secure network connections via SSL and enforces HTTPS connections through its requirements on the SSL version, encryption cipher, and key length. We are currently working with all of our partners in an effort to become ATS-compatible. At this time, however, we require that publishers disable ATS for AdColony. This can be done two ways; please see below.
The easiest way to turn off ATS for AdColony is to disable it for the entire application by adding the following entry to the app’s plist:
<key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key> <true/> </dict>
Disabling ATS for AdColony does not require that it be turned off for the entire application, however. In an effort to be aligned with Apple’s recommendations around ATS, publishers may want to ensure their apps are as ATS-compliant as they can be. If you are one of those publishers, then Option 2 is what you want. To disable ATS for AdColony but keep it enabled for other domains, simply add the XML from Option 1 to your app’s plist (which disables ATS for the entire application), and then add an exception for each domain known to be ATS-compliant. Please refer to the example below.
<key>NSAppTransportSecurity</key> <dict> <key>NSAllowsArbitraryLoads</key> <true/> <key>NSExceptionDomains</key> <dict> <key>example.com</key> <dict> <key>NSIncludesSubdomains</key> <true/> </dict> </dict> </dict>