App Crashing On Launch

Support
1

Hello everyone.

I seem to be having an issue with my automation after upgrading my device to iOS 9.2.

I had to reload my Provisioning Profiles on it. When running my scripts I was seeing that it was launching the app on the device, however it would crash quickly.

When I manually launch the app I get the same outcome and the following in the logs. I was hoping some of the experts here might have some idea on what the issue could be.

Thanks in Advance.

Jan  8 10:46:00 iPod-touch SpringBoard[48] <Error>:  SecTrustEvaluate  [leaf IssuerCommonName SubjectCommonName]
Jan  8 10:46:00 iPod-touch SpringBoard[48] <Notice>: MIS: Using empty blacklist.
Jan  8 10:46:00 iPod-touch SpringBoard[48] <Error>:  SecTrustEvaluate  [leaf IssuerCommonName SubjectCommonName]
Jan  8 10:46:00 iPod-touch SpringBoard[48] <Notice>: MIS: Using empty blacklist.
Jan  8 10:46:01 iPod-touch kernel[0] <Notice>: xpcproxy[252] Container: /private/var/mobile/Containers/Data/Application/53438E27-6966-4ED1-805E-88603DC24279 (sandbox)
Jan  8 10:46:02 iPod-touch SpringBoard[48] <Warning>: BSXPCMessage received error for message: Connection invalid
Jan  8 10:46:02 iPod-touch SpringBoard[48] <Warning>: BSXPCMessage received error for message: Connection invalid
Jan  8 10:46:02 iPod-touch SpringBoard[48] <Warning>: HW kbd: Failed to set (null) as keyboard focus
Jan  8 10:46:02 iPod-touch com.apple.xpc.launchd[1] (UIKitApplication:com.myapplication.lead.test[0x66f5][252]) <Notice>: Service exited due to signal: Bus error: 10
Jan  8 10:46:02 iPod-touch ReportCrash[251] <Error>: assertion failed: 13C75: libsystem_trace.dylib + 15927 [0AE31C11-AAE7-301F-9B1B-143B1A2C764C]: 0x0
Jan  8 10:46:02 iPod-touch Unknown[251] <Error>: 
Jan  8 10:46:02 iPod-touch ReportCrash[251] <Warning>: os_activity_diagnostic_for_pid() failed!
Jan  8 10:46:02 iPod-touch ReportCrash[251] <Notice>: Formulating report for corpse[252] LeadCap
Jan  8 10:46:02 iPod-touch SpringBoard[48] <Warning>: Application 'UIKitApplication:com.myapplication.lead.test[0x66f5]' crashed.
Jan  8 10:46:02 iPod-touch UserEventAgent[23] <Warning>: 385452936457: id=com.myapplication.lead.test pid=252, state=0
Jan  8 10:46:02 iPod-touch ReportCrash[251] <Warning>: saved type '109_LeadCap' report (3 of max 25) as /var/mobile/Library/Logs/CrashReporter/LeadCap_2016-01-08-104602_iPod-touch.ips
2

If you are the QA Engineer you need to file a P0 bug immediately. Your app does not work with iOS 9.2.

If you are the Developer you need to fix the app so that it will work with iOS 9.2.

Because you are able to reproduce manually, it’s definitely not an Appium issue.

3

Hey @wreed

Thanks for the response. I am actually the QE responsible for this application.
Whats odd is that other builds from our build server from this same branch are working. We have a specific job setup for automation, due to the signing we need to do of the app.

I know this may not be an Appium issue directly, it is something I figured some members in here may have come across and have some insight on.

4

That’s interesting. It could be a certificate issue. Regardless I would file the bug immediately as your tests are blocked.

I did look at the log you posted but Apps can differ so much it’s hard to say from that what is happening. The ‘connection invalid’ makes me think your backend might have changed in some way (maybe a staging environment) but I don’t know if your app talks to a back end (not all do). Filing the bug is my best advice right now. Make sure the Developers know that you are facing this problem–they may actually know the answer.

5

Its definitely a bit of a stumper for sure.

I have talked to some of our iOS devs and they are not quite sure either. I am going to keep working with them to see if we can figure it out. Thought I would see if anyone here may have some insights.

This app doesn’t talk to our BE at all until login, this is just upon initial load. Very confusing :slightly_smiling:

Thanks again @wreed

6

Hi Trent,

Did you even figure this out? I’m having the same problem but I’m stumped! Any help would be much appreciated.

7

Hi Martin,

So what ended up being the root issue for me in this case was that something changed in the cert. So on my build server (Jenkins) I needed to regen the cert that I was using for this to ensure it was signing it correctly.
Hope that helps and good luck.