Hi everyone,
I’m looking for advice on a repeated App Store rejection under Guideline 2.5.1.
Background:
We initially explored using Family Controls for a planned feature.
That feature has now been fully removed from the app.
We no longer provide any Screen Time related functionality.
What we already cleaned up:
Removed all FamilyControls / ManagedSettings / DeviceActivity code usage.
Removed commented-out code and all related references from the project.
Removed related capabilities and entitlements from targets.
Removed related frameworks/dependencies.
Performed a clean rebuild and submitted a new archive.
However, App Review still says the app includes ScreenTime API in an unapproved manner and suggests removing those APIs.
Questions:
What are the most common hidden places where Screen Time / Family Controls traces remain?
Has anyone seen this triggered by transitive dependencies or stale build artifacts?
What evidence/details should I provide in App Review Notes to help the reviewer verify cleanup?
Is there a recommended way to ask App Review to share the specific symbol/framework/target they detected?
Any practical checklist or experience would be greatly appreciated. Thank you.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
App Review
Xcode
Family Controls
Screen Time
2
0
190