app crashes in xcode simulator iOS 7 SDK

Solar2D iOS
#61

I realised that the Starter could not see daily builds. I was just going to buy into the Basic but there will be no benefit there either then.

H’mm it is really frustrating/costly to be stopped using your products that you advertise as being able to publish to the app store, but now we cant do that if we stay up to date with Apple code and Corona public releases because of this bug.

I think there is a case here for your consideration of this solution being available in the daily build, to be quickly promoted to Starter and Basic level for public release, otherwise as you are not at the moment conforming to your ads.  As I see it, I have to wait now for 3-4 months  before I can publish and test on a device, maybe not even  then?

I think this could be a business risk to your company if some Starter or Basic user has the funds to pursue this non-conformity…

May be check not the techy side of the business, but the legal!

Any way are there any technical alternatives in Corona for us Starter and Basic users to overcome this earlier?

#62

@ibmprgmrsince1964, I think you mis-read what I said.  I was not saying you will have to wait 3-4 **MORE** months.  The current public build is about 2.5 months old.  We’ve got some bugs to knock out of the new Graphics 2.0 engine before we can release a new public build.  We will probably be freezing the branch soon and entering the deep testing phase.  We can’t commit to an exact date because there are too many variables but it won’t be that much longer.

The benefit of a Basic plan is to get access to InApp Purchases.  Daily builds are a benefit to Pro and Enterprise subscribers. 

This particular bug only impacts the Xcode simulator with Mavericks.  It does not impact device builds.  So far everyone suffering issues with device builds have been able to solve their problem by cleaning out their keychain.  You do not have to do XCode Simulator builds to build and deploy your app. 

Are you experiencing a different issue?

Rob

Rob

#63

Rob,

Thanks for a bit more clarity. It could be a variation/ additional problem. I had cleaned out keychain and even built new certificates/profiles etc.

I have gone and built direct to device and the app does not run/ but just flashes icon and then nothing. No console output at that stage, so I need to go and re-check via the XCode’s Organizer.

I had assumed this to be the same cause, so maybe not. I guess  I need to check filenames for mismatch case typing or fonts( I am sure I have done this before but will now check again…).

Thanks

Alec

#64

I recently too upgrade from Lion to OS Mavericks and Xcode. Same problems, mainly to do with some key signing issue. Cleared out Key chains and certs and all that and it hasn’t resolved anything. I’m with Alec on this, could a one time only daily build not be issued to at least starter subscribers to resolve this issue?

Evan

#65

Well,  have spent the day checking, changing, cleaning and any thing else I could think of or using suggestions  from throughout the forums on this subject (excluding Pro or Enterprise build downloads-as I still have Starter).

I can now run on the xcode simulator (whoopie)  but  the app fails still trying to get installed on to the device!.

iTunes does not show the proper icon (default develop icon shown)  and iTunes just sits there with ’ installing’ on the install button.

Sync shows copying, but never finishing install.

Using the Xcode organiser this shows that the code signature is missing/wrong.

So in my keenness what have I deleted? how//what do I re-create within the  keychain utility? I have tried many variations so I think the only route to restore the code signature is remove xcode and re-install. 

Would any one agree./disagree/ suggest another alternative?

I have tried recovery via the time machine but could not easily see what to select in the backup Libray/KeyChains folder and a little nervous I might corrupt something else.

Alec

#66

This is now getting really confusing! 

The problem is obviously something to do with the keychains and provisioning specification (sequence/definition) [a bug or lack of knowledge]

Now (down loading and re-installing  Xcode 5 after cleaning all relevant keys yet again  and then recreating them for about the fifth time) I cannot run the app now in the xcode simulator (the prior post time, the same app ran in the Xcode simulator OK!!!).

But now the app only  runs on the device !!!  First time for weeks. 

After installing Xcode I cleaned out all keys and certs in my name and started afresh and recreated dev and distribution provision etc. In the provisioning there is also two activated by Xcode (default and one ap id i created). Plus a distribution provisioning, a dev provisioning, each I created. The device build used a default Xcode team dist code sign. I have tried various profiles sign id.s in the simulator and all fail the same way.

The Xcode simulator fails with a message about an unspecified device family!.

[DEBUG] SDK Root: <DTiPhoneSimulatorSystemRoot 0x100600920> path=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk version=7.0 name=Simulator - iOS 7.0

[DEBUG] using device family unspecified

Alec

PS The concern here is sometimes it works one way and then another different way. So are the ‘solutions’ stated above ‘permanent’ or just the luck of the draw as I find it varies depending on what day it is!

#67

Help in understanding required here… Is this really due to the bug addressed by the latest daily build . Am I waisting my time or does all this help understand the bug???

I tried to load the exact same App onto my iPad and it failed to install.

The app installed ok on iPhone.

It will not run on Xcode simulator.

I am using provisioning profiles that include both devices

Curiously I have 3 DEV Provisioning Profiles defined and only 1 Distribution Provisioning Profiles. 

The extra 2 are

a) Xcode install created ???

b) MyApp Id I created - but not referenced

Xcode Wild Card is used in all Profiles thus far.

Profiles

  1. MyApp-Develop provisioning-Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active

  2. MyApp-Distribution provisioning-ad hoc -Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active

  1. IOS Team * -Dev Provisioning -Xcode: Wildcard AppID (*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active-MANAGED BY Xcode

4.IOS Team com.MyApp * -Dev Provisioning-MyApp(com.myapp.*)-1 Certificate-2 devices-Services none-expire Nov 2014-Active-MANAGED BY Xcode

All install ok on iPhone using iPhone Config Utility

However when installed on iPad only profile (1) and (2) are marked as vallid (3) and (4) are marked as not sign on the iPad only!

Therefore the Xcode organiser disabled the add application and it will not install. On iTunes I can add it but the iPad gives a msg unable to install and iTunes sits with ’ Installing’ displayed

I am on Xcode Version 5.0.1 (5A2053) 

iPhone IOS 7.03911B511)

