As discussed here and here, the only apparent way to manage reusable images in a frame
.xcassets file, then use the images in storyboard / XIB of an app, to be manually create a reference to that directory file directly in the app's project. This puts the properties in the app's main package and avoids this error when trying to use them via interface builder:
Could not load the image "ImageName" referenced by a nib in
bundle of identifier "BundleName"
However, my question is: Has this led to duplication of assets during construction? Is iOS smart enough not to double the assets that are both: [1
If this leads to duplication, what other approach can be achieve the same result more effectively? The frame must be embedded in the app because it contains other reusable code, and the assets must be in the frame directory because they are also used in other apps.