B03
iOS privacy manifestValidated
The library ships a privacy manifest and uses no required-reason file APIs.
Validatedios
How to read this page
A scenario is one test case: prepare the environment, run the steps, then compare the expected result (written before the run) with the observed result (copied from the run, with screenshots).
- B03 · B
- Build or packaging check — does the package install and compile.
- Validated
- Run, and the result matched what was expected.
Why it matters
App Store review rejects undeclared required-reason API use.
Environment
- App
- Example app, simulator build
- Library
- 0.2.0
Setup
Prepare the environment.Then run the steps.
- 01Build the example app for iOS.
Steps
What to run.What to read.
- 01Look for DeviceIntegrityPrivacy.bundle/PrivacyInfo.xcprivacy in the app.
- 02grep the iOS sources for stat/lstat/fstat.
Expected result · written before the run
No single pass/fail status.No signals.
Manifest declares no tracking, no data collection, no required-reason APIs.
Observed result · copied from the run
No single pass/fail status.Observed 2026-09-30.
evidence
DeviceIntegrityPrivacy.bundle/PrivacyInfo.xcprivacy present in the built app; no stat/lstat/fstat calls.Checks this scenario covers
Every check this test case touches — including ones that aren't expected to fire here. The expected and observed results above say which ones should and did. Each links to how the check works.
None