The last couple of daily builds simply don’t launch the simulator once installed. No error message, it just exits.
Running latest macOS on late 2016 pro.
Interesting, I’m running 3134 on my MacBook pro without issue.
Are you running the macOS beta or 10.12?
Rob
10.12.6
Does 3132 work?
Rob
I’m at work right now so I can’t test this, but I believe that it does not; If memory serves, it had the same issue as 3134. I will check when I get home.
Can you try running the Simulator from a Terminal window and sending me all the output?
To do this, open a Terminal window and paste this command:
"/Applications/Corona-3135/Corona Simulator.app/Contents/MacOS/Corona Simulator" -no-console yes@Rob 3132 does not work. I try to launch the sim and nothing happens. Currently limited to 3130.
@Perry Output for 3135:
Matthews-MacBook-Pro:mecho matt$ “/Applications/Corona-3135/Corona Simulator.app/Contents/MacOS/Corona Simulator” -no-console yes
Sep 12 01:18:57.344: Activated fonts in ‘Lato-Bold.ttf’ (Lato-Bold)
Sep 12 01:18:57.346: Activated fonts in ‘Lato-Regular.ttf’ (Lato-Regular)
Sep 12 01:18:57.348:
Copyright © 2009-2017 C o r o n a L a b s I n c .
Sep 12 01:18:57.348: Version: 3.0.0
Sep 12 01:18:57.348: Build: 2017.3135
2017-09-12 01:18:57.423 Corona Simulator[3264:1940951] recentDocuments: (
“file:///Users/matt/git/mecho/main.lua”,
“file:///Users/matt/Dropbox/Public/Help/EventXY/main.lua”,
“file:///Users/matt/Dropbox/Public/ScreenGrabTest/main.lua”,
“file:///Users/matt/Dropbox/games/Crank/workshop/mecho/main.lua”,
“file:///Users/matt/Dropbox/LaunchImage/TestBlank/main.lua”,
“file:///Users/matt/Dropbox/games/Crank/workshop/Blank/main.lua”,
“file:///Users/matt/Dropbox/LaunchImage/TestLaunch/main.lua”
Output for 3132:
Matthews-MacBook-Pro:mecho matt$ “/Applications/Corona-3132/Corona Simulator.app/Contents/MacOS/Corona Simulator” -no-console yes
Sep 12 01:20:16.161: Activated fonts in ‘Lato-Bold.ttf’ (Lato-Bold)
Sep 12 01:20:16.163: Activated fonts in ‘Lato-Regular.ttf’ (Lato-Regular)
Sep 12 01:20:16.165:
Copyright © 2009-2017 C o r o n a L a b s I n c .
Sep 12 01:20:16.165: Version: 3.0.0
Sep 12 01:20:16.165: Build: 2017.3132
2017-09-12 01:20:16.254 Corona Simulator[3267:1942560] recentDocuments: (
“file:///Users/matt/git/mecho/main.lua”,
“file:///Users/matt/Dropbox/Public/Help/EventXY/main.lua”,
“file:///Users/matt/Dropbox/Public/ScreenGrabTest/main.lua”,
“file:///Users/matt/Dropbox/games/Crank/workshop/mecho/main.lua”,
“file:///Users/matt/Dropbox/LaunchImage/TestBlank/main.lua”,
“file:///Users/matt/Dropbox/games/Crank/workshop/Blank/main.lua”,
“file:///Users/matt/Dropbox/LaunchImage/TestLaunch/main.lua”
I should note that when I run the above command both 3132 and 3135 started normally.
I wonder if Gatekeeper Path Randomization has gotten messed up (it’s a Sierra anti-malware feature). Occasionally, it just seems to lose the plot and an app needs to be reset.
First thing to try is to simply restart your Mac and try to start the Simulator. If that doesn’t work, trash the /Applications/Corona-3135 folder and recopy it from the DMG.
Unfortunately, no dice. Same result as before.
Build 3154 has solved the problem. Not really sure why, but very happy again.
With build 3206 I’m seeing this problem again and need to run the command above, again.
Have you made any updates to your mac?
Rob
No, exactly the same as last time - it’s been a busy few months.
Ok, there were some security updates, but I’m not on High Sierra.
So is it starting correctly when you use the command line option?
Rob
Yes, just fine. Loading from the .app does nothing, though.
Odd, but I’m glad it’s working…
Rob
Definitely. Although as a developer I’m driven to find out why it is happening. Any suggestions for my further investigation?
What happens when you drop back to a build that wasn’t working? Was it the OS update? Or was it a Corona update or a combination of both?
Rob
I think it was both. Feels like I’m going a bit crazy here because over the past couple of weeks I’ve had to keep updating the command file to launch Corona and after a while it becomes habit, so I forgot to check.
I definitely had to launch 3208 with the command file, but now I go back, every daily build back to 3208 launches just fine from the .app on it’s own.
So maybe it was the OS update as well, but I suspect there is something which got removed and now allows the app to launch(?)
I’m just glad it’s working - thanks!