iOS crash at startup

[codenameone]

Original issue 714 created by codenameone on 2013-05-18T23:56:00.000Z:

I have just released the second version of my iOS app. Some maintenance and a couple of new features, nothing that major.

I have one user that ran the first release without a problem. After installing second release it displays the splash screen and crashes. My app never starts. Just the one user.

She has tried deleting the old app, reinstalling, rebooting the device. Nothing helps.

She is using an original iPad running iOS 5.1.1. She sent me the crash log included below. Does this show anything relevant.

I don't know how to debug this.

Thanks

Had to attach the log as a file, too long

[codenameone]

Comment #1 originally posted by codenameone on 2013-05-19T04:36:34.000Z:

I just tried your latest version on an iPad II and it worked just fine.
I'm guessing that this isn't the first iPad but rather iPad III. There is a regression related to iPad III with OS 5.1 which should be resolved by upgrading to OS 6.0 on the device.

[codenameone]

Comment #2 originally posted by codenameone on 2013-05-19T14:40:07.000Z:

It is an original iPad, iOS 5.1.1 is the last release for that device.

[codenameone]

Comment #3 originally posted by codenameone on 2013-05-19T18:16:02.000Z:

Unfortunately we don't have such a device and its hard to debug things like that remotely (Apples simulators are no good). Do you know when you built the last version that you know was good?
I'll try and find someone who still has an iPad 1 device.

[codenameone]

Comment #4 originally posted by codenameone on 2013-05-19T19:20:24.000Z:

The first release was submitted to Apple on March 11th 2013, it was probably built the same day or shortly before. This worked.

The second release was submitted to Apple on May 8th 2013, this one fails on this particular iPad.

I have an old iPod 3G that is also running 5.1.1. Unfortunately I am traveling and don't have that device with me. I will try it on this when I can. I don't know if the problem is 5.1.5 or the original iPad or a combination of both. If you have an older device stuck at 5.1.5 can you test on it.

[codenameone]

Comment #5 originally posted by codenameone on 2013-05-19T19:26:19.000Z:

I contacted a friend who might be able to get one but it isn't his device so that might be difficult. I'll try to review commits in this date range.
Did you add any features that weren't there before? That might rely on something new?

[codenameone]

Comment #6 originally posted by codenameone on 2013-05-21T00:20:07.000Z:

I have been through the list of chsnges and I don't see anything that would require something new. There are some enhancements but they are all based on existing functionality.

I am trying to get the user back to the old version via iTunes. If we can do that and get the old version to run again it will prove that it wasn't a change her end.

Then I will do two adhoc build, the original release and the new release and will have her install them. Hopefully the results1 will point us in a direction.

[codenameone]

Comment #7 originally posted by codenameone on 2013-05-21T09:56:59.000Z:

I just tried our existing code on the older simulator for 5.1 (unfortunately still no device) and it seemed to work.
Will you be building an App using XCode? If so you can include symbol information into an app to get a log that isn't obfuscated. It will be pretty huge but it might allow debugging the crash.

[codenameone]

Comment #8 originally posted by codenameone on 2013-05-22T08:08:03.000Z:

We have encountered a very similar crash with our app on iPad 1 running iOS 5.1.1. It works fine on iPad 2, and it did work fine on iPad 1 too but suddenly started to crash at the very begenning when showing the splash screen. The crash log is very similar to this one, this part being identical:
"Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000009c"

Since then it has been impossible to run it again on iPad 1. Rebooting and reinstalling hasn't helped either.

[codenameone]

Comment #9 originally posted by codenameone on 2013-05-22T16:52:55.000Z:

khash777 do you still have the device?
Can I send you a special build of KitchenSink for testing?

[codenameone]

Comment #10 originally posted by codenameone on 2013-05-23T07:54:01.000Z:

Yes we have the device so feel free to send the build and I'll be happy to help you.

[codenameone]

Comment #11 originally posted by codenameone on 2013-05-23T08:47:56.000Z:

Thanks,
unless your device is jailbroken I will need a UDID for it.

[codenameone]

Comment #12 originally posted by codenameone on 2013-05-23T10:42:06.000Z:

the UDID is: ac3b933eca0270467b329035c4d16ca8b6b85bf4

[codenameone]

Comment #13 originally posted by codenameone on 2013-05-23T11:35:28.000Z:

Thanks, can you try installing this:
http://codename-one.appspot.com/getData?m=result&i=10157205&b=add2ac10-1b81-442b-a38b-853acf80bff3&n=KitchenSink.ipa

Install link here: https://codename-one.appspot.com/ota.jsp?id=10157205&t=i

If it will fail on startup we "should" have readable logs (hopefully).

[codenameone]

