ITMS-91053: Missing API declaration

Getting into LiveCode for iOS? Ask your questions here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
LG73
Posts: 36
Joined: Fri Jun 05, 2009 8:25 am
Location: Vancouver, BC, Canada
Contact:

ITMS-91053: Missing API declaration

Post by LG73 » Fri Apr 05, 2024 5:15 am

My latest app beta update submissions for TestFlight have generated warning e-mails about issues with missing API declarations. The specific API categories are NSPrivacyAccessedAPICategorySystemBootTime, NSPrivacyAccessedAPICategoryFileTimestamp and NSPrivacyAccessedAPICategoryDiskSpace.

This is something that has to be resolved by May 1st. In the e-mail for each of the 3 API issues, Apple says: "While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code."

I'm using LiveCode 10.0.0 (dp 7). Anyone know which inclusions or standalone settings for iOS might be triggering the above?
Cheers,

Phil
LG73 - Vancouver's Hit Music Mix!
http://www.LG73.ca/

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7240
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: ITMS-91053: Missing API declaration

Post by jacque » Fri Apr 05, 2024 6:39 pm

I did a quick look at the requirements and I think these probably relate to the main functions of your app, which I think does music playback, right? The timestamp one specifically mentions audio playback calculations. If your app stores any data on the device, that would explain the diskspace requirement. I suspect the boot time is also related to audio calculations.

It probably wouldn't be too hard to adjust the manifest to include the specific reasons you need to access these days APIs. You must use the specified reasons here:https://developer.apple.com/documentati ... reason_api
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

Klaus
Posts: 13829
Joined: Sat Apr 08, 2006 8:41 am
Location: Germany
Contact:

Re: ITMS-91053: Missing API declaration

Post by Klaus » Fri Apr 05, 2024 7:06 pm

As far as I know, LC is already working on an update which will support these new requirements.

MWCoastMedia
Posts: 32
Joined: Fri Jan 16, 2015 5:31 pm

Re: ITMS-91053: Missing API declaration

Post by MWCoastMedia » Thu Apr 18, 2024 8:28 pm

Arrived here after submitting a new build to the App Store today and getting flagged for this too using LC 9.6.11. My app has NO iOS requirements.

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7240
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: ITMS-91053: Missing API declaration

Post by jacque » Fri Apr 19, 2024 6:10 pm

MWCoastMedia wrote:
Thu Apr 18, 2024 8:28 pm
Arrived here after submitting a new build to the App Store today and getting flagged for this too using LC 9.6.11. My app has NO iOS requirements.
It's probably APIs the engine is calling. Look at the manifest in a text editor and see what's in there. Usually there's a list at the bottom with LC default strings you can edit.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

LiveCode_Panos
Livecode Staff Member
Livecode Staff Member
Posts: 821
Joined: Fri Feb 06, 2015 4:03 pm

Re: ITMS-91053: Missing API declaration

Post by LiveCode_Panos » Tue Apr 30, 2024 5:17 pm

Hello all,

We have added a lesson on how to create a privacy manifest and include it in the iOS app:

https://lessons.livecode.com/m/4069/l/1 ... ur-ios-app

You can follow the lesson and add your own privacy manifest to the Copy Files section in any existing LiveCode version (e.g. 9.6.11 or 10.0.0 DP-7).

Note that very shortly we will release 9.6.12 RC1 and 10.0.0 DP-8 that will automatically include a sensible default privacy manifest when building an iOS app, which will be replaced by your own custom one *if* you provide one in the Copy Files - but this will probably not be necessary in most cases.

Hope this helps.

Kind regards,
Panos
--

Post Reply

Return to “iOS Deployment”