View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0031372||Marketplace Extensions||Google Mobile Ads||Public||2019-09-24 17:41||2020-04-13 08:56|
|Priority||Very High||Severity||B - Major||Reproducibility||100%|
|Platform||iOS||OS||iOS||OS Version||Pro x64|
|Target Version||Fixed in Version|
|Summary||0031372: Google Mobile Ads: v3.1.7 of Google Play Services asset causes iOS submission fail because of old Bluetooth framework|
|Description||The Google Mobile Ads extension within v3.1.7 of the Google Play Services asset causes iOS submission fail because of an old Bluetooth framework which the extension brings in during game builds.|
Users of this extension will get the following submission response from Apple:
Description: App Store Connect
We identified one or more issues with a recent submission for App Store review for your app, [REDACTED]. Please correct the following issues, then upload again.
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSBluetoothAlwaysUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).
The App Store Team
|Steps To Reproduce||1. Add our Google Play Services extension to a blank project.|
2. Ensure iOS is enabled in the various Copies To checkboxes for the ads extension.
3. Build the project for iOS and inspect the package which is made.
|2.x Runtime Found In||126.96.36.1994|
|2.x Runtime Verified In|
||Pretty certain this went into the 3.1.8 which went live late Sept (otherwise would be in 3.1.9 from mid-Oct), but we should confirm all is well and finally close as we test 3.2.0...|
||Fixed in v3.2.0 of the MP asset, which will be published asap.|