So I followed your instructions below, and the playground opened and I waited very very patiently for the wheel to stop spinning as it said “running playground”. Then I was met with the following pop up.
"Failed to launch iOS stub for playground execution: error: attach failed: lost connection.” > On Jun 11, 2015, at 12:00 PM, Quincey Morris > <[email protected]> wrote: > > On Jun 11, 2015, at 10:58 , David Grant <[email protected]> wrote: >> >> Playground execution terminated because the process stopped unexpectedly. > > Here’s what I would do: > > 1. Close all projects and any playground windows you have open. > > 2. Go to the Projects window (that’s been split out from the organizer), and > delete any entries for various playgrounds you have previously created. I’m > not sure this does anything useful, but there’s no “Clean” function for > playgrounds, and it’s possible this will clean something out. > > 3. Quit and relaunch Xcode. Watch the status area in the toolbar to make sure > you wait until it’s finished spinning after relaunch. You may even want to > use Activity Monitor to check that Xcode goes pretty much idle. (It’s not > necessarily a problem if it’s still doing something, but it gets confusing if > that delays what you do next to the point of it seeming broken.) > > 4. Create a new iOS playground. Again, wait for it to go idle or crash or > report an error. This might take a minute or so. > > 5. Click the “Show the Debug Area” button in the bottom left, and check there > for error messages. > > 6. Check the system log (via Console utility) to see if anything has been > logged there. > > 7. If you still don’t see the “Hello, playground” output, submit a bug report > and attach the playground. > > You can then play around trying things like closing and re-opening the > playground, quitting and relaunching Xcode, and using Editor -> Execute > Playground to see if you can get it to start working. The key is to try one > thing at a time, and *wait* to see what happens, since some errors take a > while to be logged. > > My guess is that if you can get it work once, it will work fine after that. > If you can’t get it to work once, then there’s probably something corrupt in > Derived Data (or a similar cache location) that’s preventing Xcode from > running the playground process. > _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
