Now that Mountain Lion and Xcode have both gone to Gold Master seed status, I dare ask, has anyone taken the plunge to install it and does Corona SDK still work and build binaries properly with it? [import]uid: 6084 topic_id: 28475 reply_id: 328475[/import]
By the way, I would have asked this in the Install Help subforum, but it disappears when I log into the site. Very strange. [import]uid: 6084 topic_id: 28475 reply_id: 114930[/import]
We have been tracking Mountain Lion and the new Xcode. We think it works with the caveat that you need to (just for now) disable GateKeeper. Internally, we already have applied and received our DeveloperID certificate, but our signed builds have not yet been merged into mainline/daily-builds yet. We would appreciate any bug reports you find running the latest OS/Xcode.
[import]uid: 7563 topic_id: 28475 reply_id: 114972[/import]
One additional tidbit for those who don’t want to disable GateKeeper, instead of disabling GateKeeper, you can permit apps to run on a per-app basis if they are not signed. Using the command line tool spctl:
spctl --add /Applications/CoronaSDK/Corona\ Simulator.app
[import]uid: 7563 topic_id: 28475 reply_id: 114987[/import]
Well, I decided to take the plunge and test out Mountain Lion 10.8 GM and Xcode 4.4 GM. Corona SDK build 846 successfully runs and compiles my iOS app. Didn’t even check the GateKeeper feature yet. Thanks, and keep up the great work. [import]uid: 6084 topic_id: 28475 reply_id: 114993[/import]
Ok, I take it back a little bit. Corona build 846 is crashing about every third or fourth run of the Simulator in Mountain Lion. It’s annoying, especially when I have to restart the Simulator and Terminal.
Getting a lot of this in the Terminal:
[text]The file sandbox for this project is located at the following folder:
(/Users/BeyondtheTech/Library/Application Support/Corona Simulator/MyApp-FD83EC2E4368E69712DEC0902A233EB9)
/Applications/CoronaSDK/Corona Terminal: line 9: 55308 Segmentation fault: 11 “$path/Corona Simulator.app/Contents/MacOS/Corona Simulator” $*
logout[/text] [import]uid: 6084 topic_id: 28475 reply_id: 115086[/import]
I just tried 846 with the Bridge example and relaunched the simulation a dozen times and could not crash it. I have not seen any crashes like this in any of our previous testing. I need a specific procedure to reproduce the crash. The Apple crash log would be helpful to. (Please file a bug report with us and attach the crash log as well as the reproducibility instructions.)
[import]uid: 7563 topic_id: 28475 reply_id: 115175[/import]
@ewing One can also ctrl-click or right-click on Corona and go “Open” and accomplish the same thing. [import]uid: 73951 topic_id: 28475 reply_id: 115228[/import]
Really strange stuff. Haven’t rebooted or anything, just relaunched the Simulator and now I can’t get it to crash. I guess that’s a good thing.
Enclosed is the crash log from when it was doing it. Maybe you can spot something in it.
http://cl.ly/1x11212S222p2w093i47
The crash was happening when I was working on my .lua files and I would make a change, save it, and the Corona Simulator would automatically restart. I see it redrawing the iPhone skin, and then it crashes.
Speaking of which, whatever happened to my request to make it “skinless?” I’m working on a MacBook Air 11" which has a very limited resolution of 1366x768, so seeing a really large iPhone 4 skin edging out the top and bottom and covering up most of the screen real estate is overbearing. It’s nice to see, but not always necessary. Please include an option to just make it a vanilla or borderless window!
[import]uid: 6084 topic_id: 28475 reply_id: 115232[/import]
Speaking of which, whatever happened to my request to make it “skinless?” I’m working on a MacBook Air 11" which has a very limited resolution of 1366x768, so seeing a really large iPhone 4 skin edging out the top and bottom and covering up most of the screen real estate is overbearing. It’s nice to see, but not always necessary. Please include an option to just make it a vanilla or borderless window!
Sorry, but I have to agree as am in the same situation as @BeyondtheTech by one year right now on my Macbook 13".
Thanks,
Rodrigo. [import]uid: 89165 topic_id: 28475 reply_id: 115244[/import]
Hmmm, that crash log suggests to me that it is Apple’s stuff that is crashing. Thread 5 crashed which has ImageKit stuff. We use that to draw the skin image around the window. It’s a pretty simple API and we aren’t doing much with it except simply asking it to draw the image (which is what it is designed for).
If you encounter it again, let us know, but I also recommend filing a bug with Apple (include the crash log), state it is hard to reproduce, and letting them know what I told you here about the use of IKImageView. Maybe we’ll get lucky and there is an engineer at Apple that has a good hunch on what’s wrong and will fix it.
[import]uid: 7563 topic_id: 28475 reply_id: 115254[/import]
Ah… In the meantime, this could be our push to go towards our request for a skinless Simulator! Pretty please, it doesn’t hurt anyone to have that option! [import]uid: 6084 topic_id: 28475 reply_id: 115255[/import]
I have been running OSX10.8 and XCode 4.4 combined with CoronaSDK for a while already (actually since 10.8 +Xcode 4.4 came out in beta). Apart from the Gatekeeper warning when I first tried it (by default it’s set to AppStore+Cert Devs only), I have had no issues with the combination. And I don’t see that imageKit crash either, although I must admit I’ve never bothered to check any logs.
Regarding the borderless simulator, I vote for that too. But there is something like virtual desktops, guys 
[import]uid: 106658 topic_id: 28475 reply_id: 115291[/import]
I have an update on 10.8 support here:
http://www.coronalabs.com/blog/2012/07/23/corona-how-to-train-your-mountain-lion/ [import]uid: 26 topic_id: 28475 reply_id: 116791[/import]