iOS 10 and xCode 8

Solar2D iOS
#1

Hey all, while trying to submit an update to the iOS app store I ran into the issue many are having here: https://forums.coronalabs.com/topic/63382-itunes-connect-processing-stopped-for-build-an-app/

So in an attempt to resolve this I have updated my xCode to v8, and did a build using 2945 and iOS beta 10.  After submitted to the app store I no longer get the thinning error, however I received an email with the following issues:

Dear developer,

We have discovered one or more issues with your recent delivery for “KOMBO”. To process your delivery, the following issues must be corrected:

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 NSPhotoLibraryUsageDescription 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 NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

My app doesn’t access the calendar, photo library, or camera.  Anyone know of a way to resolve these?

#2

Ok so I tried adding this to my build.settings:

iphone = { plist = { NSCalendarsUsageDescription = "Testing", NSPhotoLibraryUsageDescription = "Testing", NSCameraUsageDescription = "Testing" } }

After I resubmitted the build it seemed to resolve the issue stated in the first email.  However now I am getting the app thinning error.  So unfortunately at this time upgrading to xCode 8 and iOS 10 isn’t resolving the original issue.

#3

Yea, the new pList entries is apparently tested before the app thinning tests happen.

Rob

#4

Will there be a list compiled showing which plugins trigger each of these plist warnings?  As stated in the first post my app doesn’t explicitly use any of those 3 libraries.  I’m assuming those are arising from plugins

#5

Are you using the AddressBook plugin?

#6

No

#7

I have same problem.

My app not using the photoLib or camera.

But…

This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSPhotoLibraryUsageDescription 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 NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

Xcode 8, iOS 10.

Plugins:

plugins = { ["plugin.notifications"] = { publisherId = "com.coronalabs" }, ["plugin.utf8"] = { publisherId = "com.coronalabs" }, ["CoronaProvider.analytics.flurry"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.google.iap.v3"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true } }, },

What’s wrong?

#8

I’m also getting these issues. Not using the camera, photolibrary etc…

On latest daily build.

Thanks! :slight_smile:

#9

The photo/camera access is part of the Corona Core. You just need to include the entries. Since you’re not using them, your users should not get prompted for permissions which is where those items will show. You can leave the text empty or provide a generic message.

Address book is part of a plugin. I’m not sure at this time why it’s getting flagged, but its easy to work around by adding a plist entry to satisfy the automatic check.

Rob

#10

So if we don’t use photo/camera, can we ignore this mail from apple?

#11

Anyway, after uploading successfully my new app version (iOS 10) with Application Loader:

  • I’ve received the “photo/camera” mail from Apple

  • Even if the upload was a success, the build doesn’t appear in iTunes Connect

So I’m stuck.

Don’t know what to do.

Any help will be appreciated.

#12

You need to add the plist entries to your build.settings.  Please see my 2nd post in this thread

#13

Thank you JonPM :slight_smile:

But you said :

…  However now I am getting the app thinning error.  So unfortunately at this time upgrading to xCode 8 and iOS 10 isn’t resolving the original issue…"

So I thought that if you resolved this problem, you’ve got another one. Am I wrong?

Best

#14

No this was prior to Corona fixing the issue on their side with daily build 2948.   Now I am using build 2951 and it is working properly

#15

Ok, sorry I misunderstood!

Thank you very much for your help JonPM  :unsure:  :slight_smile:

#16

Hi,

I have the same mensage:

"This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSPhotoLibraryUsageDescription 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 NSCameraUsageDescription key with a string value explaining to the user how the app uses this data.

Once these issues have been corrected, you can then redeliver the corrected binary."

I work with “Application Loader 3.6” and “Coronalabs Version 2016.2951” (2016.9.17)

Then I include:

          NSCalendarsUsageDescription = “Testing”,
          NSPhotoLibraryUsageDescription = “Testing”,
          NSCameraUsageDescription = “Testing”,

in build.setting, and the app is “build has completed processing” … I’m waiting the Apple OK

#17

If you have those three keys in your settings.iphone.plist{} table you should pass the submission.

Rob

#18

I spent time because of this problem, too.

This problem was difficult to understand by the first pattern.

Though it can be uploaded in this case, it can’t be released.

I was surprised at the error mail which has reached.

I noticed a problem by 2951 and arrived here.

It was returned to 2948, but I didn’t settle a problem.

I added setting of plist.

> NSPhotoLibraryUsageDescription = “****”,

> NSCameraUsageDescription = “****”,

It’s much anxiously, but can I release it?  :unsure:

#19

My application could be released.   :slight_smile:

 

> iphone = {

>   plist = {

>     NSPhotoLibraryUsageDescription = “Unused by an application”,

>     NSCameraUsageDescription = “Unused by an application”,

 

There is a possibility that a string isn’t being seen in Apple.

I showed a character string as Test to a screen, and was rejected by a review many times.

So I couldn’t write “Testing”.  :rolleyes:

#20

I encountered this issue for the first time today as well. I do not wish our users to see that the app requires permissions for something that it doesn’t actually use. It causes people and especially parents to kids to avoid the app.

Please update your core so that it does not require these permissions. The core code should be as clean as possible and without ‘hidden features’. As we begin paying for our license again, its a good time to get rid of all the extra baggage in there.