Repository navigation
|
How can a team catch On-Demand Resources still in 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 'NSBundleResourceRequest\|OnDemandResources\|on-demand-resource' --include='*.swift' --include='*.m' --include='*.plist' --include='*.entitlements' --include='*.pbxproj' .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 What the hit means. Apple deprecated On-Demand Resources starting in iOS 27, iPadOS 27, tvOS 27, and visionOS 27. Apps that rely on NSBundleResourceRequest tags will lose the download path in a future release and should migrate to Background Assets. The fix. Migrate tagged resources to the Background Assets framework before the iOS 27 family becomes the submission floor. 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-ODR-DEPRECATED-27with a coverage line and a proper exit code.What the hit means. Apple deprecated On-Demand Resources starting in iOS 27, iPadOS 27, tvOS 27, and visionOS 27. Apps that rely on NSBundleRe…