The system effectively merges all of your asset packs into a single directory hierarchy. You can think of it as your app’s single, shared asset-pack namespace. The system expects that every individual file have a relative path from the root of that shared namespace that’s unique across all of your app’s asset packs (though not necessarily across multiple apps). An asset pack’s ID is not part of the unique path, but every other path component is. In your case, Foo/10/239/414.png and Bar/10/239/414.png are distinct paths that shouldn’t collide.
This is also what I suspected from observation. That also actually works out great for something like map tiles, unless there are duplicate files.
I would much prefer to just list the images as z/x/y.png, but duplicates appear to resolve in an error.
I suspect that you’re testing your app on OS 26, not OS 26.1. There’s a known issue with AssetPackManager.url(for:) in OS 26 that we fixed in OS 26.1 beta
I was testing with 26.0.1. I'll upgrade and give it a go!
Thank you for the quick reply!
