“translate scheme”

I'm experiencing the same hang when building an project that has an app target with one embedded cocoa touch framework, which is also built as a dependency. I'm running the beta 2 of Xcode 7 and Server 5.1 with Xcode server on the same MBP box which is running 10.10.4 release. The raw log file shows what happens after the hang:CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Dist

Mac: OSX 10.11, both wired and wifiiPhone: iOS 9.0 (I think beta 2 - downloaded/installed 7/7/2015)Followed the directions for setting this up. All went flawlessly. The iPhone is connected wifi to the created shared wifi connection, hosted on the iMac. I've confirmed there is an IPv6 connection in existence using a 3rd party app (HE Network Tools). The iMac is still able to open websites, ping, etc. using IPv4.BUT the iPhone has no network connectivity. It's like the translation in OSX isn't happening from IPv6 to IPv4.How do I troubleshoot this?Thanks.

The following is probably the worst way possible and has nothing to do with Swift. (Caveat programmeur.) Use Core Text with whatever line break scheme for fragments (words, characters, etc) and then base your count on the internal rendering.

I've tried that, but that doesn't seem to work. Here's an extremely bare bones project I made and submitted to Apple in a bug report: https://www.dropbox.com/s/ayltpprjck37ins/HandleWatchkitExtensionError%202.zip?dl=0You can see the first time you press the button in the Watch app, you get the error below. Susequent calls will succeed until you open and kill the app via Multitasking.(Warn ) WatchKit: <SPCompanionAppServer.m __91-[SPCompanionAppServer launchCompanionAppForGizmoAppWithIdentifier:withUserInfoData:reply:]_block_invoke_2:1450> Got BSActionErrorCodeResponseNotPossible for com.alarm.Testing123.watchkitapp. This will translate to WatchKitApplicationDelegateWatchKitRequestReplyNotCalledError error: Error Domain=com.apple.watchkit.errors Code=2 The UIApplicationDelegate in the iPhone App never called reply() in -[UIApplicationDelegate application:handleWatchKitExtensionRequest:reply:] UserInfo=0x60800007d800 {NSLocalizedDescription=The UIApplicationDelegate in the iPhone App never called

I'm experiencing a similar hang when building in Xcode server. For me it hangs in step 4 of 9 Signing product. I'm running the beta 2 of Xcode 7 and Server 5.1 with Xcode server on the same MBP box which is running 10.10.4 release. The raw log file shows a similar problem to what you are reporting after the hang:CodeSign /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/DerivedData/Build/Products/Debug-iphoneos/SpotfireFramework.framework cd /Library/Developer/XcodeServer/Integrations/Caches/56b1bc2eb30515c3f99753f43121a783/Source/Spotfire/SpotfireFramework export CODESIGN_ALLOCATE=/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate export PATH=/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/Applications/Xcode-beta.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbinSigning Identity: iPhone Distribution: TIBCO

It's not a suggestion. You are definitely allowed to run your own apps on your own devices now without a paid membership. I'm not an iOS developer, so I don't know precise details, but I think if you're signed in with the same AppleID on both Mac and iOS and connect the iOS device to your Mac, you should be able to select your iOS device as a run destination from the Scheme pop-up just to the right of the run/stop buttons in the toolbar.

The process that seems to work best for me is:1. Delete the previous version of your app from the phone.2. After it removes the app from the watch, power down both devices.3. Quit Xcode completely.4. Restart both devices.5. After they are up and running, start Xcode.6. Wait for the watch to show up as paired. (You can go into the watch app and rearrange icons to speed this up).7. Run the watch app scheme. Wait.8. If step 7 fails, repeat step 7 a few more times.This has been the most reliable way I've been able to get an app to run on the watch (which is pathetic and a pain in the butt).I don't understand why other developers aren't screaming about this. Is everyone using the simulator instead?

I suggest you boot into Internet Recovery Mode, which should be available even if normal recovery mode isn't:Boot to the Internet Recovery HD:Restart the computer and immediatly hold down the Cmd+Alt+R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.Partition and Format the hard drive:Select Disk Utility from the main menu and click on the Continue button.After DU loads select your newly installed hard drive. Click on the Partition tab in the DU main window.If your internal drive is big enough for two OS X partitions (which is desirable so that you can have a stable 10.10.4 OS and a 10.11 side-by-side) then set the number of partitions from the drop down menu to 2.Click on the Options button, set the partition scheme to GUID then click on the OK button.Set the format type to Mac OS Extended (Journaled). Click on the Partition button and wait until the process has completed.Quit DU and return to the main menu.Reinstall OS X: Select Reinst