“Unexpected Machine Code” warning from iTunes Connect

117
votes

After I uploaded my build to iTunes Connect by using Application Loader, I got an email about an issue "Unexpected Machine Code" see below.

Unexpected Machine Code - Your upload contains both bitcode and native machine code. When you provide bitcode, it's not necessary to include machine code as well. To reduce the size of your upload, use Xcode 7.3 or later, or any other toolchain that removes machine code.

I am so confused about this warning. Is this a new thing in iTunes Connect? Why it doesn't give me the warning when I upload QA build but Release build?

Update: I upload QA build last week, it wasn't any warning. And today (June 27th 2016) I upload Release build, it send me the warning.

1
iosapp-store-connect
I received this email too today. We had an app update go through review two days ago without problems. And I uploaded a TestFlight internal build today that "processed" just fine. The thing that was odd to me was that all of the emails associated with our developer account were cc'd on the email. I called Apple Developer Support - no help there yet. The email I received arrived just before a TestFlight processing complete email arrived. I just did a "normal" Xcode build. No fancy build tools. – Daniel
Same error. Built and uploaded directly from Xcode. – picciano
20 min after getting this email, my app became available for testing. Seems likely it was a bug on Apple's end and it resolved itself. – evanflash
I am nominating this question to be reopened. It is still occurring, and is not a simple typographical error. The question clearly explains the process used to reproduce the error, the error message (from Apple), and the expected result (no error). – picciano
Apparently this question should be reopened. And here is some update, I submitted my app for review (nothing changed after got the warning email) yesterday, and it passed today without any issue. I believe we can ignore the warning email and wait Apple's explanation. – Herbert

1 Answers

122
votes

Just got this as well, it's a bug. I uploaded the near exact same binary as I did a couple of days ago which went through fine (only change was to the version and build number). Developer support confirmed this.

If you do get the e-mail, don't worry about it. Your binary will still process and you'll still be able to submit it to the app store.

Update: both of my binaries which received this message passed review and have been released to the app store.