“xcode github”

Which version Xcode are you using?

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)

Playgrounds are slow, and in my opinion, basically unusable in the current Xcode 7 beta. 😢

Check the console output. If this is an Xcode 6 playground, show the assitant editor to see the console output. There may be an error there.Also, please post your playground code - it's very difficult to guess what might be wrong without seeing it.

Did you update the project for Xcode 7? If so, try editing the source of the playground (see the xml metadata) to bring it up to date.

Anything from the Xcode 7 b releases notes shed light?Playgrounds Opening a Playground that was previously displaying the Version Editor may present an alert stating, “The file “MyPlayground.playground” couldn’t be opened because you don’t have permission to viewit.” (20623808). Workaround: Dismiss the alert dialog and show the Standard Editor (Command-Return).Playgrounds sometimes show a window with no editor if they are opened as part of Xcode launching (20694143) Workaround: Close and re-open the playground.Executing an iOS Playground for the first time may take longer than subsequent executions. (21163503)For old-style playgrounds, the menu item Edit->Convert->To Latest Swift Syntax... is greyed out. (20902099) Workaround: Upgrade the playground before attempting to convert to Swift 2.0 by choosing Editor- >Upgrade Playground...Playground pages may recompile each time they are navigated to, even when there are no changes. (21177662)Playgrounds live views may not show images when

There is info in the documentation for XCode you can get to by going to the Help menu and choosing Documentation and API ReferenceIn the pane on the left, choose XCode 7 Documentation > XCode > IDE's > Guides > AutoLayout HelpOr, the online version:https://developer.apple.com/library/prerelease/ios/recipes/xcode_help-IB_auto_layout/chapters/UnderstandingAutolayout.htmlSpecifically:https://developer.apple.com/library/prerelease/ios/recipes/xcode_help-IB_auto_layout/chapters/pin-constraints.html#//apple_ref/doc/uid/TP40014226-CH28-SW1

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 GameViewController: UIView

Just curious, are you using Swift 2 with SceneKit by any chance?If so, please see these discussions:Abort trap: 6 error in Swift 2 with Xcode 7 beta-1Abort trap: 6