Build error when building app for xcode simulator

@Tom I clicked on the app icon as well: same result. Any news on a public release ? Thanks. St

@st.tosi, does your app run on a real iOS device? Failure to run on the Xcode Simulator doesn’t always means it’s an issue with Corona. Bugs in your app can result in the same behavior. You should always test on a real device to verify and review the console output to make sure there are no errors in your code. You should also enable runtime error messages on your device when debugging code (they are off by default). You enable the runtime error mode in the config.lua.

http://docs.coronalabs.com/guide/basics/configSettings/index.html#runtime-errors

If you still think there is a problem running the simulator, try building and running a sample project (e.g., HelloWorld) on the Xcode Simulator. 

We don’t have a release date for the next public release because we are still sorting out issue related to iOS 8.1 and iPhone 6. You can always pay to be a Pro user and get access to all our daily builds. 

@Rick

I am now running Yosemite with (always) corona public build 2393.

I did again as per your suggestion: build Corona for Xcode simulator/converted the .app to a .ipa/renamed .zip/unpacked and in the Payload folder my .app file is created.

I then run 

ios-sim launch /Users/stefanotosi/Desktop/Payload/myAppName.app   --devicetypeid “com.apple.CoreSimulator.SimDeviceType.iPhone-6, 8.1”

The app is loaded in the iPhone6 / iOS8.1(12B411) simulator. The app shows the default image and then crashes.

The console log shows:

Oct 28 16:42:57 iMacSt-2 assertiond[18851]: assertion failed: 14A389 12B411: assertiond + 11523 [3F572A0B-7E12-378D-AFEE-EA491BAF2C36]: 0x1

Oct 28 16:43:00 iMacSt-2 PopChase[18924]: assertion failed: 14A389 12B411: libxpc.dylib + 59417 [464E62EA-4CF2-3FEF-9C17-692AD8D66AA8]: 0x7d

Oct 28 16:43:00 iMacSt-2 com.apple.CoreSimulator.SimDevice.B68C61D9-576C-4D88-8BE7-E34247ADD5E4.launchd_sim[18836] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.

 My app works fine on an iPhone 5/iOS8.1 device.

I need to run in the simulator to check for iPhone6 and 6Plus graphics as well as getting the screenshots for ITC.

Can you help ?

@Tim

any news on an update on public build ?

Thank you all

st

I’m also getting an error with the openssl plugin now, even with the latest daily build when building for the XCode Simulator. Device builds are finishing, but the resulting build will not load on the device (i.e., install will fail). Building without the openssl plugin does work with the same exact code (just taking the plugin out of build settings), though of course I get a runtime error when I run the app due to lack of the library. My wild guess is that this might have something to do with the new 64-bit format? Though I got this error even using an older corona build, prior to 64-bit support, I believe.

Just checked: It does seem to work in XCode 5.02, by the way.

Environment:

Mac OSX 10.9.5 Corona build: 2015.2533 (2015.1.9) XCode: Version 6.1.1 (6A2008a)

Error: 

1/10/15 4:58:34.856 PM Corona Simulator[22822]: Runtime error /Users/xx/Dropbox/app/xxx.app/.build/libtemplate/Builder.lua:310: \<error\>{"status":256,"message":"ld: warning: ObjC object file (/Users/xx/Dropbox/app/xxx.app/.build/libtemplate/libtemplate.a(main.o)) was compiled for iOS Simulator, but linking for MacOSX\nUndefined symbols for architecture i386:\n \"\_fwrite$UNIX2003\", referenced from:\n \_int\_rsa\_verify in libplugin.openssl.a(rsa\_sign.o)\n \_test\_rc4\_init\_key in libplugin.openssl.a(eng\_openssl.o)\n \_TXT\_DB\_read in libplugin.openssl.a(txt\_db.o)\n \_read\_string in libplugin.openssl.a(ui\_openssl.o)\n \_read\_string\_inner in libplugin.openssl.a(ui\_openssl.o)\n \_ENGINE\_load\_gost in libplugin.openssl.a(gost\_eng.o)\n \_dtls1\_retransmit\_buffered\_messages in libplugin.openssl.a(d1\_both.o)\n ...\nld: symbol(s) not found for architecture i386\nclang: error: linker command failed with exit code 1 (use -v to see invocation)"}\</error\> stack traceback: [C]: ? [C]: in function 'assert' /Users/xxx.app/.build/libtemplate/Builder.lua:310: in function 'checkError' /Users/xxx/app/xxx.app/.build/libtemplate/Builder.lua:333: in function 'build' ?: in function 'buildExe' ?: in function \<?:796\>

I also funda galaxy note 4 was about to post this. My xcode simulator never opens funda galaxy A7 after build process.

Hi Tom. Another month, anything yet?

We are close.  We are madly testing away.

Rob

Thanks for the update Rob

@Rob

the sooner the best !

Thanks 

st

I’m also getting an error with the openssl plugin now, even with the latest daily build when building for the XCode Simulator. Device builds are finishing, but the resulting build will not load on the device (i.e., install will fail). Building without the openssl plugin does work with the same exact code (just taking the plugin out of build settings), though of course I get a runtime error when I run the app due to lack of the library. My wild guess is that this might have something to do with the new 64-bit format? Though I got this error even using an older corona build, prior to 64-bit support, I believe.

Just checked: It does seem to work in XCode 5.02, by the way.

Environment:

Mac OSX 10.9.5 Corona build:&nbsp;2015.2533 (2015.1.9) XCode:&nbsp;Version 6.1.1 (6A2008a)

Error: 

1/10/15 4:58:34.856 PM Corona Simulator[22822]: Runtime error /Users/xx/Dropbox/app/xxx.app/.build/libtemplate/Builder.lua:310: \<error\>{"status":256,"message":"ld: warning: ObjC object file (/Users/xx/Dropbox/app/xxx.app/.build/libtemplate/libtemplate.a(main.o)) was compiled for iOS Simulator, but linking for MacOSX\nUndefined symbols for architecture i386:\n \"\_fwrite$UNIX2003\", referenced from:\n \_int\_rsa\_verify in libplugin.openssl.a(rsa\_sign.o)\n \_test\_rc4\_init\_key in libplugin.openssl.a(eng\_openssl.o)\n \_TXT\_DB\_read in libplugin.openssl.a(txt\_db.o)\n \_read\_string in libplugin.openssl.a(ui\_openssl.o)\n \_read\_string\_inner in libplugin.openssl.a(ui\_openssl.o)\n \_ENGINE\_load\_gost in libplugin.openssl.a(gost\_eng.o)\n \_dtls1\_retransmit\_buffered\_messages in libplugin.openssl.a(d1\_both.o)\n ...\nld: symbol(s) not found for architecture i386\nclang: error: linker command failed with exit code 1 (use -v to see invocation)"}\</error\> stack traceback: [C]: ? [C]: in function 'assert' /Users/xxx.app/.build/libtemplate/Builder.lua:310: in function 'checkError' /Users/xxx/app/xxx.app/.build/libtemplate/Builder.lua:333: in function 'build' ?: in function 'buildExe' ?: in function \<?:796\>

I also funda galaxy note 4 was about to post this. My xcode simulator never opens funda galaxy A7 after build process.