“xcode github”

Also: try launching the camera companion app on the watch. This typically works to jump start the watch->phone data connection.But in all honesty I think getting Xcode to recognize your watch is only the first hurdle. I still haven't been able to debug on-device with my iPhone 5 and watch. It seems like data transfer is just too slow between the phone and the watch right now, it always times out or hangs.

Watch the What's New in Swift talk. Since `executeFetchRequest` is a throwing method (https://developer.apple.com/library/prerelease/ios/documentation/Cocoa/Reference/CoreDataFramework/Classes/NSManagedObjectContext_Class/index.html#//apple_ref/occ/instm/NSManagedObjectContext/executeFetchRequest:error:), you need to wrap it in a `do { ... } catch { ... }`. So I think it should look like this:do { ... let results = try managedContext.executeFetchRequest(request) as! [StockCode] } catch { fatalError(Fetching from the store failed) }This is based on my take away from the talk. I still haven't downloaded Xcode 7 :[

I have uploaded a code example for this issue / bug to github: under /snowkidind/evalCrash

Can I work on my iOS 7+ app using Xcode 7 to add features and prep it for iOS 9, but still submit it to the App Store once per week using Xcode 6?

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, though).&g

I have a similar issue: in one of my view controller's viewWillAppear, self.view.frame has a size of 320x568 when using Xcode 6/iOS 8, but only 320x480 when using Xcode 7 beta/iOS 9. In both cases I'm testing in the simulator for iPhone 6. Any ideas why this is happening?

Did you ever get the 'trust this computer' dialog on the watch? If not you'll need to un-pair and then re-pair the Watch with your iPhone. Then re-start Xcode and it can take about a minute or longer for the watch to showup the first time.

When I click Run on the [AppName] WatchKit App scheme, the status window says Running [AppName] WatchKit App on [Phone name]. It stays like that for about 45 seconds. Then it says Finished running [AppName] WatchKit App on [Phone name].Did the 'trust this computer' diaglog ever show on the watch? Unpairing and then re-pairing and restarting Xcode should have gotten you that prompt. The symptoms you are experiencing seem to indicate that this dialog was not presented after you upgraded.

Did the 'trust this computer' diaglog ever show on the watch? Unpairing and then re-pairing and restarting Xcode should bring it up. Once the computer is trusted you should be able to debug from Xcode.