build disappears

From the Xcode 7 Beta release notes (bold is mine)Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store.Some compiler and linker options are not supported when bitcode is enabled (e.g., -mglobal-merge for clang and -sectalign for linker). Some linker options will result in warnings (e.g., - weak_framework and -weak_libraries). Bitcode builds for iOS also require a minimum deployment target of 6.0. (18447465)

Yes, I have the Enable Bitcode option switched off. I can build and run my app in the simulators, but I cannot connect hardware that's running less than iOS 6.0.I'm wondering whether running code (through the debugger) on hardware that has less than iOS 6.0 has been dropped, or whether it's only because it's a Beta.Regards,David

I get this 95% of the time. To work around the bug, remove your iOS app from the Simulator and then build/run again.

Hmm. According to the WWDC15 presentation on UIDocument, building a document thumbnail using a UIView is a no no. So I have to create some facsimile of my document from scratch using other means. This is non-trivial.

Set a breakpoint and inspect the value of your backgroundImage variable. If it contains a valid image, then you will have to look at whatever that KLPAAlert class is. It's not an Apple framework class so you probably won't get any support here.If the image is *not* loaded correctly, then you'll have to look at the build settings and make sure the filename matches exactly (including case), and that it's being copied to the app target in the Copy Bundle Resources build phase. (Or if it's in an asset catalog, make sure the name matches - you might not want that .png suffix.)

I'm continuing to test this and have found something interesting. At least in my case, the problem appears to have something to do with SceneKit's SCNVector3 type. Here's what I did.1. Create a brand-new project in Xcode 7 beta-1. Type is Game, Language is Swift, Game Technology is SceneKit.2. Build and run with default settings. Project builds and runs fine in simulator (you will see the default rotating 3D spaceship model).3. Add a single SCNVector3 property to the gamecontroller in GameViewController.swift, like this:class GameViewController: UIViewController { var p = SCNVector3ZeroLo and behold, guess who pops up? Our friend Abort trap: 6. Project will no longer compile.4. Change the constant to an empty initializer.class GameViewController: UIViewController { var p = SCNVector3()Same problem, Abort trap: 65. Remove property, restoring to the clean project state. Abort trap: 6 is gone, project again compiles and runs.6. Try adding SCNVector4 instead of SCNVector3.class GameViewControlle

iOS 9 battery usage by my measurements is reduced 62%. In addition overall performance is about 30% slower right now. I assume it's the beta build. iOS 8 was that way in the first couple of betas too.

I filed a bug report based on my own situation. Hopefully more people will submit bug reports and Apple will coalesce them. Here's the info:Bug ID: 21376523Title: Adding property of type SCNVector3 yields Abort trap: 6 errorClassification: Serious BugReproducibility: AlwaysDescription:When using Swift 2 with Xcode 7 beta-1 (7A120f), with SceneKit, using SCNVector3 produces Abort trap: 6 compile error. This happens whether a project is migrated from (Swift 1.2 + Xcode 6.3) to (Swift 2 + Xcode 7.0), or with a fresh Swift 2 + Xcode 7.0 project. Error text is below:------------------[COMMAND LINE COMPILER OPTIONS OMITTED BECAUSE OF 3,000 WORD BUG REPORT LIMIT]Assertion failed: ((IGF.IGM.DataLayout.getTypeSizeInBits(coercionTy) == IGF.IGM.DataLayout.getTypeSizeInBits(paramTI.StorageType)) && Coerced types should not differ in size!), function emitDirectExternalParameter, file /Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-700.0.38.1/src/swift/lib/IRGen/IRGenSIL.cpp, line 908.0 swift 0x000000010c

I don't know if the previous response answered your question. Check your project build settings under Apple LLVM 7.0 - Warning Policies that you do not have Treat Warnings as Errors enabled.

I'm getting a similar thing when setting the target to 7.1.A bunch of the bitcode warnings disappeared by doing what @beagle said but I'm still getting the exception on the swift-stdlib-tool