iPad IOS 6.1.2 (10B146) -this is left back level -wife wont allow update but also good base to validate on older IOS levels 

is this the cause of failure to install now on iPad?

Alec

#68

Alec, I’m sorry you’re having all of these problems.  I wish there was some magic that would help. 

The Mavericks-XCode5 issue shows when you look at the Mac’s Console app.  Running 1202 you will get this error:

11/9/13 1:19:23.776 PM taskgated[13]: killed Orientation[pid 2489] because its use of the keychain-access-groups entitlement is not allowed (error code -67030)
 

This error occurs because pre-Mavericks, it was okay to run an app in the XCode simulator that was signed in a particular way.  Mavericks changed this behavior and this is what we fixed in the daily builds, so that on Mavericks we changed how we sign the apps for the Simulator the way Xcode expects it.

We also have noticed that the IPhone Configuration Utility (which many people use to install apps to their device) seems to have issues on Mavericks.  There is another thread about this.  Engineering points to these two links:

http://forums.macrumors.com/showthread.php?t=1662524
https://discussions.apple.com/message/23562825#23562825

For workarounds.  If you are using the iPhone Configuration Utility those links might help, but I highly recommend only using XCode’s Organizer to install things since it gives better error messages. 

Now your issues are something that is different.  There have been a few people after upgrading to Mavericks who had problems installing on device.  So far you’re the only person that cleaning out the provisioning profiles and key chain hasn’t fixed.   So let me try to summarize where you are:

1.  You cannot build for the XCode simulator with 1202 on Mavericks.   This is expected.

2.  You can build for an iOS 7 iPhone with no difficulties.

3.  You cannot build for an iOS 6 iPad.

Has the iPad been plugged into the Mac and from XCode’s organizer and you’ve told it to use that iPad for development?

Have you tried to create an AdHoc Distribution profile specifically for your app?  I’ve never had a lot of luck using the Team profile.  Making sure you have your devices in there.  Download the profile and manually move it to ~/Library/MobileDevice/Provisioning\ Profiles/

Restart Corona SDK (Oh side note, after cleaning up all your keys and such, did you reboot?) and try building with the specific provisioning profile for your app?

Rob

#69

“I wish there was some magic that would help.” from Mr Miracle !

Well you certainly provide some here…

Following your guidance and using the Xcode organiser instead of the IPhone Configuration Utility I am there (well almost).

I now have the app running on the iPad and the iPhone.

I am still no where near confident with these certificate/profile/ distribution/dev/team methodology.

Many reasons…

The attached image capture shows of the three I created two failed. So the only active is the xcode team and my own distrubition profile.

I used my own distribution profile which is now on the working devices.

I tried the Xcode simulator yet again but the error  I see is not the error you gave but is still related to signatures

EXC_CRASH (Code Signature Invalid)

The app loads into the simulator and the icon can be seen in the window but crashes with the above error.

Previous profiling included a request to use my certificate “AS Cockle” keychain click allow always etc

This time it just requested <key> keychain. I have no idea why.

So I need to go and find a dark corner and  study this certification process  a lot more because it is all smoke and mirrors to me so far…

Anyway thank you Rob for the continued feedback and guidance.

Alec

#70

The whole certificate/keychain stuff is complex enough that if you don’t do it often enough you never get comfortable with it. 

#71

Here’s some reading I have found… just in case others may need some referencing, or maybe  can point to other ‘training’ material.

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/Troubleshooting/Troubleshooting.html

http://fovea.cc/blog/index.php/ios-developer-certificates-provisioning-profiles-application-id/

http://ipad.about.com/od/iPad-App-Dev/a/How-To-Renew-Your-Apple-Developers-Certificate-And-Provisioning-Profiles.htm

#72

I am still having the problem running the app on the simulator. It works on the device. I’m using build 1256. Has this problem been resolved. When I try to run it, the simulator just hangs up.

#73

It was fixed in 1248.

Can you bring up the Console app and see what errors you are getting?

#74

corona doesn’t let me choose a different SDK to compile with.

Is there any way to do so?

#75

There should be some messages in the Console log.  For the Xcode simulator that is in the “Console” app.  What does it say there?

#76

its use of the keychain access groups entitlement is not allowed

I already deleted the provisioning profiles and created new ones.

no difference in the simulator

#77

don’t know what I’m doing wrong. my bundle identifiere is like com.company.appname.

even with a wildcard it doesn’t work…

desperate :frowning:

#78

the weird thing is that it’s working on my real device 3gs ios 6.1 with new profiles.

but the ios7 simulator doesn’t take it…

something to do with info.plist?

#79

It’s possible.  Do you have an iOS 7 device to test it on?  Is this a landscape app calling GameCenter or things like the camera or popups?

Can you post your build.settings

#80

build.settings:

-- Supported values for orientation: -- portrait, portraitUpsideDown, landscapeLeft, landscapeRight settings = { orientation = { default = "portrait", supported = { "portrait", } }, iphone = { plist = { --UIStatusBarHidden = false, --UIPrerenderedIcon = true, -- set to false for "shine" overlay --UIApplicationExitsOnSuspend = true, -- uncomment to quit app on suspend --[[-- iOS app URL schemes: CFBundleURLTypes = { { } } --]] } }, }

app:

local mytext = display.newText("hello",0,0,"Arial",20) mytext.x = display.contentWidth / 2 mytext.y = display.contentHeight / 2