With the Firebase
3.6.0 launch comes the release of version 7.11.0 of the Google Mobile Ads
SDK, which has been optimized for the latest release of iOS. Any app that
supports iOS 10 should be built against v7.11.0 or higher of the Mobile Ads SDK.
AdMob publishers can grab the latest version of the SDK using the
Firebase/AdMob CocoaPod or via the Firebase manual
download . DFP publishers can get the latest version from the
Google-Mobile-Ads-SDK CocoaPod or via the Mobile Ads SDK
manual download .
What changed?
With the rollout of iOS 10, the App Store’s privacy
policy requires apps to provide a usage description when attempting to
access privacy-sensitive data, such as a user’s calendar
or Bluetooth .
You may have seen the following errors when attempting to upload your app to
iTunes Connect:
"This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSCalendarsUsageDescription key with a string value explaining
to the user how the app uses this data. "
"This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSBluetoothPeripheralUsageDescription key with a string value explaining to the user how the app uses this
data. "
The latest version of the Mobile Ads SDK has been updated for iOS 10, and will
no longer cause these errors to appear.
Information for MRAID creative designers
To comply with the App Store privacy changes, we removed support for the
mraid.createCalendarEvent() and
mraid.storePicture() methods. You will now see that the
mraid.supports("calendar") and mraid.supports("storePicture")
methods always return false. Per the MRAID v2 spec ,
MRAID creatives should check for support of these features before using them,
and correctly handle the case where they’re unavailable.
If you have any questions regarding these changes, please contact us through our
forum .
Tristan Emrich , Mobile Ads Developer Relations