Comment #14 originally posted by codenameone on 2013-05-23T11:45:34.000Z:

I get this error message when trying to install it via your link:
"Unable to Download Application. "debug_iphone" could not be installed at this time."

[codenameone]

Comment #15 originally posted by codenameone on 2013-05-23T12:05:23.000Z:

Sorry about that, wrong provisioning profile. https://codename-one.appspot.com/ota.jsp?id=10139352&t=i
Or IPA link: http://codename-one.appspot.com/getData?m=result&i=10139352&b=3f8363e9-7c4d-4359-9a22-fbf4999967c0&n=KitchenSink.ipa
Should work fine now (hopefully).

[codenameone]

Comment #16 originally posted by codenameone on 2013-05-23T12:32:40.000Z:

Still getting the same error message. Has it something to do with certificates maybe?

[codenameone]

Comment #17 originally posted by codenameone on 2013-05-23T13:49:57.000Z:

I'm a bit stumped, since I built locally I deleted stuff from xcode and rebuilt. If this doesn't solve the issue then I'm not sure what could be the cause.
http://codename-one.appspot.com/getData?m=result&i=10317004&b=48e970a4-7a6b-4931-8b84-666c8ad773eb&n=KitchenSink.ipa
https://codename-one.appspot.com/ota.jsp?id=10317004&t=i

[codenameone]

Comment #18 originally posted by codenameone on 2013-05-23T14:22:52.000Z:

Yeah still can't install getting the same error message. I've got help from an ios developer to clear all provisioning profiles on the device and try to install it running the console in xCode, this is the output which might give you some clues.

[codenameone]

Comment #19 originally posted by codenameone on 2013-05-23T17:11:16.000Z:

Thanks, I think its because push notification is turned on but not in the provisioning profile. Try this http://codename-one.appspot.com/getData?m=result&i=10317211&b=57296734-acef-47e7-9922-09d7d11a1358&n=KitchenSink.ipa
https://codename-one.appspot.com/ota.jsp?id=10317211&t=i

[codenameone]

Comment #20 originally posted by codenameone on 2013-05-24T08:10:48.000Z:

Heeey it worked! :D
So I could install and run it and it didn't crash. What to do now?

[codenameone]

Comment #21 originally posted by codenameone on 2013-05-24T08:24:53.000Z:

Lets try this http://codename-one.appspot.com/getData?m=result&i=10343281&b=1721ae7d-d923-431a-aba4-5a9f1897fbf8&n=KitchenSink.ipa
https://codename-one.appspot.com/ota.jsp?id=10343281&t=i

They were built on the build server (not locally) without the symbol information.
If this fails to install I will try building on the servers with the symbol information (assuming a server config issue).

[codenameone]

Comment #22 originally posted by codenameone on 2013-05-24T08:50:57.000Z:

This one also installs fine and doesn't crash when running.

[codenameone]

Comment #23 originally posted by codenameone on 2013-05-24T08:54:12.000Z:

OK, in this case can you check that Mark's readerware application from the app store (its free) crashes?
If it does then Mark, can you please send a debug build with an updated provisioning profile that includes khash777 and includes the build argument: ios.no_strip=true

Thanks.

[codenameone]

Comment #24 originally posted by codenameone on 2013-05-24T09:07:16.000Z:

Ok I installed "Readerware 3 (Books)" and ran it and it didn't crash. He said that version 2 crashed though, not sure if that's relevant or not.

[codenameone]

Comment #25 originally posted by codenameone on 2013-05-24T11:52:29.000Z:

Mark?
I guess we should have started with that test first...

[codenameone]

Comment #26 originally posted by codenameone on 2013-05-24T15:02:34.000Z:

It's Martin :-)

I am not sure what you are asking.

The problem I had was this one user who had installed the initial release and it worked fine. I updated the product, the one currently in the app store, and it crashed on startup, just this one user. She had an original iPad running 5.1.1 which may or may not have been relevant. So that was the problem I was reporting. I still have not had any other reports of this.

As my app runs fine on khash777's iPad 1 then maybe it is nothing to do with the device.

What about your problem khash777? You still have an app that will not run on it right?

[codenameone]

Comment #27 originally posted by codenameone on 2013-05-24T15:22:19.000Z:

Martin:
yes that's right, our app still crashes on iPad 1. Since the above test app that Shai made for me to test doesn't crash I was hoping that would help us finding the problem.

[codenameone]

Comment #28 originally posted by codenameone on 2013-05-24T19:38:07.000Z:

Sorry Martin, long days ;-)

khash777 does your app work on other iOS devices?

[codenameone]

Comment #29 originally posted by codenameone on 2013-05-28T07:55:47.000Z:

