Apple's update to their API policy - Required Reason in Privacy manifest

[kdvmgn]

Describe the feature or problem you’d like to solve

From Fall 2023 Apple starts rolling out new privacy requirements, The apps and third-party SDKs should contain a privacy manifest file when they access required reason API. SkeletonView SDK uses UserDefaults which is required description of use in PrivacyManifest.
Otherwise, apps that don’t describe their use of required reason API in their privacy manifest file won’t be accepted by App Store Connect. Here is a link to the [Apple documentation].(https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).

Proposed solution

Add a PrivacyInfo.xcprivacy file and the following information to the Privacy Accessed API Types section

• Privacy Accessed API Type: User Defaults
• Privacy Accessed API Reasons: CA92.1: Access info from same app, per documentation

Additional context

Apple documentation

[mayios]

Even though I updated to 1.30.4, there is no privacyinfo file inside. What should I do?

[cendolinside123]

@Juanpe please add this configuration on .podspec file

s.ios.resource_bundles = {'SkeletonView' => ['SkeletonViewCore/Sources/Suporting Files/PrivacyInfo.xcprivacy']}

and make update for cocoapod

[macdrevx]

Apple announced that they'll start enforcing these new requirements on May 1. Would love to see a release with these changes soon to allow time to update, test, etc.

[ASWalnut]

Any updates?

[WGMB]

Hi, please create new release version with the latest changes and a Cocoapods release as well.

[caosuyang]

The PrivacyInfo.xcprivacy file was not found in the pod update library.

[caosuyang]

1. I found that the PrivacyInfo.xcprivacy file was only found in the main branch. I hope it can be updated to the tag branch in time later.
2. s.source_files = "SkeletonViewCore/Sources/**/*.{swift,h}" in the SkeletonView.podspec file, resulting in the pod install library not containing the PrivacyInfo.xcprivacy file. I think this is an issue