Can't upload Xcode 6.3b2 app to Testflight: "Invalid Segment Alignment"

Originator:ajpike
Number:rdar://19928802 Date Originated:23-Feb-2015 03:16 PM
Status:Open Resolved:
Product:iOS SDK Product Version:Xcode 6.3b2
Classification:Serious Bug Reproducible:Always
 
Summary:
I have a Swift app in Xcode 6.3b2, but when I try to submit to Testflight using Application Loader, it fails with many errors of the form ‘ERROR ITMS-90209: “Invalid Segment Alignment. The app binary at ‘spies.app/Frameworks/libswiftCore.dylib’ does not have proper segment alignment. Try rebuilding the app with the latest Xcode version.”’

Steps to Reproduce:
1. Open attached project.
2. Archive app.
3. Hit “Export” to save the app to an .ipa (can’t use Submit to App Store flow because of rdar://19809552)
4. Choose “Save for iOS App Store Deployment” and save to file 
5. Open Application Loader 3.0 (620)
6. Hit Deliver your App, find the file, hit Next.

Expected Results:
Application Loader submits the build to iTunes Connect for Testflight testing.

Actual Results:
Application Loader displays 18 errors like this:

ERROR ITMS-90209: “Invalid Segment Alignment. The app binary at ‘spies.app/Frameworks/libswiftCore.dylib’ does not have proper segment alignment. Try rebuilding the app with the latest Xcode version.”

There is one error for each Swift dylib - CoreAudio, CoreGraphics, Darwin, UIKit, etc.

Regression:
Submission to Testflight worked fine in Xcode 6.1. It’s non-trivial to re-test Xcode 6.1 with this project since it doesn’t build anymore with all our Swift 1.2 changes.

Notes:
I have seen other people on Stack Overflow and the Dev Forums hitting this issue once working around rdar://19809552. I’ve filed this as a separate issue because it doesn’t seem like it would have the same root cause as rdar://19809552.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!