On Demand Resources "0 Asset Packs"

On Demand Resources 0 Asset Packs

Whatever the problem is, it seems to be resolved now. Asset packs seem to show the correct number of Asset packs in the iTunes Connect, and the apps downloaded through test flight now work properly. I guess they got aware of such a problem and fixed it, and we just happened to test our apps in this unlucky time.

Unable to find On-Demand Resources embedded in App bundle

The fact that you are sidestepping the use of the server as a source of the ODR download by embedding the on-demand resources changes nothing about how you access them. You still have to have an NSBundleResourceRequest and call beginAccessingResourcesWithCompletionHandler: and access the resources in the completion handler, exactly as you would do if you hadn't turned on Embed Asset Packs In Product Bundle.

So your code should be unchanged, without regard to the value of Embed Asset Packs In Product Bundle. If the same code works when Embed Asset Packs In Product Bundle is NO but not when it is YES, your code was wrong to start with.

Asset Catalog Compile Error with On-Demand Resources: has no output specification

My coworkers and I struggled with this error for over a day and were only able to fix it by wiping our existing local repos and installing a fresh clone from our remote repos with the code that contains the on-demand resources.

In our case, I was the one that created the on-demand resources functionality and did the tagging for the assets. I built and ran all of that code, and everything worked fine locally on my machine. I pushed those commits to our remote, and when my coworkers pulled they received the asset catalog compile error that you reported when they tried to build.

I compared my build logs with those of my coworkers and found that I had the --asset-pack-output-specifications flag along with a filename whereas they did not, even though all of our production code was the same. I never set that flag manually myself during development, it was automatically generated at some point in the process but I have no idea where -- I didn't even know it existed until this build failure occurred. After struggling for many hours we noticed that if my coworkers deleted their local projects entirely and basically started fresh by installing a new project and repo again from the remote, they suddenly were able to build. They had already tried to clean and nuke their derived data, but that didn't work. Only totally deleting the repos and the projects entirely did the trick. Not sure why, but something about wiping the project and all associated directories and building themselves totally fresh from their own local machines triggered something that enabled the --asset-pack-output-specifications flag.

How to host on demand resources from xcode during development

You can embed resources in the bundle for local testing and Ad-hoc distribution.

If you want to test ODR downloads you'll need to use Testflight.

---

Related Topics