TestFlight corrupting app's executable. App failing to launch only when installed from TestFlight

App Store Distribution & Marketing TestFlight
Smithers OP
Created Sep ’15
Replies 57
Boosts 0
Views 22k
Participants 15

I've got an app that runs perfectly well when run from the debugger. When uploading to TestFlight it goes through fine and am able to download using the Testflight app.


However, the moment I launch the app, it displays the splash for 20 or so seconds before closing. No crash report as such is generated but was able to extra a '.ips.beta' file from CrashReporter and it looks like this:


Exception Type: 00000020 Exception Codes: 0x000000008badf00d Exception Note: SIMULATED (this is NOT a crash) Highlighted by Thread: 0 Application Specific Information: com.some.app failed to launch after 20.00s (launchIntent: foreground-interactive) Elapsed total CPU time (seconds): 30.760 (user 30.760, system 0.000), 77% CPU Elapsed application CPU time (seconds): 0.080, 0% CPU Filtered syslog: None found Thread 0 name: Dispatch queue: com.apple.libdispatch-manager Thread 0: 0 libsystem_kernel.dylib 0x3805e3c0 0x38048000 + 91072 1 libdispatch.dylib 0x37f749a6 0x37f64000 + 68006 2 libdispatch.dylib 0x37f66b2e 0x37f64000 + 11054 Thread 1 name: Dispatch queue: com.apple.root.default-qos.overcommit Thread 1: 0 libsystem_kernel.dylib 0x3805d54c 0x38048000 + 87372 1 libdispatch.dylib 0x37f727f0 0x37f64000 + 59376 2 libdispatch.dylib 0x37f727da 0x37f64000 + 59354


I can see it says '8 bad food' and that it's closing before it's able to initialize - but - it produces no statements in the console, and it's running absolutely perfectly on a device when run using the Debugger or even when I install a Adhoc copy (manually from Xcode or using Fabric). Why would it fail only when coming from TestFlight? How do I go about debugging this when it's working fine otherwise. It's failing on every device that it otherwise is able to run using the debugger.

I have even tried putting a NSLog statement in the main() method before the delegate gets passed control - that doesn't get logged to the console (I'm using the Device Manager to see raw device logs). Furthermore, every time I launch the app, I see this before the app closes:


AppName[640] : Bogus event received by listener connection: { count = 1, contents = "XPCErrorDescription" => { length = 18, contents = "Connection invalid" }

What does this mean?


UPDATE: Please see my comments below - it's not the app, it's TestFlight.

Replies  57
Boosts  0
Views  22k
Participants  15
OP
Apple
Sep ’15

The fix for this issue should be in place now, so the workaround is no longer necessary. Please let us know if you continue to see any problems like this.

0
Smithers OP
Sep ’15

Thanks - dare we test *that* again!


What's really annoying, and possibly a complete time waster, is this 'Processing' state that we get into! It lingers for hours and hours! Each time we upload a build it could be anything between 30 minutes to 2 days. I uploaded a build this morning and after 8 hours I've uploaded another one, which is now an hour in and still waiting.


This is not only unproductive, it's wasting developers' time to the point I'm actually considering abandoning developing for this slow and buggy environment!


Please, put tvOS on hold for like a week and concentrate all efforts on fixing iOS 9, iTunesConnect and TestFlight bugs. You know there are too many to ignore. How on earth would developers work on a new platform when they can't get out existing versions out to the store?

0
jeeeyul OP
Sep ’15

What excatly name means? Is it bundle name?

0
OP
Apple
Oct ’15

The issue has now been fixed so you don't need to change any names.

0
kozachek_julia OP
Oct ’15

No, it's not fixed. Trying to fix it all day long. Reinstalled OS X, XCode. Trying to rename $(EXECUTABLE_NAME) but another error comes out.

Please, tell me what exectly should I rename.

0
OP
Apple
Oct ’15

If you're still seeing a problem, then it is a different issue and renaming things isn't going to help.


You can locally go through some parts of the process by exporting for ad hoc distribution. If you haven't already tried that, I suggest you try that and see if you run into problems. If so, it may be easier to work out what's wrong when it fails on your machine.


If you're still stuck, you can file a bug report.

0
kozachek_julia OP
Oct ’15

I tried Ad Hoc. Everything is fine. IPA was successfully installed on the device.

So, what should I do to file a bug report?

0
OP
Apple
Oct ’15

http://bugreport.apple.com


Please provide as much information as possible about the problem that you're having.

0
kozachek_julia OP
Oct ’15

I have posted a bug report with steps to reproduce.

Bug report number is 22961224.

I hope it will be fixed soon. Also I hope Apple will give me free expedited review attempts 🙂

0
simplesimon OP
Oct ’15

I also have this problem, which I've filed with report 22963693.


I haven't re-submitted my app, but do you think I should?

0
red_dog OP
Nov ’15

same here. Everything works fine in adhoc and Testflight, but apple rejects app for not launching.

0
Technology Evangelist OP
Apple
Nov ’15

red_dog - The issue discussed in this thread was resolved in early October. If you are seeing a new issue, please do contact iTunes Connect for support.

0
TestFlight corrupting app's executable. App failing to launch only when installed from TestFlight
First post date Last post date
 
 
Q