xcode 5 archive build fail, but normal build successfully

Question

I can build and run my app on my device, but when I tried to build archive, I got many errors. The errors are about my 3rd library - google protobuf. It showed that #error Host architecture was not detected as supported by protobuf. But what is the difference between archieve and normal build?? After all, I built successfully and ran my app on the device when I choose product=>run (cmd+R).

Solution 1

When you build to run, Xcode usually builds for the active architecture only. When you archive it builds all the architectures specified by the intersection of the Build Settings "Architectures and Valid Architectures".

So it's likely that Xcode is trying to build for some architecture that isn't supported by your protobuf library, e.g. Arm64.

Solution 2

For me the problem was that the scheme for "Archive" was different than the scheme for "Run". When i switched "Archive" to use DEBUG instead of RELEASE it worked.

Solution 3

You can see reasons for failure in Report Navigator present in Navigator window.

Menu -> View -> Navigator -> Hide/Show Navigator

Extra icon will appear/disappear next to Breakpoint icon after Hide/Show Navigator

Open Report Navigator by pressing last button present on list of buttons in Navigator window.

Here you can view reasons either By Group or By Time.

Comments

[Arton]

Thanks a lot! I changed the setting and then built successfully!

[Michael]

This was also my issue after updating to xcode 5.1, it added it to my existing project. Not very nice! What's worse is all it would say is "Archive failed", no hint to the issue. Thanks for pointing this out.

[Chris Allinson]

thanks a bunch for this answer!!! Apparently after I upgraded to Xcode w/ SDK7.1 it has automatically added the arm64 as a valid architecture to every single one of my projects!!! Removing arm64 was the solution!!! THANKS!!!

[Ankur Loriya]

I have tried as you say @Rhytmic but still failed archive. Just I had change xcode 5 to xcode 5.1

[Salman Hasrat Khan]

Strangely this works for me too, but I don't think using the Debug Configuration is the right way to go. I think I'll fill it as a bug with Apple

[Salman Hasrat Khan]

@Darmen they acknowledged the bug and linked it to another one. I think they plan to fix it in the upcoming release although they haven't officially acknowledged it.

[StackRunner]

Archive is supposed to use release so it strips the debug symbols from the app and allows it to be used for app store distribution.