“Xcode”

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.

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.

Ok. Thanks KMT and spielplatz. Sounds like I can develop full on using Xcode 7 and then when I get a feature ready for release (e.g. 1 week from today) I can simply open the project using the latest version of Xcode 6, do a regular Clean followed by an option Clean Build Folder..., then use Product > Archive to submit my iOS 7-9 app to the App Store even before iOS 9 has been released to the public. This sounds great. I'll try this workflow this week. Thanks.

FInally figured a workaround of sorts. Xcode seems to be picking up on another SVN repository that I have that is completely unrelated to my xcode projects (it's in a completely unrelated directory). It is included in the list of repositories when I look at Preferences->Accounts. Nothing I could do would convince Xcode to ignore the repository (tried deleting the reposity from the account list, but it would just come back next time I restarted Xcode). Tried disabling the repo. No effect. Still rows of ?s on my source code.But then I tried removing the other repository (as in: removing the directory containing it - not via Xcode). I then fired up Xcode. This time it popped up a dialog at the beginning, saying:This workspace includes files from other working copies that are not checked out. Choose Check Out to select additional working copies. Choose Ignore to skip these working copies.If I then say Ignore - voila.. the problem is fixed!When I get a chanc

> Xcode 7.0 beta does not support iOS 8.4 and earlier simulator runtimes. (20699475)http://adcdownload.apple.com/WWDC_2015/Xcode_7_beta/Xcode_7_beta_Release_Notes.pdf

Seems odd - even with deployment set to 8.3 it should list various simulators. What simulators do you have installed in Preferences?Try a new project using your choice of simulator and see what it does.Also, did you by any change rename Xcode or install it someplace atypical?◅▻

My mistake - thought I was running Xcode 7, but it was Xcode 6.3.2.

That tech note describes using gcov, and is not part of Xcode 7's code coverage support. For Xcode 7, there's a Coverage.profdata file that's produced down inside the CodeCoverage directory of the Intermediates folder of your project's build directory. That file can be read by the llvm-cov command line tool.

Connect your iPhone to your computer, then open the devices window in Xcode (shift + CMD + 2). When you select your iPhone, the UDID and other information about a paired Apple Watch will appear below the regular device information.