yes: console.app
All Messages (not to miss something)
it looks like the composer does not make the gotoScene that is the last statement of my main.lua. I tried to remove that line and run in the device: the screen is same as in the simulator. Hope this may help
Well, I’m not sure what’s going on with Xcode not outputing to the Console.app. It could be something new with Xcode 6.
As for your issue, without seeing code related to where the problem is happening, all we can do is guess. Like I said earlier, it’s very likely that if you are expecting 4 things to draw on the screen and only 2 do, there is a problem either with item #3 or the code in between loading #2 and loading #3.
Rob
New test here:
environment: OSx 10.9.5/Corona2393/Xcode6/iOS simulator iPhone5/iOS8.0(12A365)
I’ve run in the Corona simulatore the HelloWorld. Add a line print(“Hello World”). Built for Xcode simulator. Launched the iOS Simulator (Xcode6, using terminal xcrun simctl etc.)
Installed the HelloWorld.app
Runr the Console.app in iMac. All messages. Cleared the window.
Launched in the iOS simulator the HelloWorld app. It runs in the simulator.
Console output: none.
Attached please fine my main.lua and menu.lua: the scene (supposed to be) launched at the end of main. In the simulatore it is not. It is in the device
Rob: it is time here for me to sleep.
I am confident we could sort this out in some way.
I look forward to your reply on this.
st
I suspect this is your issue:
stage=display.getCurrentStage()
stage:insert( background )
stage:insert (infoLabel)
stage:insert(composer.stage)
stage:insert(HUDgears)
What is composer.stage when this executes? Since you have not created any scenes yet, this may not be a display group or object that you can insert at that point.
The way composer works, is that any display object not part of the scene sits on top of the scene. I’m not sure what infoLabel is, but why not simply create your HUDgears, don’t put it in the stage. Add your background and infoLabel as part of the scenes themselves?
Rob
as I wish the infoLabel and HUDgears stay on top of everything later created in the scenes. Similar to a military HUD.
I will investigate on that. Thank you.
removed the line stage:insert(composer.stage) according to your comment.
In the iOS simulator behavior remains the same.
??
st
- For the composer.stage comment: I did as per the documentation in the composer.stage API:
– Sort everything in the correct z-index order
local stage = display.getCurrentStage()
stage:insert( background )
stage:insert( composer.stage )
stage:insert( meter )
– Open the initial scene
composer.gotoScene( “scene1”, “fade”, 800 )
I am confused.
- iOS Xcode6 simulator: I confirm I do not see any print(…) message in the console app. Print(…) statements exist in the main.lua and are correctly executed in the physical device. Done this test with the stage:insert(composer.stage) statement removed.
What I see in the Xcode iOS 8.0 simulator is the main screen only as if the last statement composer.gotoScene were not executed. All display objects shown come only from the main.lua: a background image (newImageRect) ; an ImageSheet (named HUDGears); a newText named infoLabel.
The app runs in the simulator as an event from the Game Center linked to the infoLabel does change the content shown on the screen.
The scene menu.lua, called as the last statement of main.lua, is simply not loaded.
- iiOS Xcode6 simulator: run iPhone5/iOS 7.1 simulator (xcrun simctl etc.) instead of 8.0. Same results as above. Problem not iOS-version-depending.
How long to wait for a public Corona release with iOS simulator 6 properly running ? Maybe it is worth waiting for that ?
We don’t have an ETA on a new public release. There are still too many outstanding issues like this Xcode bug (which isn’t a Corona thing but something we have to figure out)
To view the Xcode 6 iOS Simulator console click on the Debug menu and choose Open System Log…
Xcode 6.0.1
build number: 2393a
OS: OSX Mavericks 10.9.5
My application runs fine on all the simulators except (iphone 5s, iphone 6 and iphone 6-plus and ipad-Air).
the terminal is giving me “could not verify application”
what should I do ???
knowing that I added all launch images and icon sizes.
the user ingemar posted something about interface builder: you can check it here
Is this of any importance for them to run?
Any help is appreciated
Edit 1: simulator’s system log upon running on iphone 6 simulator
Oct 15 12:24:49 Users-mac assertiond[2018]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1
Oct 15 12:24:49 Users-mac com.apple.CoreSimulator.SimDevice.FE8BCADD-5F1E-484D-B507-F39A406D0263.launchd_sim[2003] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
Oct 15 12:24:49 Users-mac AppName[2124]: assertion failed: 13F34 12A365: libxpc.dylib + 59417 [75E30F22-514B-3A20-B82C-EDA43AF5C35C]: 0x7d
Oct 15 12:24:49 Users-mac assertiond[2018]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1
Oct 15 12:24:49 — last message repeated 1 time —
Oct 15 12:24:49 Users-mac SpringBoard[2014]: [MPUSystemMediaControls] Updating supported commands for now playing application.
Oct 15 12:24:50 Users-mac com.apple.CoreSimulator.SimDevice.FE8BCADD-5F1E-484D-B507-F39A406D0263.launchd_sim[2003] (UIKitApplication:com.User.appName[0xdafe][2124]): Service exited with abnormal code: 1
Edit 2: another user is having the same problem : link here
~ b0b_k
Can you try and run the Hello World sample app on the simulators that are causing you problems?
Rob
Hello World sample is also not running on the simulated iPhone 5s.
Marker - 16.10.2014 08:01:14 Oct 16 08:01:17 thomasmac assertiond[717]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1 Oct 16 08:01:18 thomasmac com.apple.CoreSimulator.SimDevice.9AEB3AC1-F4A0-4BA2-A3A9-7B781BC6BFCD.launchd\_sim[702] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The \_DirtyJetsamMemoryLimit key is not available on this platform. Oct 16 08:01:18 thomasmac HelloWorld[765]: assertion failed: 13F34 12A365: libxpc.dylib + 59417 [75E30F22-514B-3A20-B82C-EDA43AF5C35C]: 0x7d Oct 16 08:01:18 thomasmac assertiond[717]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1 Oct 16 08:01:18 thomasmac.fritz.box SpringBoard[713]: [MPUSystemMediaControls] Updating supported commands for now playing application. Oct 16 08:01:18 thomasmac com.apple.CoreSimulator.SimDevice.9AEB3AC1-F4A0-4BA2-A3A9-7B781BC6BFCD.launchd\_sim[702] (UIKitApplication:net.app-artist.mathsartists[0x45b0][765]): Service exited with abnormal code: 1 Oct 16 08:01:18 thomasmac.fritz.box SpringBoard[713]: Application 'UIKitApplication:net.app-artist.mathsartists[0x45b0]' exited voluntarily. Oct 16 08:01:18 thomasmac assertiond[717]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1 Oct 16 08:01:18 thomasmac.fritz.box SpringBoard[713]: Unable to deliver -[UIRemoteApplication showTopMostMiniAlertWithSynchronizationPort:] message to port 0: (ipc/send) invalid destination port Oct 16 08:01:22 thomasmac com.apple.CoreSimulator.SimDevice.9AEB3AC1-F4A0-4BA2-A3A9-7B781BC6BFCD.launchd\_sim[702] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The \_DirtyJetsamMemoryLimit key is not available on this platform.
On the xCode iPhone 5 simulator it works without problems.
In some threads i often read that we have to build the application with the 7.1 SDK. How can i manage this? I have no build option in the corona simulator to change the iOS SDK.
Nop, it didn’t work with the given set of simulators (5s,6,6-plus and ipad-air)
I even tried following this thread as well : here and it didn’t work 
Hi, I am getting the same problem. Trying to run on xcode sim for iphone 6 and 6 plus so I can get some screen shots.
Splash screen appears ok, then app closes. Console Shows as below.
Note app runs fine on a real iPhone6+
Oct 16 22:58:47 — last message repeated 1 time —
Oct 16 22:58:47 Richards-iMac assertiond[18994]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1
Oct 16 22:58:49 Richards-iMac com.apple.CoreSimulator.SimDevice.BFA81011-82CA-4A78-8892-99AC8CCEB4C3.launchd_sim[18979] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
Oct 16 22:58:49 Richards-iMac TaskPad+[19425]: assertion failed: 13F34 12A365: libxpc.dylib + 59417 [75E30F22-514B-3A20-B82C-EDA43AF5C35C]: 0x7d
Oct 16 22:58:49 Richards-iMac assertiond[18994]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1
Oct 16 22:58:49 Richards-iMac.local SpringBoard[19050]: [MPUSystemMediaControls] Updating supported commands for now playing application.
Oct 16 22:58:49 Richards-iMac com.apple.CoreSimulator.SimDevice.BFA81011-82CA-4A78-8892-99AC8CCEB4C3.launchd_sim[18979] (UIKitApplication:uk.co.littleredrocket.taskpadplus[0xcb79][19425]): Service exited with abnormal code: 1
Oct 16 22:58:49 Richards-iMac.local SpringBoard[19050]: Application ‘UIKitApplication:uk.co.littleredrocket.taskpadplus[0xcb79]’ exited voluntarily.
Oct 16 22:58:49 Richards-iMac.local assertiond[18994]: notify_suspend_pid() failed with error 7
Oct 16 22:58:49 Richards-iMac assertiond[18994]: assertion failed: 13F34 12A365: assertiond + 11619 [03CE1BE5-ACCB-3989-A453-41D167A25E66]: 0x1
Oct 16 22:58:49 — last message repeated 1 time —
Oct 16 22:58:49 Richards-iMac.local SpringBoard[19050]: Unable to deliver -[UIRemoteApplication showTopMostMiniAlertWithSynchronizationPort:] message to port 0: (ipc/send) invalid destination port
Oct 16 22:58:53 Richards-iMac com.apple.CoreSimulator.SimDevice.BFA81011-82CA-4A78-8892-99AC8CCEB4C3.launchd_sim[18979] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
The current public build is not designed to work with Xcode 6’s way of running the simulator. If you need this, you will either need to wait on the next public build (no ETA as we are still working on things) or upgrade to Pro or Enterprise to gain access to Daily builds.
Rob
See next post …
The “A fatal error has occurred” message happens when the Corona Simulator application has been damaged (usually files added or removed from the app bundle).
You can run the verification process yourself in the Terminal and it might provide a hint if you don’t already know what’s going on:
/usr/bin/codesign --verify '/Applications/CoronaSDK/Corona Simulator.app'I see in another communication that you are running OSX 10.9.5. Apple changed the way it handles code signing of apps in 10.9.5 and above in a way that apparently breaks older builds. Any release prior to 2398 is affected though the current public release is fine because we went back and re-signed that to avoid an alarming GateKeeper message that 10.9.5 would show otherwise.
Because of Apple’s Gatekeeper change in Mac OS 10.9.5, all Corona SDK builds before 2393a will not run. If you need to use an older version of Corona on a Mac, don’t upgrade to Mavericks 10.9.5.