show when run

Can anyone suggest what I need to do to get the new Swift Standard Library to run with Xcode 7 beta on OS 10.10.3 (i.e. _not_ 10.11 beta)?I consistently get Unable to find a suitable target device as soon as I go to a playground page with executable code in it. Prompted by a Stackoverflow suggestion for a previous version of Xcode, I have tried creating an iOS 9 simulator device, but that has not solved the problem. Unlike a full-fledged project, a playground does not seem to have any way of attaching it to a device, real or simulated.

Two parts to session:Transitioning to IPv6-only networksReducing Delays in NetworkingTransitioning to IPv6-only networksMore mobile carriers are moving to IPv6 networksIn Ye Olde Days, cellular data networks used IPv4. As IPv4 addresses ran out, NAT was introduced to make IPs go further.To fix the long-term problem, mobile carriers are now moving to IPv6. But they're also having to support IPv4 with NAT.The carriers want to drop IPv4 with NAT, so they're deploying DNS64/NAT64 to handle translation between IPv4 and IPv6 networks.DNS64 synthesizes an IPv6 address for an IPv4-only serverNAT64 performs IPv6 to IPv4 address translationApp Store apps need to be IPv6 ready - It will be an app submission requirement later in 2015.Enabling IPv6 test network from a Mac1. Boot OS X 10.112. Open System Preferences3. Option-click on the Sharing preference pane4. Option-click on Internet Sharing5. A Create IPv6 Only Network checkbox will appear6. Check Create IPv6 Only Network (this may also be labeled Create NAT64 Network

Hello Everyone,Like many others i installed Watch OS 2 on my Apple Watch a few days after WWDC. Since then the experience of using the Watch was a complete nightmare. I have had many problems including contacts not syncing via my iPhone, not receiving notifications, home screen freezing , the watch running warm against my skin, and worst of all poor battery life. My watch only seem to last 4 hours on a single charge ever since the beta was installed. Even though Apple has not documented a way to downgrade. I decided to try to figure out a solution on my own. I tried many things like downgrading my iPhone to iOS 8.3 to see if I could force a downgrade, nothing happened. I even tried resetting the watch back to factory settings and setting up as a new watch, still nothing happened. The Apple watch app even showed me an alert saying that my iOS was out of date to use the watch. As a final resort i reupgraded my iPhone to iOS 9 just to get the Watch paired up to use, until the next beta or until

Not sure if this is the best place to post this, but I couldn't find a dedicated HealthKit forum, so I figure this is best.I'm creating an app that tracks workouts at the gym. I've created an HKWorkout and set its activity type to HKWorkoutActivityType.TraditionalStrengthTraining. I run my HKWorkoutSession, the calories get counted, and the workout gets logged in the Health app when completed, but the workout time (I tried five minutes) didn't get added to my green exercise ring on my Apple Watch.It was mentioned in the WWDC keynote that WatchKit apps can contribute to the exercise ring, so I'm wondering if I'm missing something?Another thing I noticed is that while the HKWorkoutSession is created, and I am able to save it later on, my WatchKit app does not stay in the foreground while the workout session is currently in progress. Perhaps this hasn't been implemented in the first beta?

I've got an existing CloudKit based app that I'm trying to put a map into (via MapKit). CloudKit is currently storing building names, photos and also includes a location record for latitude and longitude for each building. I'm trying to search for a tutorial or example so I can see how to properly download CKRecords and use the locations to provide annotations/pins in a MapKit view.I'm not having any luck, though. I've run across a couple older Objective-C examples, but nothing recent and in Swift. Has anyone else seen something I might be able to use?

Greetings,I am not having a problem compiling or locating an error. I am wondering if there is a way to actually look deeper into what is happening behind the scenes. For example I am presently reading a book on Mathematics to Genereric programming. I have found this book to be very enlighting so far but I am trying to under what is happening to the code behind the scenes. I know in Visual studios the IDE will show you the binary while debugging. Is there a way I can see it with xcode as well? I will show you an example of the I am break pointing to so that I what's happening.// Helper methodsbool odd(int n) { return n & 0x1; }int half(int n) { return n >> 1; }I want to see what is happening with the return n & 0x1 values. I was also trying to debug the bit shifting method as well to see the values and what is going on.Here is the code I am running it against with some random values.Again, the program works. I am trying to see what is happening with bit shift and the n

Hello,I'm getting an error when attempting to make a new iOS playground on Xcode 7 beta.The error is as follows:Error running playground.Unable to find suitable target device.I haven't found many similar cases to assume this is a bug in the beta. Has anyone else had this error or have had luck fixing it?

I'm writing a code for WatchOS2 extension that uses CMAccelerometerData.Built with no error, running correct scheme, installed in Apple Watch device, but nothing happend.Can not even stop breakpoint on first line.Something missing ?@implementation ExtensionDelegate- (void)applicationDidFinishLaunching { motionManager = [[CMMotionManager alloc] init]; motionManager.accelerometerUpdateInterval = 0.1; if (motionManager.accelerometerAvailable) { [motionManager startAccelerometerUpdatesToQueue:[NSOperationQueue currentQueue] withHandler:^(CMAccelerometerData *accelerometerData, NSError *error) { double xx = accelerometerData.acceleration.x; NSLog(@%lf, xx); }]; }}@end

I can build, run and debug watchOS 1 apps absolutely fine. When I try and build/run watchOS 2, Xcode runs for a bit, beachballs after a while and then it eventually stops. I can usually get the app on by manually installing via the iOS Apple Watch app.No debugger or logs though..Has anyone figured out a workaround or is this just not possible in the current beta?Simulator builds are all ok but I'm experimenting with Core Motion so it only really works on device..Note.. I'm trying with a brand new project, no changes. I believe everything is correctly provisioned..