Reputation: 14123
This is quite linked to this question but it doesn't have any solution.
On uploading a build to iTunes Connect, I received the following message:
We have discovered one or more issues with your recent delivery for "Hurdal IL". Your delivery was successful, but you may wish to correct the following issues in your next delivery:
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.
After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.
Upvotes: 29
Views: 5403
Reputation: 566
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.
Upvotes: 0
Reputation: 14123
The app which I published with this waring was just approved by Apple. So to answer my question, this won't affect the app approval. Also, I am accepting @Helen Wood's answer as she was right that this is an apple bug.
Upvotes: 0
Reputation: 9
I've the same problem, I send my application to review with that issue.
Result:
My app pass the review and already in publication. No problem... I think it's a issue from iTunes Connect.
Upvotes: 1
Reputation: 1882
I just talked with the Apple Developer Support, the official one. They don't said it clearly, but yes it's a bug. So, it's confirmed that there's some malfunctioning in their side.
UPDATE: It won't affect the Apps in Production neither Testing!
Upvotes: 14
Reputation: 722
I have same issue but in my case I set in Xcode Build Setting Enable Bitcode to NO. After this error I change it to YES and it works
Upvotes: 3
Reputation: 1941
I just uploaded a binary recently (like 20m ago). They did sent me a note just like you. After that, I just re-built it again, only update the build version (1943) and upload. Now it seems like there's nothing happened anymore. And the previous build (1942) has completed processing without failure. So I doubt it's a bug from Apple.
Just ignore it. You may want to build another binary to fix the warning tho.
Upvotes: 1
Reputation: 944
No, its not effect app approval and the binary seems to be accepted by the iTunes store.
Upvotes: 1