Yes it does work on iPad 2 (ios 6.1.3) and iPhone 4s.

[codenameone]

Comment #30 originally posted by codenameone on 2013-05-30T23:09:05.000Z:

I made a new debug build for her device. Still crashing, log attached.

[codenameone]

Comment #31 originally posted by codenameone on 2013-05-31T06:01:47.000Z:

Did you define ios.no_strip=true in this build? If so it doesn't seem to be working.

[codenameone]

Comment #32 originally posted by codenameone on 2013-05-31T13:04:24.000Z:

Sorry missed that, will do a new build.

[codenameone]

Comment #33 originally posted by codenameone on 2013-05-31T13:17:44.000Z:

Is ios.no_strip=true just a build hint to the server? It doesn't seem to make that much difference to the resulting ipa file. Just wanted to check before I involve the user.

[codenameone]

Comment #34 originally posted by codenameone on 2013-05-31T13:23:57.000Z:

yes. I'm afraid I didn't have a chance to properly test it out so I'm not sure if it works. I'm assuming you are sending debug builds, right?
it will only work on those.

[codenameone]

Comment #35 originally posted by codenameone on 2013-05-31T21:59:27.000Z:

Here is the log with ios.no_strip=true.

It doesn't look any different to me though

[codenameone]

Comment #36 originally posted by codenameone on 2013-06-01T04:34:28.000Z:

Damn, I think the no strip didn't work. I'll test this and get back to you.

[codenameone]

Comment #37 originally posted by codenameone on 2013-06-01T13:06:22.000Z:

I just tried crashing my own app and I don't get symbol information either. I looked at the build process and we seem to be doing everything correctly but its still not working. Unfortunately trying to figure out how to do these things through code is a very long process of trial/error and guesswork.
The only thing I can think of is if you can extract a small test case and check that it crashes on the device. If so send it to me and I will build it manually in XCode and archive it, then we can send that test case out and get a "proper" error log.

[codenameone]

Comment #38 originally posted by codenameone on 2013-06-05T19:21:23.000Z:

It looks like any CodenameOne app crashes on her system now so something seems to have changed in the build process since my original release. I rebuilt the original release and it now crashes. I sent her the basic skeleton app you create when I select a new CodenameOne Project with the Hello World (Manual) theme. It displays the screen briefly and then crashes. Log attached.

Source code for test app attached, the class name is set for my provisioning certificates. I use some iOS build properties and I included them in my test build so they might be relevant:

ios.project_type=ios
ios.application_exits=false
ios.fileSharingEnabled=true

If you are going to build an app for her, I think you will need her UDID d64dd616dae9223224e3b6dc88b982286d27f7b3

[codenameone]

Comment #39 originally posted by codenameone on 2013-06-05T19:37:45.000Z:

Can you also include my UDID in any test build, that way I can verify that it installs before we involve the customer. Thanks

cb203cb5c90a44ce8869c24f4c51cd10d80281cc

[codenameone]

Comment #40 originally posted by codenameone on 2013-06-08T09:04:42.000Z:

This is an archived kitchen sink IPA which means that even if the crash log will seem obfuscated to you I still should be able to see it properly in xcode. I'm using Dropbox since google code only supports 10mb of attachments: https://dl.dropboxusercontent.com/u/57067724/cn1/KitchenSink.ipa

[codenameone]

Comment #41 originally posted by codenameone on 2013-06-08T18:31:14.000Z:

Thanks

I used iTunes to install it here and everything went fine. I have forwarded it to my user and will post as soon as I hear back.

[codenameone]

Comment #42 originally posted by codenameone on 2013-06-10T00:18:48.000Z:

Here you go

[codenameone]

Comment #43 originally posted by codenameone on 2013-06-10T04:43:17.000Z:

Thanks, I'm looking into it, just for reference this is the deobfuscated stack.

[codenameone]

Comment #44 originally posted by codenameone on 2013-06-10T07:45:40.000Z:

I made a fix for this, it should be on the server now.
Thanks for all the work on this!

[codenameone]

Comment #45 originally posted by codenameone on 2013-06-10T20:34:22.000Z:

I did a new build for my customer and she confirms it is now working.

Thank you!

[codenameone]

Comment #46 originally posted by codenameone on 2013-06-11T05:04:06.000Z:

Great!

[codenameone]

Comment #47 originally posted by codenameone on 2013-06-12T08:54:35.000Z:

Shai: I can't find the fix on the server, the latest version available through Elipse seems to be 1.0.0.201305291835. Can you please direct me how to get this fix?

[codenameone]

Comment #48 originally posted by codenameone on 2013-06-12T08:56:39.000Z:

Just send a build. The fix is seamless.
If it doesn't solve your issue then you have a different issue.