xcasset

When validating or submitting my app with xcode 6, I get the error: ERROR ITMS-9000: "Invalid Image Path - No image found at the path referenced under key 'CFBundleIcons': 'AppIcon120x120'" I've checked my plist file, and there is no entry for CFBundleIcons. I am using an asset catalog, which I can see is configured correctly under the General target settings (it also builds properly with the icons on a device). I've tried removing and re-adding the catalogues, as well. My best guess is that there is some kind of bug in xcode when using multiple asset catalogs across multiple targets. Any

In a nutshell : How can I load images from a compiled Assets.car within an NSBundle ? Full Version: I'm in the process of converting a suite of apps to use CocoaPods . Each app relies on a shared pod called Core . Core includes code files, xib files, and several xcasset files. Here's the relevant line from the Podspec for Core that creates the resource bundle: s.resource_bundles = {'CoreResources' => ['Core/Resources/*']} The Podspec passes pod spec lint , and main project that relies on it correctly builds. However, none of the images from any xcasset files within Core are showing. I am

As discussed here & here , the only apparent way to host re-usable images in a Framework's .xcassets file, then use those images in the storyboard / XIB of an app, is to manually create a reference to that catalog file directly within the app's project. This puts the assets within the app's main bundle, and avoids this error when trying to use them via Interface Builder: Could not load the "ImageName" image referenced from a nib in the bundle with identifier "BundleName" My question, though, is: Does this lead to duplication of the assets at build-time? Is iOS smart enough not to double-up

When I build my application on El Capitan using Xcode6.4 (Xcode7 is no option right now), all images/icons (except the AppIcon) does not show, or looks garbled. Looking at the output from the asset compiler it looks fine, but there are two outputs I suspect could be related, but I am far from certain: 2015-10-02 12:26:53.569 ibtoold[28899:273288] NSFileCoordinator is doing nothing. 2015-10-02 12:26:54.906 ibtoold[28899:276436] CoreUI(DEBUG): CSIGenerator using 'LZFSE' Compression coreui version (362.000000) Could it be that the LZFSE compression messes up so that Yosemite is unable to

We switched our XCode project over to use the Asset Catalog during a redesign. We needed several large background images, which we included in the asset catalog. The images were originally JPEGs that we renamed to PNGs to save space. The size of the images on disk is 19.1MB, but when we archive the app the Assets.car file that is generated is 6 times larger than that. I have tried using PNGs and compressing them, but the size is still huge. I'm not sure what else I can do. It turns out that any image no matter what the original format is converted into a png during the archiving process. I

I'm not using storyboards here, for reasons that would be a distraction to get into. I'm instead trying to add four launch images to an asset catalog: My app doesn't support iPads or 3.5-inch iPhones, so these should be sufficient. Is that fine or do I need landscape as well? Here are the properties of each of the images: Here's the same information in textual form: filename: LaunchImage.launchimage children: filename: 5.5.png idiom: iphone subtype: 736h scale: 3x orientation: portrait extent: full-screen minimum-system-version: 8.0 image: height: 2208 width: 1242 filename: 4.7.png idiom:

I have a big amount of images in a Images.xcassets and I need to load them all in a UITableView. But I don't wat to write each name for the [UIImage imageNamed:@"imageName"] . What i'm looking for is something like: NSArray *images = [MagicClass loadAllImagesIn:@"images.xcassets"]; Do you know if this is even possible? If not maybe i'll create a .bundle... Thanks!! Images.xcassets copies all the images in bundle, and it mixes up with other images, better follow the instructions in image below By adding the folder with the option Create folder reference will actually create a folder in main

according to the apple documentation it is recommended to use xcassets for iOS7 applications and reference those images over imageNamed. But as far as I'm aware, there were always problems with imageNamed and memory. So I made a short test application - referencing images out of the xcassets catalogue with imageNamed and started the profiler ... the result was as expected. Once allocated memory wasn't released again, even after I removed the ImageView from superview and set it to nil. I'm currently working on an iPad application with many large images and this strange imageView behavior leads