How to find usages of Reason Required API?

Question

Created Mar ’24

Replies 4

Boosts 0

Views 1.7k

Participants 3

We are getting warnings from Apple, ITMS-91053 Missing API declaration, for categories Disk Space, Timestamp, and more. But we've checked our source code to make sure we are not making any of the entry points at issue.

We suspect they are being called from one of the 3rd party frameworks we use, some of them are binary xcframeworks.

Is Apple planning on extending their warnings to provide more information about where the usages are? Are we left to find it ourselves? Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.

Boost

Answer 1

endecotp OP

Mar ’24

Is Apple planning on extending their warnings to provide more information about where the usages are?

”File a bug”, ha ha ha.

Are we left to find it ourselves?

https://developer.apple.com/forums/thread/748621

I don’t know if that works for .xcframeworks; if not it’s probably fixable to do so.

Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.

That is certainly what most people will do.

0

Answer 2

hotngui OP

Mar ’24

That is certainly what most people will do.

So sad... Kind of defeats the purpose.

Thanks for the link to your handy-dandy tool

0

Answer 3

hotngui OP

Mar ’24

Along the same lines, is there a correct location in a Swift Package where the PrivacyInfo.xcprivacy should go so that it can be read correctly Apple? I am seeing it in a few different locations after a Quick Look at some packages.

0

Answer 4

rsippert OP

Mar ’24

Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.

This may not be possible for some of these. For example, our app has two missing API declarations flagged in our widgets extension, which must be coming from third-party code because one of them is for UserDefaults which we are already declaring in our app. According to Apple's documentation, we should not need a separate privacy manifest for widgets, so adding one to address this seems like it would not work.

0