Xcode6: Playground not working. All options grayed out on Product menu - xcode6

OS X 10.9.3 iMac
Installed Xcode 6 beta today and I am immediately stuck.
Following an apparently successful install, without errors, I have done nothing more than:
Clicked the "Xcode 6 Beta" icon to run
On the "Welcome to Xcode" screen, clic ked "Get started with a playground"
Created a new Playground file
Error thrown. "Error running playground. Failed to prepare for communication with playground"
All options under the "Product" menu are grayed out: Run, build, etc.
Anyone else, or is it just me?
Tyvm
Keith

I had the same problem. Try closing Playground or Xcode 6(Same thing) and reopen. This seemed to fix my problem.

Related

"Unable to resolve module" debuggerWorker errors in recent react-native releases

I keep my project(s) relatively up to date with the latest RN releases. This error seems to be coming up more and more lately.
Error: Unable to resolve module `./debugger-ui/debuggerWorker.d9da4ed7` from ``:
None of these files exist:
* debugger-ui/debuggerWorker.d9da4ed7(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
Really makes it hard when trying to debug issues and a debugger statement does noting and errors are not reported to the browser tab where the console output goes.
I've already tried wiping node_modules. Is this a known issue with a concrete fix available?
Got stuck with this exact issue for hours. Just found that this occurs only on device where app is already installed with debug mode enabled.
I fixed it by:
uninstalling manually app from device (cmd+H to display simulator home) then long click on app icon and click on cross to delete app => this forces disabling debug mode,
then run app again from xcode.
Enabling debug mode after that works normally.
I had to come across a similar issue after updating #react-native-community/cli-debugger-ui to 4.2.1. Tried out several methods, nothing worked. Reverting #react-native-community/cli-debugger-ui back to 3.0.0 resolved the issue for me.
I closed the app (pressing home twice and swiping up), then started it again from the simulator and it worked.
Happens to me recently using expo and android.
The solution was to clear all Expo Go data:
Long press the Expo go icon
Then select App info
At the bottom of the screen, press Clear Data
And press Clear all data
Relaunch expo go and the react native app

Zerobrane debug on Corona SDK

I try to debug with Zerobrane , code for Corona SDK, but when I press the button to start the debug, popups all the time a window saying that main.lua is used from other programs. There is no other program using the main.lua
When i press the button then the corona simulator starts and this is using the main.lua . When I kill the corona simulator the popup windows disappear.
Any other experienced this?
Thanks in advance
There was a fix for the files not closed, which may be related to this issue. You can try with the current master branch version to see if it fixes the problem.

Can't start RubyMine from app icon after upgrade, only from command line

I just upgraded my RubyMine to v8.0.0 with the custom bundled JDK. After installing it I tried to open the app from it's icon and nothing happened. I mean it showed me the dialog box if I trust the app (this happens whenever you want to open a new installed app for the first time), but afterwards nothing showed up.
I looked through the app processes, and couldn't find the RubyMine app. I also tried the solution from this question:
RubyMine fails to start on Yosemite
No success.
After I ran chmod +x /Applications/RubyMine.app/Contents/MacOS/rubymine, I tried again from the app icon, but it still doesn't seem to work.
I updated my java version to java version "1.8.0_65" and still no luck.
It works when I run /Applications/RubyMine.app/Contents/MacOS/rubymine from the command line.
Just to be clear, before upgrading to v8.0 this problem didn't occur.
I run OS X Yosemite.
Any ideas what can cause this issue?
[UPDATE] I ended up downgrading to v7.1.4 until this gets solved.
Found the problem. Looks like I had to run the app in 64-bit mode.
Right click app icon -> Get Info -> "Open in 32-bit mode" must be unchecked.

xcode 5 issue : "iOS Simulator failed to install the application"

I have just upgraded my xcode version to 5.0. After running application 2-3 times it's giving me error like this "iOS Simulator failed to install the application". This is working fine in old xcode. When I reset the simulator it works fine, but this is irritating again and again.
Can anybody tell me what is the real issue? How can i resolve it.
Did you find new solution for this thing?
Try manually launch the iOS Simulator and from the "iOS Simulator" menu, click "Reset content and settings", then close and rebuild your app. It worked for me.
i got the same problem but solved by following way....
launch the iOS Simulator
Go and click "iOS Simulator" Menu
click "Reset content and settings"
close simulator and rebuild your app.
Above screen shot is showing the way how you can do this...
I think this works for you...!!!
I just used CMD+SHFT+K and quit the simutor and then run again and it's working, no need to reset simulator or delete an applicaiton.I'm not sure but some time it will work.
Just delete the application from the simulator and build it again.
Or try to use a device with different iOS version.

Cannot run project after updating Xcode project settings

Recently I updated my project settings as Xcode recommended. I just pressed a button and they did "everything". However now when I try to run my app on my device it freezes on the loading bar at about 75% and then after 15 seconds it says "build succeeded" but does not run on my device and everything stops as if I had pressed the stop button. I am getting no errors but I am getting the following warnings. It works on the simulator just fine.
For the record I have looked this up and everyone says to add "armv6 or armv7" and I already have this done. I am running deployment target iOS 3.0+
If anyone can help me, it would be appreciated. Thank you!
EDIT
Works on my device when I run leaks in instruments... but won't without instruments
Well, I can't really say much specific here, but if all else fails, I'd try making a new project and copying the content of this project to the new one. This could fix some underlying problems that may have developed in the build settings etc.