pointfreeco/swift-composable-architecture

Adding a `.xcprivacy` manifest file

Closed this issue · 1 comments

DandyLyons commented

Description

Apple has announced, starting May 1, 2024 that:

Starting May 1, 2024, apps that don’t describe their use of required reason API in their privacy manifest file aren’t accepted by App Store Connect.

"Required reason API" include File timestamp APIs, System boot time APIs, Disk space APIs, Active keyboard APIs, and User defaults APIs (per the documentation here. In particular User defaults will be used by the .appStorage persistence strategy in the upcoming shared-state-beta.

For this reason, I would like to submit a PR to add a .xcprivacy file, and I'm opening this Issue, so that I can ask further questions while I audit the privacy practices of TCA. (Hopefully there isn't much to declare other than User defaults.)

Some Context

Note: This isn't a "bug" per se, just an issue that severely affects the usability of TCA for the community. (The bug label was automatically applied by the Issues form.)

Checklist

  • I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
  • If possible, I've reproduced the issue using the main branch of this package.
  • This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior

For the TCA community, it would be a benefit to all if we had a .xcprivacy file.

Actual behavior

There currently isn't an .xcprivacy file.

Steps to reproduce

No response

The Composable Architecture version information

any version

Destination operating system

any OS

Xcode version information

any version

Swift Compiler version information

No response

DandyLyons commented

Since this is more of a infrastructural concern and not a bug, we'll close this Issue and continue discussion here.