Privacy Manifest

[amcalgates]

According Apple docs:

From Fall 2023 you’ll receive an email from Apple if you upload an app to App Store Connect that uses required reason API without describing the reason in its privacy manifest file. From Spring 2024, apps that don’t describe their use of required reason API in their privacy manifest file won’t be accepted by App Store Connect.

Does Telegraph use any APIs mentioned here? If so, are there plans to include a privacy manifest? I'm not 100% sure what that'd even look like, but this thread maybe has a little insight.

[JuneLee61]

+1，同问

[amcalgates]

Looks like the hard deadline for this is May 1st:

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. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api

[linhaosunny]

Any Plan support Apple Privacy Manifest for cocoapods ? @yvbeek

[donly]

has one or more issues:
ITMS-91053: Missing API declaration. 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.

[yvbeek]

I've included the Privacy Manifest, see https://github.com/Building42/Telegraph/blob/main/Sources/PrivacyInfo.xcprivacy
I'm not sure if CocoaPods is going to pick it up correctly. I've made changes to the Podspec, but I'm running into CocoaPods linter issues because of CocoaAsyncSocket. Not sure if I can fix those issues without creating a fork of CocoaAsyncSocket 😞

[mobileteo]

Any update on this?