Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

iPhone/iPod Touch: application executable contains unsupported architeture(s): armv7s

i'im seeing a problem releasing on AppStore my App! The validation process say: "iPhone/iPod Touch: application executable contains unsupported architeture(s): armv7s"

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

I've also tryed to remove GoogleAnalytics Library but the problem is the same! Do you have any idea?

Thanks

like image 313
Luca T Avatar asked Oct 30 '12 21:10

Luca T


3 Answers

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

I was able to work around it by changing the build architecture in Build Settings from Standard(armv7,armv7s) to armv7 and rebuilding. This should only have the effect that the compiled code is not optimized for iPhone 5. It will still run, but may not be quite as fast as if it were compiled for armv7s. I suspect the performance difference would be negligible in most cases.

like image 151
Chris Garrett Avatar answered Oct 26 '22 16:10

Chris Garrett


This helped me:

Project -> Build Settings -> remove the architecture from "valid architectures" as well as setting the "Build Active Architecture Only" to Yes in the Project

like image 21
Nekelle Latoya Celestine Avatar answered Oct 26 '22 15:10

Nekelle Latoya Celestine


I had the same problem today. My app has no third-party libraries.

12 days ago I submitted a build from Xcode 4.5.1 that was subsequently reviewed and released to the App Store. Today I tried to submit a new build and suddenly received this error.

I then tried to validate the same executable (not a rebuild) from within Xcode that I had submitted 12 days ago and that had passed validation and is now available for download in the App Store, but this time it failed validation with the above error.

Performing step 4 above allowed me to submit the new build. But the executable is smaller even though I have added a small amount of code and three small png/jpegs. This makes me think that armv7s code is missing from the archive.

What is happening? Why should step 4 above 'work'? Why does an executable that previously submitted OK and was released suddenly no longer pass validation?

Note: this is not a duplicate of any previous post that I was able to find 15 hours ago. This is the first time I have seen any mention made of seeing this error when submitting to iTunes Connect rather than receiving a compiler warning. So please do not mark this as a duplicate. It is not.

like image 38
ghr Avatar answered Oct 26 '22 16:10

ghr