iOS enterprise distributed app terminates without any error log

1k Views Asked by At

I have very weird distribution scenario with the iOS app.

  • App works normally in simulator
  • App works normally on the device with developer profile (and corresponding bundle id domain.product)

When downloaded from testFairy service with valid enterprise provisioning profile app and bundle id (in form domain.beta.product) app:

  • Installs without error
  • Shows lunch screen and terminates immediately
  • When I connect device and check logs through Xcode -> Devices -> Show log I don't see any today's crashes, like no error happened. (this confuses me the most)

This happens on 2/2 iPhone devices that tried to run the app.

Some other infos that could maybe ring a bell to someone: - App uses Core Data - App uses TestFairy SDK (but it was the same without it) - target is iOS 7.0, base SDK is Latest iOS(iOS 8.1) - provisioning profile is set to that Enerprise Profile and signing identity is set to corresponding certs for both debug and release. - I've removed armv7 from Targets-> Info -> Required Device capabilities as suggested on some stack overflow solutions.

Anyone experienced similar problem? What could be the cause?

1

There are 1 best solutions below

6
On BEST ANSWER

I work for TestFairy, I think I can assist.

Few points:

  1. TestFairy's distribution does not alter the IPA in any way.

  2. When using an enterprise profile, you need to sign using (TEAM.domain.company.app) in your application-identifier. iOS 8 shouldn't let you install if the identifier does not include the TEAM.

  3. If the app crashes immediately (with or without the Default splash screen,) it might be because you're out of memory. Does rebooting fix the problem?

  4. Can you please paste all the logs from right before the launch, till the app exits? you can attach and send to TestFairy's support (via Contact page.) That would be helpful. Also, if you're interested, you can email support with your username and link to build, and they can try installing it on their devices and let you know what the problem was.