“translate scheme”

@zacware,I am using the following steps to debug the watch and iphone at the same time.1) Create a scheme with both watch and phone combination.2) Build successfully with command B.2) Setup breakpoints that are shown to be active in the simulator. Typically in the send and receive message methods of each device.3) Run the scheme above which starts up the watch simulator (running) and creates an iphone simulator.4) Look for the icon for my app in the iphone simulator and click it to run the iphone app.5) Go back to Xcode debug->attach to process and find the pid for my app and attach to it.Hope this helps.KellyM

First, thank you very much for taking the time to reply.I'm glad to see it is working for someone, I did try your workflow and everything is OK but I never see any debug output from the iphone app even though after attaching the PID I can switch the debug pane back and forth between the watch extension and the phone app. The watch extension continues to show debug output, but even though the iphone app process is selectable, and shows me status on CPU and memory usage for both, it does not output any of my debug messages on the phone side of things if I switch the debug pane popup menu to show phone debug messages.My only workaround is to switch the executable in the scheme from the watch app to the phone app, then I can debug the phone side. To go back to editng the watch side, I have to change the executable and re-build. So I can debug one or the other, but not both at the same time.Since it works for you however, it must work, so perhaps I have a setting wrong somewhere. I will continue to mess a

Same story for me, only I have an exsiting project to deal with and the error message is slightly different:UI Testing Failure - Failed to background test runner.What's strange, is that I have no issues with running recording, it's only when it comes to running the tests I get this error.I have tried running a test action on the UI Testing scheme as well as test action on the main app target. Got the same results when running from command line and tried all possible iOS 9.0 simulators. Here's my full log: t = 10.07s Assertion Failure: UI Testing Failure - Failed to background test runner. /Users/maksym.grebenets/Projects/ffx/ci-workspace/mobile-apm-alfred/AlfredAcceptanceTests/AlfredAcceptanceTests.swift:22: error: -[Alfred.AlfredAcceptanceTests testExample] : UI Testing Failure - Failed to background test runner. 2015-08-31 15:29:01.260 AFR-dev[20969:1615111] *** Terminating app due to uncaught exception '_XCTestCaseInterruptionException', reason: 'Interrupting test' *** First throw call stack: ( 0

The WWDC talk Building Watch Apps discusses how to do this.Basically select the Watch App as the scheme in xcode, hit build+run which will build the iOS app and WatchKit app, install the WatchKit app on to the Watch and attach the debugger to the WatchKit Extension. Then in xcode select the iOS app in the scheme selector and select the iPhone as the target device, launch the iOS app by tapping the app icon on the phone and in xcode in the menu bar select Debug > Attach to Process and select your app in the list. This should result in having xcode attached to both processes at the same time.If you want to debug something early in the iOS app's lifecycle you can select Debug > Attach to Process by PID or Name... and type in the process name of the iOS app prior to launching it manually. This way the debugger will be attached right when the app launches.Hope that helps

Hi Max,i had a little difficulty performing the log. Sorry for all the threads:Sep 1 07:07:36 localhost bootlog[0]: BOOT_TIME 1441105656 0Sep 1 07:08:24 localhost syslogd[47]: Configuration Notice: ASL Module com.apple.AccountPolicyHelper claims selected messages. Those messages may not appear in standard system log files or in the ASL database.Sep 1 07:08:24 localhost syslogd[47]: Configuration Notice: ASL Module com.apple.Accounts claims selected messages. Those messages may not appear in standard system log files or in the ASL database.Sep 1 07:08:27 --- last message repeated 1 time ---Sep 1 07:08:24 localhost syslogd[47]: Configuration Notice: ASL Module com.apple.authd sharing output destination /var/log/asl with ASL Module com.apple.asl. Output parameters from ASL Module com.apple.asl override any specified in ASL Module com.apple.authd.Sep 1 07:08:24 localhost syslogd[47]: Configuration Notice: ASL Module com.apple.authd sharing output destination /var/log/system.log with ASL Module com.apple.asl. Outp

The best response is no response. Ignore the reviews and enjoy better dev health.Otherwise, it sounds a bit like you don't have a proper support scheme they can take advantage if they truly wish to interact. Perhaps that should become a heightened focus going forward.

Hi MKGillies,If you are following the steps I posted on these forums for making a USB installer for downgrding back to Yosemite, then preparing your USB drive from El Capitan is easier than that (you don't have to seperately partiton the USB drive). Use these steps:First download the OS X 10.10 Yosemite installer from the Mac App Store in the Purchases section (you may need to hold alt/option while selecting Purchases. Once it's downloaded, just quit the installer and set the downloaded file's name to InstallOSXYosemite.app (make sure only .app, not .app.app)Plug in your USB drive into the computer and open Disk Utility (in Applications).Select the USB drive from the left sidebar and click on Erase tab.Set the name be YosemiteInstaller - leave Format on Mac OS Extended (Journaled) and Scheme as GUID Partition TableNow click on Erase button and wait until the format process completes.Launch the Terminalapp (in Applications/Utilities) and copy-paste the following command in, and then hit Enter:sudo /Ap

good catch. thanks! i should have looked at the other properties. yes, many of the other properties are also null and deeper investigation showed the Simulator had me out in the middle of the North Atlantic! the difficulty lie in setting a test lat/long value and the fact one can do that in multiple places: 1) Edit Scheme, 2) the Simulator Loction menu item, and 3) directly in source.so, if these various settings conflict, what happens? it would be nice to set test lat/long's in one place and everything then just works.thanks again.

Thank you for this bug report. I certainly agree that we should provide some better feedback here (even if only at compile time). To be clear, though, the documentation does clarify that what you're doing by specifying a CLLocation value in the userInfo is unsupported:Each key and value must be of the following types: NSArray, NSData, NSDate, NSDictionary, NSNull, NSNumber, NSSet, NSString, or NSURL. The system may translate file scheme URLs that refer to iCloud documents to valid file URLs on a continuing device.Doesn't mean we can't be more helpful, but you need to change your code regardless.

You're welcome! I guess modifying the source to hard code a location would override anything else. I think setting the simulator location takes priority over the scheme setting -- the simulator can simulate a moving location. If the fixed location of the scheme took priority, the simulator moving location wouldn't work.