title: Xcode 10 GM - Invalid Binary Architecture when submitting to App Store Connect?
body: <p>I have an iOS and watchOS app that support iOS 11/12 and watchOS 4/5. I've been submitting builds to App Store Connect for TestFlight without issue using the Xcode 10 betas. Today I submitted a build using Xcode 10 GM, and I got the following email:</p>
  <blockquote>
  <p>Dear Developer,</p>
  <p>We identified one or more issues with a recent delivery for your app, &quot;littlefeed&quot;. Please correct the following issues, then upload again.</p>
  <p>Invalid Binary Architecture - iOS 3.0 introduced support for multiple binary architectures. If your binary is built for multiple architectures, your Info.plist must have a MinimumOSVersion key with a value of at least 3.0. Additionally, if your app is intended to support earlier iPhone and iPod touch models, your app must contain at least an armv6 binary; &quot;thin&quot; armv7-only binaries will not be accepted unless the armv7 required device capability is also present in the Info.plist UIRequiredDeviceCapabilities key or the MinimumOSVersion key has a value of 4.3 or higher.</p>
  <p>For more information, see Technical Q&amp;A QA1707 at: <a href="http://developer.apple.com/iphone/library/qa/qa2010/qa1707.html" rel="noreferrer">http://developer.apple.com/iphone/library/qa/qa2010/qa1707.html</a>.</p>
  <p>Best regards,</p>
  <p>The App Store Team</p>
  </blockquote>
  <p>Problem is, this information is terribly out of date. The MinimumOSVersion key has long been deprecated; armv6 is an irrelevant architecture for iOS 11+ devices; the link to QA1707 is dead; etc. All related issues on Google and Stack Overflow tend to date back to 2012 or earlier, so I don't actually know what the issue is. My best shot-in-the-dark is that it's related to the fact that the Apple Watch Series 4 is now a 64-bit processor, and maybe I need to configure my watch app and watch extension targets somehow to handle it?</p>
  <p>If anyone has any thoughts, it'd be much appreciated.</p>