Thanks for the effort, Quinn! The code signing info from launchctl procinfo looks exactly like yours, ending with entitlements validated. The bundle flags line is as follows: bundle flags: is-containerized (0000004000000000) Does it need the is-Beta-App flag? The dump only shows that for apps installed via TestFlight.

It appears to be correctly signed. "Automatically manage signing" is checked, my standard team is set. With those settings, as soon as I assign an app group in Xcode 26.1, it changes to an Xcode managed provisioning profile and my valid Apple Development certificate and does not let me change them. I also checked the build with codesign -dv --verbose=4 and in ~/Library/Developer/Xcode/UserData/Provisioning Profiles to verify and that the profiles update, e.g., when I change the Info.plist. I also tried setting up a fresh sample project from the standard multiplatform SwiftUI app template in Xcode and did not change anything in Signing & Capabilities except setting the app group for the app and download extension. Same minimal app just calling AssetPackManager.shared.assetPack(withID:), same result: on iOS it works, on macOS the URL override is not permitted.

It turns out the duplicate log entry for the BackgroundAssetsSample app was from a copy of the project I created during testing. I removed that but I still get a (single) "Development overrides aren’t permitted" log entry now. When run on iOS, I do get com.apple.backgroundassets The application with the identifier “com.imaier.BackgroundAssetsSample” is configured to use Apple hosting. com.apple.backgroundassets A development-override URL, “https://myhostname.fritz.box”, is set. com.apple.backgroundassets Using the development-override URL “https://myhostname.fritz.box/manifest?platform=iOS” for the application with the identifier “com.imaier.BackgroundAssetsSample”…

In the meantime, I have looked into the log a bit more. I have found the following entries from the backgroundassets.user process: com.apple.backgroundassets The application with the identifier “com.imaier.BackgroundAssetsSample” is configured to use Apple hosting. com.apple.backgroundassets A development-override URL, “https://myhostname.fritz.box”, is set. com.apple.backgroundassets Development overrides aren’t permitted for the application with the identifier “<devteam>.com.imaier.BackgroundAssetsSample”. com.apple.launchservices _LSBundleCopyOrCheckNode: cached node not found, _LSBundleCreateNode for bundleID 3464 returned -43 com.apple.backgroundassets The application with the identifier “com.imaier.BackgroundAssetsSample” is configured to use Apple hosting. com.apple.backgroundassets A development-override URL, “https://myhostname.fritz.box”, is set. com.apple.backgroundassets Development overrides aren’t permitted for the application with the identifier “<devteam>.com.imaier.BackgroundAssetsSample”. com.apple.launchservices _LSBundleCopyOrCheckNode: cached node not found, _LSBundleCreateNode for bundleID 2828 returned -43 com.apple.launchservices _LSBundleCopyOrCheckNode: cached node not found, _LSBundleCreateNode for bundleID 4052 returned -43 where <devteam> is my alphanumerical dev team ID. What could be the reason that the overrides aren’t permitted?

It does seem buggy. In case you haven't found out already, for the grayed out failure options, it appears that the file may be missing entries in the _storeKitErrors array and the editor won't create them. Edit the config file JSON (Open As -> Source Code) and replace the empty _storeKitErrors array with the following. Seems to fix it for me. "_storeKitErrors" : [ { "current" : null, "enabled" : false, "name" : "Load Products" }, { "current" : null, "enabled" : false, "name" : "Purchase" }, { "current" : null, "enabled" : false, "name" : "Verification" }, { "current" : null, "enabled" : false, "name" : "App Store Sync" }, { "current" : null, "enabled" : false, "name" : "Subscription Status" }, { "current" : null, "enabled" : false, "name" : "App Transaction" }, { "current" : null, "enabled" : false, "name" : "Manage Subscriptions Sheet" }, { "current" : null, "enabled" : false, "name" : "Refund Request Sheet" }, { "current" : null, "enabled" : false, "name" : "Offer Code Redeem Sheet" } ]

Thanks for your reply, here it is when set to a local IP address: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>MBALastWeeklyCollectionDate</key> <date>2025-11-12T15:18:41Z</date> <key>MBAURLOverride</key> <data> YnBsaXN0MDDUAQIDBAUGBwpYJHZlcnNpb25ZJGFyY2hpdmVyVCR0b3BYJG9iamVjdHMS AAGGoF8QD05TS2V5ZWRBcmNoaXZlctEICVRyb290gAGkCwwTFFUkbnVsbNMNDg8QERJX TlMuYmFzZVYkY2xhc3NbTlMucmVsYXRpdmWAAIADgAJfEBZodHRwczovLzE5Mi4xNjgu MTc4Ljg30hUWFxhaJGNsYXNzbmFtZVgkY2xhc3Nlc1VOU1VSTKIXGVhOU09iamVjdAgR GiQpMjdJTFFTWF5lbXSAgoSGn6SvuL7BAAAAAAAAAQEAAAAAAAAAGgAAAAAAAAAAAAAA AAAAAMo= </data> </dict> </plist> What is the meaning of the MBALastWeeklyCollectionDate field? BTW, what I now get in the log on the Mac (not with the iOS app) is Checking for updates failed: A HTTP client error occurred: “Forbidden”. Process: BackgroundAssetsSample | Library: BackgroundAssets | Subsystem: com.apple.backgroundassets.managed | Category: AssetPackManager about a second after the "asset not found" error. I haven't noticed it before. For the sake of completeness, AssetPackManager.shared.assetPack(withID: assetPackID) is the first BackgroundAssets method I call and I don't call any other method after it has thrown.