App crash at start with XCode5 and iOS simulator

Solar2D iOS
#21

I also recently installed Maverick and 5.

now when building for device, I’m getting a darkened version of the icon on the device screen on what appears to be install completion. when you click on the darkened icon, it says “installing”. iTunes says “finishing sync” forever.  the console says: <Error>: 0x345000 __DeleteLibrarian_block_invoke: unable to determine evictable space: The operation couldn’t be completed. (LibrarianErrorDomain error 10 - Unable to configure the collection.)

librariand[134] <Error>: ubiquity account is not configured (or is disabled for this client), not creating collection

 <Warning>: Can’t get bundle identifier for process 2024

<Error>: error in _handle_client_request: LibrarianErrorDomain/10/Unable to configure the collection.

it won’t install on iPhone5 or iPad running iOS7.

I’ve even uploaded .ipa version to test flight and tried to install from there. same issue. thanks. I r4ally need to test changes in my app.

#22

p.s., I tried it from the latest daily build. same results.

#23

My Builds are failing now also (device and xcode), but they did work before my vacation in August. The message I get is a {null} over a yellow exclamation mark.

I have been using the free version and building ok for my own-use app trials.

Since then I have installed Maverick, Xcode Version 5.0.1 (5A2053) and  downloaded the 2013 1202 build. I fell back to the  working Corona 2013.1135 (2013.6.3) and that now fails with same issue.

So is it the Xcode upgrade, Maverick or something else I am missing.

Clues are very few …

Anyone know what the {null} message should really mean?

Thanks

#24

What message is in your console log??

#25

Several people have reported that cleaning out your keychain of it’s keys and certificates and provisioning profiles and regenerating all of them seems to have helped.

#26

Rob,

Thanks for the memory jog to check the consule,

The build seemed to be finding old assets that are not used. These are not referenced in the code and therefore test run ok.

I have deleted the assets from the Outlaw project and from the Mac folder. Still failed. So shut down simulator and Outlaw and restarted build after making sure all unused code assets were remove- NOW BUILDING!

Here is the Console

04/11/2013 01:04:08.025 Corona Simulator[6326]: The file sandbox for this project is located at the following folder:
    (/Users/aleccockleNewMacbook/Library/Application Support/Corona Simulator/236-E6D8975B6377F043451D9D9A03E0CCB0)
04/11/2013 01:04:43.723 Corona Simulator[6326]: COMPILE ERROR: Could not complete build because there were compile errors in Lua file (/Users/aleccockleNewMacbook/Library/Application Support/Outlaw/Sandbox/236/Scenes/SwingTally.lua).
 

#27

clearing out my keychain keys appeared to do the trick for me.

(had to regenerate my developer certificate)

oddly, the app crashes on initial load (as triggered by the compiler) but manually launching the app, it doesn’t crash like it was before.

using 2013.1251

#28

I’m sorry for the noob question but im relatively new to corona. Im having the same problem. Crash when trying to deploy app to Simulator AND device.

How can I clean the keychain certificates?

Best regards 

#29

You run the “KeyChain Access” app and hunt through there to take care of keys and certificates. 

#30

Rob, 

Cleaning out/restoring the keychain certificates worked for me to get it working on the iOS Simulator.  Everything except the 64 bit simulator(s) works although it does run slow in Xcode simulator.  My app works great on actual devices, never crashes. I’ve tested on 3GS, 4S, 5, 5s, iPad mini non retina, and iPad 3.  All work great. Would there be any reason why iOS simulator 64 bit would crash? It always runs great on the Corona simulator, 5s device and all devices I’ve tested?

#31

What Mac are you using?

What version of Corona SDK?

What version of OSX?

What version of Xcode?

#32

Late 2011 MacBookPro 17" 2.5 GHz Intel Core i7

OSX 10.9.1

Build 2013.1235 - Also tried build 2014.2183 with same crashing results on 64 bit simulators

Xcode 5.0.2

#33

Can you describe what you  mean by “Crash”?  Is the Xcode simulator exiting?  Is your app just exiting on it?  Are there helpful messages in the console?  Remember the Xcode simulator outputs to the specific app:  “Console”.

Look there for any messages that might help track this down.

Rob

#34

It “crashes”/closes out of the app back to home screen of simulator after the default/splash screen is displayed. The system.log states “exited abnormally with signal 9: Killed: 9”  and in the console it also states " taskgated[14]: killed …(com.company.app)…[pid 26975] because its use of the keychain-access-groups entitlement is not allowed (error code -67030)" 

#35

Does this happen if you build the Hello World app?

Rob

#36

Yes

Correction, sorry that was in build 2013.1235.  In build 2014.2183 the Hello World app does NOT crash, My app only crashes on 64 bit iOS Simulators. 

#37

If I build my app using my standard development Provisioning profile instead of the actual app specific profile, It works fine. 

#38

Rob, I was able to fix this by re-generating my app provisioning profile using a different prefix on the appID that I had. It works on all iOS simulator now.  Thanks. 

#39

Rob, 

Cleaning out/restoring the keychain certificates worked for me to get it working on the iOS Simulator.  Everything except the 64 bit simulator(s) works although it does run slow in Xcode simulator.  My app works great on actual devices, never crashes. I’ve tested on 3GS, 4S, 5, 5s, iPad mini non retina, and iPad 3.  All work great. Would there be any reason why iOS simulator 64 bit would crash? It always runs great on the Corona simulator, 5s device and all devices I’ve tested?

#40

What Mac are you using?

What version of Corona SDK?

What version of OSX?

What version of Xcode?