Background Assets: how to add BAManifestURL | backgroundassets-debug tool doesn't do anything

Question

Created Sep ’22

Replies 2

Boosts 0

Views 1k

Participants 4

I've added a background downloads extension to my app and added device console logging to every method in the placeholder code created by XCode, then installed the app to the phone.

When I run the following command:

xcrun backgroundassets-debug --app-bundle-id com.myCompany.myApp --device-id 00008110-001E0DDA0AB8801E --simulate --app-update

and watch the console log - there's none of my logging from within the extension.

In the OS log I can see this:

error 11:24:41.550702-0700 backgroundassets.user Event (1) dropped for client () failed because client Info dictionary is missing its 'BAManifestURL' key.

The template generated code says this: "The manifest that is downloaded is determined by BAManifestURL defined in the application's Info.plist"

So I tried adding a key of BAManifestURL with a url hoping to initially just get the extension launching. But I still get the error saying the info dictionary is missing the BAManifestURL key.

So exactly how should the BAManifestURL key value pair be added to the info.plist?

Boost

Answer 1

mungbeans OP

Sep ’22

Forgot to mention the WWDC22 session mentions a bunch of stuff to go into info.plist, but it doesn't mention BAManifestURL. In general the WWDC materials seem out of date and no use anymore. Is there some accurate up-to-date documentation?

0

Answer 2

Systems Engineer OP

Apple

Oct ’22

The addition of BAManifestURL was added in response to feedback we received from developers.

The BAManifestURL should be placed in the App's Info.plist at the top level, not inside the extension. You can easily cycle through these required keys by instantiating BADownloadManager in your app. This will cause the framework to crash your app with error messages until your Info.plist is in compliance.

All required keys for Background Assets go into the App's Info.plist, none of them go into the extension. (The extension does have some required keys, but the Xcode template creates them for you.)

Please let us know if you have any other questions.

1