Hi, I'm trying to setup background assets hosted on Apple servers.
I currently have installed Xcode 16.4 and Xcode beta 4. I have also freshly installed the command line tools for both.
When I run
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
xcrun ba-package template
I get
xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find ba-package 2> /dev/null' failed with exit code 17664: (null) (errno=No such file or directory)
xcrun: error: unable to find utility "ba-package", not a developer tool or in PATH
If I try to use Xcode beta 4:
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer
xcrun ba-package template
I get:
dyld[92926]: Library not loaded: /System/Library/PrivateFrameworks/ManagedBackgroundAssetsHelper.framework/Versions/A/ManagedBackgroundAssetsHelper
Referenced from: <7F150064-45BF-31D7-BAFD-32911BB9F569> /Applications/Xcode-beta.app/Contents/Developer/usr/bin/ba-package
Reason: tried: '/System/Library/PrivateFrameworks/ManagedBackgroundAssetsHelper.framework/Versions/A/ManagedBackgroundAssetsHelper' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/PrivateFrameworks/ManagedBackgroundAssetsHelper.framework/Versions/A/ManagedBackgroundAssetsHelper' (no such file), '/System/Library/PrivateFrameworks/ManagedBackgroundAssetsHelper.framework/Versions/A/ManagedBackgroundAssetsHelper' (no such file, not in dyld cache)
[1] 92926 abort xcrun ba-package template
Any tip?
Hello! The packaging tool (ba-package) is included with Xcode 26, so it’s not expected to be available when your selected Xcode installation is an older version, such as Xcode 16.4.
Regarding the dyld error, are you running macOS 26 Tahoe? The packaging tool might not work properly if you have an older version of macOS installed, even with the latest Xcode 26 beta. This is because the packaging tool depends on a system framework that’s new in macOS 26 Tahoe. If you are indeed running macOS 26 Tahoe or can still reproduce the problem after updating to macOS 26 Tahoe, then please file a feedback report so that we can investigate further and reply to this thread with the feedback ID. If you’re unfamiliar with the process, then you can learn more about filing feedback with Feedback Assistant. Thanks!
