chadtmiller.com/knotless
git that lives in your Atmosphere account
The iOS app is ready for TestFlight
MergedThis adds the encryption-exemption key, a privacy manifest (no tracking, no data collected, UserDefaults reason CA92.1), an ExportOptions.plist, and TestFlight steps in the README. The plists and the project.yml key look right. I found one problem: the README commands have doubled backslashes, so they won't run if copied. I didn't check whether the app uses other required-reason APIs, such as file timestamps or disk space, that the manifest would also need to declare.
ios/README.mdline 29Outdated
Raise `CURRENT_PROJECT_VERSION` in `project.yml` for each upload, then: | |
| |
cd ios && xcodegen generate | |
xcodebuild archive -project Knotless.xcodeproj -scheme Knotless -configuration Release \\ |
The line continuation is written \\, and inside an indented code block it shows literally. Pasted into a shell, the first backslash escapes the second and the newline ends the command, so the archive runs without its -destination and later flags. Use a single \ here and on line 31.
The README commands now use single backslashes, so they can be copied and run. That was the one thing I asked for, and it's done. The ITSAppUsesNonExemptEncryption key in project.yml, the privacy manifest and ExportOptions.plist all look right. I still haven't checked whether the app uses other required-reason APIs, such as file timestamps or disk space, that the manifest would also need to declare. The pull body says App Store Connect's privacy answers will have to match the manifest, so that is worth a look before the first upload.
8 passed, 2 skipped
What changes
Ready for TestFlight. The app answers Apple's encryption question in its Info.plist (
ITSAppUsesNonExemptEncryptionfalse, as it uses only the system's HTTPS), so a build doesn't ask it. A privacy manifest declares no tracking and no data collected, andUserDefaultsfor the app's own settings (favorites and recent searches).ExportOptions.plistand the README say how to archive and export a build.Why
The owner is setting up an internal TestFlight.
How it was checked
A Release archive and an App Store Connect export here succeeded. The app's bundle holds the manifest, and its Info.plist the key. Nothing has been uploaded.
Shortcomings
Signing in on such a build needs
webcredentialson Apple's CDN, which it doesn't have yet, though knotless.dev serves it. The manifest says no data is collected, which App Store Connect's own privacy answers will have to match.🤖 Generated with Claude Code