Global Platform Ops & CS, NOC, Certification, Engineering & Exchange Spaces have been MIGRATED to the Corp Confluence instance,
*****Do not use these four Spaces in this instance any longer!!****
Skip to end of metadata
Go to start of metadata

Last Updated Jan 6, 2017 Return to Top

iOS 10 introduces changes that might impact your app and its AdMarvel SDK integration. This document reviews action points for you to ensure that your applications are not rejected by the Apple app store.

Adding keys in Info.plist

In iOS 10, Apple extends the scope of its privacy controls by requiring advertisers to declare the potential use of a user’s camera, calendar, photo library, etc. in the plist, ahead of time. As always, the user would still be prompted to confirm permission to use any of such features, for each request. To ensure the best possible user experience when the AdMarvel SDK uses these features, we strongly recommend you to add the following entries to your app’s plist:

  • NSCameraUsageDescription
  • NSPhotoLibraryUsageDescription
  • NSMicrophoneUsageDescription
  • NSRemindersUsageDescription
  • NSCalendarsUsageDescription

Rendering non-secure ads in your application's web view


  1. Go to Info.plist of your app.
  2. Under App Transport Security Settings, add NSAllowsArbitraryLoads in a new row.
  3. Set NSAllowsArbitraryLoads property to YES.

Use NSAllowsArbitraryLoads until 01/01/2017 to have the least impact on your available demand. For apps released after 01/01/2017, AdMarvel recommends that you use NSAllowsArbitraryLoadsInWebContent in your app's Info.plist

Next steps