Repository navigation
|
How can a team catch Private API or deprecated framework use automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'UIWebView\|performSelector\|valueForKey' --include='*.swift' --include='*.m' . # review any reflection or deprecated framework useRead the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. References to known private API selectors or deprecated frameworks found in the binary or code. The fix. Use only documented public APIs and current frameworks. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
APPLE-2.5.1-PRIVATE-APIwith a coverage line and a proper exit code.What the hit means. References to known private API selectors or deprecated frameworks found in the binary or code.
The fix. Use only documented public APIs and current frameworks.
R…