App crash when after update app. from App Store

Solar2D Native builds
#1

Hi all,

I have some issue when after update app from App Store.

The issue happened since I registered the last update recently.

Unfortunately, I could not remember last version of Corona SDK.

Same happens all Corona SDK from Build 2013.999 to 2013.1076.

Especially it happens only in iOS platform.

Here are the logs from iPhone console:

Apr 19 13:33:53 iPhone5-seobiseugaebalbu kernel[0] \<Debug\>: launchd[980] Builtin profile: container (sandbox) Apr 19 13:33:53 iPhone5-seobiseugaebalbu ReportCrash[981] \<Error\>: libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary Apr 19 13:33:54 iPhone5-seobiseugaebalbu ReportCrash[981] \<Notice\>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/littlephonicsReview\_2013-04-19-133353\_iPhone5-seobiseugaebalbu.plist using uid: 0 gid: 0, synthetic\_euid: 501 egid: 0 &nbsp;

Also I attach the crash log file of iOS devices.

https://www.dropbox.com/s/mz8jxqkbd2llo2d/littlephonicsReview%20%2013.%204.%2019.1-33.crash.zip

#2

Can it be possible to find out which version of Corona SDK I used from app. binary?

Plz help…!

#3

coronaent1 - Can you give us more info on the problem you are seeing? Do you mean that your app is now crashing on iOS devices?

#4

DavidRangel - Yes, below is additional information. 

  1. Enterprise Info
     - account :  coronaent1
     - Enterprise Version : 1076 (or 2013.01 late Version)
     - Code Area (or Module) : corona Enterprise module  + ios native plugin code
     - Build type : Builds and Release on Xcode  (Version : 4.6 (4H127))

  2. More Info

 - Yes, just ios device.

 - First,  My App is released to appstore. there is no problem. But when my App has been updated, that was not working  with crashed and log(which is upper posted)

 - There is no problem before enterprise sdk version of 2013.999

We can’t additional updating for ours app until this problem will be solved.

Please tell or let me know additional info or advice or tech of corona enterprise to solve it

Thansks.

#5

Is the crash report from Apple? Can you reproduce this on your own devices?

Do you have the DSYM for the app update? You can symbolicate the crash log if you have the dSYM — based on the stack, it looks like your app is restoring some state?

Finally, how did you generate the IPA? There is a bug where Xcode’s archive feature (under the Product->Archive menu) does not work properly with CoronaEnterprise. So the workaround is to generate an IPA manually from a Release build.

#6

Walter, if the distribution build works and the Archive exports properly. Will the bug still affect the binary? Or is it purely on export only?

I just submitted a build using the Archive feature. It would be very VERY bad if we released to a broken binary.

Thanks.

#7

Can it be possible to find out which version of Corona SDK I used from app. binary?

Plz help…!

#8

@MochiBits, the bug is only if the Archive does not export properly (i.e. you click the “Archive” menu). If you click the “Build” menu item, everything works fine.

I’m surprised we’ve only gotten 1 bug so far so my suspicion is that this is a change in the latest Xcode update.

We’ve got a workaround coming in the next daily build (1096 or higher) in case you really want to use “Archive”.

#9

I did click the Archive button, which built the code, but everyting submitted to iTunes Connect ok.

Does it corrupt the binary? 

Or if everything went through ok, is it fine?

#10

The binary isn’t corrupted per se. The .app bundle is just not packaged correctly. 

When there were problems, it did not look like the app would actually launch, so the app reviewer should complain back. Also, we saw things like extra “.lu” files lying around in the folder — that’s a tell-tale sign that something weird happened with the Archive.

#11

I see. Just wanted to make sure.

Thanks.

#12

coronaent1 - Can you give us more info on the problem you are seeing? Do you mean that your app is now crashing on iOS devices?

#13

DavidRangel - Yes, below is additional information. 

  1. Enterprise Info
     - account :  coronaent1
     - Enterprise Version : 1076 (or 2013.01 late Version)
     - Code Area (or Module) : corona Enterprise module  + ios native plugin code
     - Build type : Builds and Release on Xcode  (Version : 4.6 (4H127))

  2. More Info

 - Yes, just ios device.

 - First,  My App is released to appstore. there is no problem. But when my App has been updated, that was not working  with crashed and log(which is upper posted)

 - There is no problem before enterprise sdk version of 2013.999

We can’t additional updating for ours app until this problem will be solved.

Please tell or let me know additional info or advice or tech of corona enterprise to solve it

Thansks.

#14

Is the crash report from Apple? Can you reproduce this on your own devices?

Do you have the DSYM for the app update? You can symbolicate the crash log if you have the dSYM — based on the stack, it looks like your app is restoring some state?

Finally, how did you generate the IPA? There is a bug where Xcode’s archive feature (under the Product->Archive menu) does not work properly with CoronaEnterprise. So the workaround is to generate an IPA manually from a Release build.

#15

Walter, if the distribution build works and the Archive exports properly. Will the bug still affect the binary? Or is it purely on export only?

I just submitted a build using the Archive feature. It would be very VERY bad if we released to a broken binary.

Thanks.

#16

@MochiBits, the bug is only if the Archive does not export properly (i.e. you click the “Archive” menu). If you click the “Build” menu item, everything works fine.

I’m surprised we’ve only gotten 1 bug so far so my suspicion is that this is a change in the latest Xcode update.

We’ve got a workaround coming in the next daily build (1096 or higher) in case you really want to use “Archive”.

#17

I did click the Archive button, which built the code, but everyting submitted to iTunes Connect ok.

Does it corrupt the binary? 

Or if everything went through ok, is it fine?

#18

The binary isn’t corrupted per se. The .app bundle is just not packaged correctly. 

When there were problems, it did not look like the app would actually launch, so the app reviewer should complain back. Also, we saw things like extra “.lu” files lying around in the folder — that’s a tell-tale sign that something weird happened with the Archive.

#19

I see. Just wanted to make sure.

Thanks.

#20

Hi there, 

I got this same error, but I’m not using the Enterprise version, so I guess there is something else taking place here than the “Archive” thing mentioned above. Any ideas, anybody ?

Emerson