OK, thank you. So I do have an Enterprise account; on the device I installed the app by hand I do have the trust setting and its trusted. The app will launch and exit and just sit in the background. To give you a scale we deploy the application via MDM to our fleet which is less than 10,000. We have been seeing devices more regularly where the app launches and exist right after seeing the splash screen. This also seems to occur on newly enrolled devices. FYI, the devices are all supervised. One last data point. If I sign the app as AdHoc using another non-enterprise developer account the app installs (did not use MDM) and launches and runs fine.

Should I open a support case for this?

So, I decided to check another one of my applications on one of these devices and it wont launch either. Could the device(s) be missing a certificate?

The closest thing I could find was one line in console log. Bootstrapping failed for <FBApplicationProcess: 0xca45dd380; app<got.lnt.MyDevice>:<invalid>> with error: <NSError: 0xc9ea77b10; domain: RBSRequestErrorDomain; code: 5; "Launch failed."> { NSUnderlyingError = <NSError: 0xc9ea76700; domain: NSPOSIXErrorDomain; code: 85> { NSLocalizedDescription = Launchd job spawn failed; }; }

I would love to post a crash log, but it does not generate one.

Its an in house app for new employees. We want them to fill out the app before doing anything on the system.