← Blog

Background Assets: plan the migration for iPhone and iPad apps

· Apple release notes from November 12, 2026

A business app installed on an iPhone or iPad may still need to download a catalogue, map or training module. Apple’s On-Demand Resources announcement gives teams a reason to check both build submission and the availability of those files on managed devices.

1. Identify the affected apps

In its November 12, 2026 release notes, Apple says that starting in early 2027, App Store Connect will reject builds containing On-Demand Resources from new apps and apps that have never used the feature. Apple recommends Background Assets. For an app that already uses On-Demand Resources, take that scope into account when scheduling its migration and next business release.

For each app distributed through App Store Connect, record its history with the feature, who owns the release and which workflows depend on downloaded files. If development is outsourced, ask the vendor to confirm the next build’s settings and provide a test version.

2. Prepare the packs and test availability

Update the Xcode project

Apple documents how to disable On-Demand Resources in the Xcode project and in targets that override that setting, remove the associated tags and replace calls to NSBundleResourceRequest. For Apple-hosted packs, plan to upload them to App Store Connect alongside the build and check their availability in TestFlight.

Test first use and an update

Install the app on a managed pilot device and measure how long it takes for priority content to become usable. Interrupt a download and check the message shown and whether the download resumes after reconnecting. If the workflow requires offline use, open the downloaded content without a network connection. For an app already in distribution, repeat these checks after updating from the production version.

3. Underside analysis for organisations in Belgium and France

A small business can ask its vendor to demonstrate a specific workflow, such as opening a field service record offline. A multisite IT team in Belgium and France can test the same build on the corporate network and on the connection staff use in the field. The MDM team verifies deployment to the pilot group. The business owner confirms that the correct content is available, in the expected language where several versions exist.

Background Assets documentation · Test asset packs in TestFlight

Testing business apps · Talk to Underside

LinkedIn · X · Facebook