“build disappears”

Same here.I already asked in the WWDC Lab, what happens with on-demand ressources, when a new version is submitted, only on demand ressources have been changed? Will I see an update, that does not download or install anything except the info.plist?But xloser to your topic:My Mac s my digital hub and I never download App Updates via WiFi, only if I do not have any other option and the update is important enough (like during the WWDC). I have 3 devices linked there, my iPhone, my newer iPad (V3) and an old original one (ignoring for now).When I download the thinned updates in iTunes, what will happen?Do I get 2 different build downloaded, one for iPhone one for iPad?Do I get a app download, that is thinned to only the 2 devices - in that case not that much at all?What happens, when I download a thinned App on my iPhone, sync it via iTunes and want to install it on my iPad? The thinned iPhone version won't work on the iPad. Do I need a download - will it be another file?Last not least, imagine I get a t

Have you tried just adding the declaration of the methods to your Obj-C bridging header?Just as a quick test, I added@interface NSString (Compatibility) - (BOOL)localizedStandardContainsString:(NSString *)str; @endto the bridging header for an app with a deployment target of 10.10, and called it from Swift.The app built without error. Then I commented it out, and the build failed with a error of only available in 10.11 or newer.So it seems to work, at least for methods.

The option to use Display Audio on an older Cinema Display disappeared. The display is now listed as an unknown apple USB device ! But that cannot be selected for long, before it switches to another output. In the meantime, lots of distortion, clicks, pops. reported as well.

HI, David,I am trying to navigate the same waters as you. The properties and methods declared in the new header are definitely for 10_11 and up. However, I did attempt to run the CocoaSlideCollection sample code in Yosemite after building it with 10_10 as deployment target. It ran, but it failed to select JPEGs when browsing.My expectation is that we will have to run different code for NSCollectionView and maybe load different NIBs, depending on the outcome of a test for OS X version. I have a question in to Apple about that.Best regards,Tom McVay

Assembly source files should work in the sense that you can build and run your project. I did not mean to imply that we somehow de-compile the assembly source into bitcode.Searching for a bitcode section is not a reliable way to detect if your files contain embedded bitcode. If you want to do that, search for the __LLVM segment. You should be aware that a normal build with the -fembed-bitcode-marker option will produce minimal size embedded bitcode sections without any real content. This is done as a way of testing the bitcode-related aspects of your build without slowing down the build process. The actual bitcode content is included when you do an Archive build.

An addition: When I tilt it directly after the build to landscape and back to portrait without tapping something on it it also crashes with the formation issue.

You can reduild the mailbox and they will show up, but for some reason doing anything with Exchange in mail causes the calendar to disappear.

Great info @bwilson. Thank you.> If you want to do that, search for the __LLVM segmentAhh, you're correct. When I searched for the __LLVM segment, I do see that the assembly's .o file contains an __LLVM segment.> Assembly source files should work in the sense that you can build and run your project. I did not mean to imply that we somehow de-compile the assembly source into bitcode.When it becomes a requirement to submit apps in bitcode format, how will this impact architecture specific code (ie. assembly, or anything that is ifdef'd for that matter). It makes sense that assembly isn't converted to bitcode, but doesn't everything need to be in bitcode in order for an archive to be fully encoded in bitcode? I have an app that's hitting a compile warning when archiving complaining that a specific 3rd party library doesn't contain bitcode so the app cannot be archived with bitcode. That 3rd party library won't emit bitcode ostensibly because it contains assembly (I could be wong about the cause, t

You have to build and submit it with a non pre-release xcode version. Otherwise you will receive a validation error like The app may have been built or signed with non-compliant or pre-release tools.