Skip to content

fix(package_info_plus): declare file timestamp API in privacy manifests - #4027

Open
jihanurrahman33 wants to merge 1 commit into
fluttercommunity:mainfrom
jihanurrahman33:fix/package-info-plus-privacy-manifest-file-timestamp
Open

jihanurrahman33 wants to merge 1 commit into
fluttercommunity:mainfrom
jihanurrahman33:fix/package-info-plus-privacy-manifest-file-timestamp

Conversation

@jihanurrahman33

Copy link
Copy Markdown
Contributor

Description

The iOS and macOS implementations read two File Timestamp APIs to report install and update times:

  • NSFileCreationDate on the Documents directory (install time)
  • fileModificationDate on the bundle path (update time)

These need a required-reason declaration, but the iOS PrivacyInfo.xcprivacy had an empty NSPrivacyAccessedAPITypes and the macOS one had no such key. This PR declares NSPrivacyAccessedAPICategoryFileTimestamp with reason C617.1 in both manifests. Packaging (Package.swift and the podspecs) already bundles the manifests, so only their contents change.

Open question for reviewers: C617.1 clearly covers the Documents-directory call, but the bundle fileModificationDate call reads outside the app's data container. I'm happy to switch to or add a different reason code if you prefer.

Related Issues

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I titled the PR using Conventional Commits.
  • I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
  • All existing and new tests are passing. (No Dart code changed; I have not run the test suite.)
  • The analyzer (flutter analyze) does not report any problems on my PR. (No Dart code changed; not run.)

Testing note: I confirmed both manifests parse as valid plists and contain the intended entry. I have not yet built the example app or checked Xcode's privacy report with CocoaPods or SwiftPM, so a maintainer check on that would be appreciated.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
  • No, this is not a breaking change.

🤖 Generated with Claude Code

The iOS and macOS plugins read NSFileCreationDate (Documents directory) and
fileModificationDate (bundle path) to report install and update times. Both
are File Timestamp APIs that need a required-reason declaration, but the iOS
manifest had an empty NSPrivacyAccessedAPITypes and the macOS manifest had no
such key.

Declare NSPrivacyAccessedAPICategoryFileTimestamp with reason C617.1 in both.

Fixes fluttercommunity#3627

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.

[Request]: The missing PrivacyManifest support

1 participant