IPhone / iPod Touch: application executable contains unsupported architectural elements: armv7s

Question

As I see it, the problem is in the AppStore for my application! The verification process says: "iPhone / iPod Touch: application executable contains unsupported architectural elements: armv7s"

this is my library linked: CoreLocation (required) Twitter (optional) QuartzCore (required) MapKit (required) UIKit (required) Fund (required) CoreGraphics (required) libGoogleAnalytics.a (required) libsqlite3.dylib (required) CFNetwork (required)

I also tried removing the GoogleAnalytics library, but the problem is the same! Do you have any ideas?

thanks

Answer 1

Based on discussions on the Apple dev forums ( https://devforums.apple.com/message/749949 ), it seems like this is a bug affecting a lot of people. Probably due to a change in Apple's inspection servers.

I managed to get around this by changing the build architecture in the build settings from Standard (armv7, armv7s) to armv7 and rebuild. This should only lead to the fact that the compiled code is not optimized for iPhone 5. It will still work, but may not be as fast as if it had been compiled for armv7s. I suspect that the difference in performance will be negligible in most cases.

Answer 2

It helps me:

Project → Build Settings → remove architecture from the “valid architecture”, as well as the setting “Only build active architecture” Yes in the project

Answer 3

I had the same problem today. There are no third-party libraries in my application.

12 days ago I sent an assembly from Xcode 4.5.1, which was subsequently reviewed and released on the App Store. Today I tried to introduce a new assembly and suddenly got this error.

Then I tried to check the same executable file (rather than rebuild) from Xcode, which I introduced 12 days ago, and which passed the test and is now available for download in the App Store, but this time it did not pass the test using the above error.

Performing step 4 above allowed me to introduce a new assembly. But the executable is smaller, although I added a small amount of code and three small png / jpegs. This makes me think that the armv7s code is missing from the archive.

What's happening? Why should you take step 4 above the "work"? Why does an executable file that was previously sent OK and released suddenly stop checking?

Note: this is not a duplicate of the previous post that I could find 15 hours ago. This is the first time I have seen this error when sending to iTunes Connect, and not when I get a compiler warning. Therefore, please do not mark this as a duplicate. This is not true.

Answer 4

Most of the answers here are those that I did not find ideal, mainly because they essentially offer you to remove armv7s support from your application. Although this will force you to approve application verification, which could potentially make your application run slower on the iPhone 5.

Here is a workaround that I am using (although I have to say that I would not call this a solution).

Instead of using Xcode Organizer, I upload a binary using Application Loader.

To download a binary using Application Loader

Open Organizer> Right-click on the archive> Open in Finder.

Right-click archive file> Show archive contents

Go to Products> Application> YourAPP.app

Compress YourAPP.app and download using Application Loader.

Answer 5

My problem was that I was using an old version of Application Loader.

The solution for me was to download the latest version of iTunes Loader Application Loader> Application Management> Download the application loader and try again.

Answer 6

Try the following:

1.Select your project in Xcode (with a blue icon)

2. Select Build Settings

3.Set the All / Combined view

4. Set "Built-in Active Architecture Only" to "Yes"