Several ITMS Errors submitting iOS 9/watchOS 2 beta app to TestFlight

I'm having a whole host of issues come back from iTunes Connect when trying to upload an iOS 9 app with watchOS 2 app and both Watch and CocoaTouch frameworks embedded. I've waited a week before posting this in case it was an issue with the iTunes Connect server.


For the iOS 9 app, I received ITMS-90086: Missing 64-bit support. "Architectures" is set to $(ARCHS_STANDARD) (armv7, arm64) and "Build Active Architecture Only" set to NO for Release.


For the Watch Framework, I receive ITMS-90087: "Unsupported archtectures...[armv7k]." "Architectures" is set to $(ARCHS_STANDARD) (armv7k) and "Build Active Architecture Only" set to NO for Release.


Also for the Watch Framework, I receive ITMS-90362: "Invalid Info.plist value. The value of the key 'MinimumOSVersion' is invalid. The minimum value is 8.0." This key was not set in Info.plist at all. I manually added this key with the value 9.0, rebuilt, and resubmitted, with no change in error message.


I also receive ITMS-90125: "The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's linker." I have not customized the linker.


Lastly, I receive ITMS-90203: "Invalid architecture: Apps that include an app extension and framework must support arm64." Most likely related to the error ITMS-90087 from above.


The Watch Framework is embedded in the watch extension via the Embed Frameworks build phase. Interestingly, on a new test app, I don't see an Embed Frameworks build phase by default for Watch Frameworks in Xcode 7b2, but without it, a "submit to App Store" operation won't include the framework. The Cocoa Touch framework is included in the Embed Frameworks option in the iOS app. The iOS app also has the watchOS 2 app embedded in the Embed Watch Content build phase.


Does anyone have more insight into these errors? As far as I can tell, my build settings contradict the errors. FWIW, I do not embed any third-party frameworks, only my own frameworks that are built in Xcode. TestFlight claims support iOS 9 beta builds. Thanks.

I've been receiving 90125 and 90362 (invalid value for 'UIRequiredDeviceCapabilities"). No clue what's going on. Been searching online like a mad man for the past two weeks. It also doesn't help that my watch is pretty much unusable since the beta came out (nearly no haptics whatsoever). 😠

On a hunch, I removed the watchOS 2 app from being embedded in the iOS 9 app, used Application Loader, and the upload succeeded. Sitting in the "Uploaded" status in iTunes Connect now. Though unfortunately, what I really wanted to test was the watch app.

I have same errors in Xcode 7 beta 6. Have you fixed this issue?

I've also been getting the same errors. Specifically:


ITMS-90086

ITMS-90087

ITMS-90362

ITMS-90076


I just tried with Xcode 7 GM (7A218) and I'm still getting the same errors. 😟

I have the same errors, opened a bug with apple, they closed it as a duplicate of some other bug. My assumption is that it's something to do with their back end not yet ready for iOS9 SDK. Notice how they have not yet invited people to submit apps for review, even though public release is soon.

Yes, I opened a radar(22417478) about this issue and it's stil open.

Getting the same thing, currently on Xcode 7 GM and watchOS2 GM... any update on your end?


(BTW, is there a way for others to see/track your radar report?)

Several ITMS Errors submitting iOS 9/watchOS 2 beta app to TestFlight
 
 
Q