NSPhotoLibraryUsageDescription Key

[BB8]

I introduced AdMob version 7.42.1 to my app and uploaded the binaries to App Store Connect, but I was notified by Apple that the binaries were invalid.

The reason is that there is no NSPhotoLibraryUsageDescription setting in info.plist.

However, the app does not use a photo library.

This time, AdMob has also been updated to the latest version in line with the app version upgrade.

In apps that introduced previous AdMob versions, it was not necessary to set the NSPhotoLibraryUsageDescription key in info.plist, so I think that the NSPhotoLibraryUsageDescription key has been changed to be necessary in the current AdMob version.

I do n’t think I ’ll need access to the photo library to display ads, and allowing access to unnecessary photo libraries can be annoying to app users.

We want you to eliminate access to unnecessary photo libraries and avoid setting the NSPhotoLibraryUsageDescription key.

The following is a notification message when the binaries are disabled after uploading the app binaries to App Store Connect.

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 NSPhotoLibraryUsageDescription 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.

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for reaching out to us. Let me do the best I can to assist you on this.

With regard to your concern, It's odd that you are encountering that behavior as our SDK has removed the NSPhotoLibraryUsageDescription requirement long time ago. 
That said, can you confirm to me that this is happening even without our SDK?

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5001UEIzST:ref

[BB8]

Thank you for your reply.

Since it is mandatory to install Mobile Ads SDK, I cannot remove the SDK and upload the binary to App Store Connect to check.

Mobile Ads SDK 7.42.1 was downloaded manually without using CocoaPods.
I updated the SDK to the latest version 7.48.0 and uploaded NSPhotoLibraryUsageDescription Key without setting it, but the same result was obtained.

The app does not access the photo library, and the uploaded binary has not been updated except for the Mobile Ads SDK.

Before archiving binaries with Xcode, we are performing a Clean Build Folder operation.


2019年8月14日水曜日 12時41分35秒 UTC+9 BB8:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for getting back to us. I'll share this to the rest of the team and get back to you with their feedback.

[BB8]

As a trial, I removed the Mobile Ads SDK from the app, and also deleted the code that displays AdMob, and then uploaded the built binary to App Store Connect, the same problem occurred.

Therefore, this is not an issue with the Mobile Ads SDK, but is more likely to be an Apple App Store Connect issue.

I decided to report this issue to Apple and ask for investigation.

Since this is presumed not to be a problem on the Mobile Ads SDK side, it will be closed.

Thank you for your response.

2019年8月14日水曜日 12時41分35秒 UTC+9 BB8: