I am afraid that there is not much information about this issue. All I read is yesterday or today. This theme on the Apple bulletin board is what I liked most:
https://forums.developer.apple.com/thread/48023
This means that there might be some kind of problem on the iTunes Connect backend. This makes sense to me because I already managed to make some releases in my application before, and the BITCODE flags have not been changed before. Thus, this is either a change in the rules of the bitcode, or some random error.
In any case, we may have to wait until Apple makes this clear. I would advise you to stay on this topic in the forum :)
EDIT: I figured it out!
I use CocoaPods, and the Enable Bitcode option is enabled for all purposes in the Pods project, while my application is disabled. This means that the frameworks were created using the arm64-bitcode architecture instead of the man64 machine code that my project requires. Putting “Enable bitcode” to “No” for all purposes within the Pods project does the trick.
At least it worked for me. Too bad an apple does not give any feedback on this, because it looks like a recent change. I think there is another option that could work without changing the project settings: try disabling the "Enable bitcode" checkbox in Organizer after clicking the "Download to App Store" button.
Change (again) . Disabling the "Enable Bitcode" checkbox in the organizer definitely works :)
Bartserk
source share