Skip to content

Conversation

@haniewais
Copy link

Added privacy manifest for compliance.
Includes details for Stat system call usage to align with Apple's privacy requirement

…em call usage to align with Apple's privacy requirements.
@haniewais haniewais mentioned this pull request Mar 13, 2024
@EvanMasterson
Copy link

EvanMasterson commented Apr 24, 2024

Seeing the same issue with Apple warning against this for NSPrivacyAccessedAPICategoryFileTimestamp, can we get some movement on a library update including the Privacy Manifest please?
@Vkt0r @grantneufeld @haniewais or whoever else is allowed approve, merge and bump the library and create a new release?

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>NSPrivacyAccessedAPITypes</key>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will also need to include the other required keys, even with empty values

<key>NSPrivacyTracking</key>
<false/>
<key>NSPrivacyTrackingDomains</key>
<array/>
<key>NSPrivacyCollectedDataTypes</key>
<array/>

s.source = { :git => "https://github.com/httpswift/swifter.git", :tag => "1.5.0" }
s.source_files = 'Xcode/Sources/*.{swift}'
s.swift_version = '5.0'
s.resource_bundles = {'Swifter' => ['Xcode/Resources/PrivacyInfo.xcprivacy']}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add spaces after { and before } for better consistency? For example:

{ 'Swifter' => ['Xcode/Resources/PrivacyInfo.xcprivacy'] }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants