ERROR ITMS-9000: "Unsupported architectures. Your executable contains unsupported architectures '[x86_64, i386]'"

Question

It is impossible to send in itunesconnect new version of the application. Although last week, the same version send happened. In the code, I just changed the name of a button, no more changes are not made where.
But always get error:

ERROR ITMS-9000: "Unsupported architectures. Your executable contains unsupported architectures '[x86_64, i386]'"

In my project -> Build Settings: ARCHS = $(ARCHS_STANDARD_32_BIT)
//:configuration = Debug
ONLY_ACTIVE_ARCH = YES
//:configuration = Release
ONLY_ACTIVE_ARCH = NO

VALID_ARCHS = armv7 armv7s

Make sure you have "iOS device" selected as your target at the top of the Xcode window - you are trying to submit a simulator build — Paulw11, Sep 17 '14 at 09:26
@Paulw11 It set my iPhone. I'm build a project on it, it all goes well. Then do the archive and try to send a itunescoonect, the result is the same. — Maxim Zakopaylov, Sep 17 '14 at 09:38
You need to check carefully your build settings or roll back from version control and try again - For some reason you are generating an x86 build — Paulw11, Sep 17 '14 at 09:40
Check Product -> Scheme -> Edit scheme... -> Archive. It has to say Build Configuration: "Release". — neutrino, Sep 17 '14 at 09:42
By the way, take a look at this: http://stackoverflow.com/q/19423800/1166894 — neutrino, Sep 17 '14 at 09:45
I experience the same issue and didn't find out how to fix it, a week ago it was everything fine. — invoodoo, Sep 18 '14 at 03:02
@AntonAnisimov I still can not solve this problem, if you find any solutions please let me know. — Maxim Zakopaylov, Sep 18 '14 at 08:48
@AntonAnisimov you use YandeksMapKit in your project? I think the problem is in it. — Maxim Zakopaylov, Sep 18 '14 at 09:56
I had used ShareKit, but the idea was to start removing of the Cocoapods or other libraries to find what doesn't work and I did find that it was ShareKit, because it used LiveSDK. — invoodoo, Sep 20 '14 at 18:48
It could be any library that you've using right now, just try to remove them and see what it cause do that. — invoodoo, Sep 20 '14 at 18:49

score 25 · Accepted Answer · answered Mar 09 '15 at 22:57

25

Check out this slick solution on Daniel Kennett's blog - it worked perfectly for me with the SpritzSDK, which I had similar issues with.

He supplies a script you can drop-in to your build phases to strip out the unwanted architectures as a last step - doesn't break the simulator, and iTunesConnect approved my upload as well on the first try.

http://ikennd.ac/blog/2015/02/stripping-unwanted-architectures-from-dynamic-libraries-in-xcode/

answered Mar 09 '15 at 22:57

BricoleurDev

827
9
14

Run script only when installing? or no? – William GP Mar 24 '16 at 06:51
The script goes into the build phase, so only when building – BricoleurDev Mar 24 '16 at 14:28
How come some of frameworks don't require this script and still manage to build and run both in Simulator and actual devices? – Genki Apr 04 '17 at 16:58

Arpan Dixit · Answer 2 · 2016-11-11T12:50:51.033

You can remove unwanted ARCHS from IPA by putting below peace of Shell Script in Build Phase -- > RUN Script This Script removes all simulator ARCHS from IPA and ARCH issues from Embedded framework. Source : http://ikennd.ac/blog/2015/02/stripping-unwanted-architectures-from-dynamic-libraries-in-xcode/

APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}"

# This script loops through the frameworks embedded in the application and
# removes unused architectures.
find "$APP_PATH" -name '*.framework' -type d | while read -r FRAMEWORK
do
    FRAMEWORK_EXECUTABLE_NAME=$(defaults read "$FRAMEWORK/Info.plist" CFBundleExecutable)
    FRAMEWORK_EXECUTABLE_PATH="$FRAMEWORK/$FRAMEWORK_EXECUTABLE_NAME"
    echo "Executable is $FRAMEWORK_EXECUTABLE_PATH"

    EXTRACTED_ARCHS=()

    for ARCH in $ARCHS
    do
        echo "Extracting $ARCH from $FRAMEWORK_EXECUTABLE_NAME"
        lipo -extract "$ARCH" "$FRAMEWORK_EXECUTABLE_PATH" -o "$FRAMEWORK_EXECUTABLE_PATH-$ARCH"
        EXTRACTED_ARCHS+=("$FRAMEWORK_EXECUTABLE_PATH-$ARCH")
    done

    echo "Merging extracted architectures: ${ARCHS}"
    lipo -o "$FRAMEWORK_EXECUTABLE_PATH-merged" -create "${EXTRACTED_ARCHS[@]}"
    rm "${EXTRACTED_ARCHS[@]}"

    echo "Replacing original executable with thinned version"
    rm "$FRAMEWORK_EXECUTABLE_PATH"
    mv "$FRAMEWORK_EXECUTABLE_PATH-merged" "$FRAMEWORK_EXECUTABLE_PATH"

done

Please don't take it personally. If you are coping an intellectual property from someone else, please be kind enough to give the credit back to the original creator. In this case, http://ikennd.ac/blog/2015/02/stripping-unwanted-architectures-from-dynamic-libraries-in-xcode/ — Goppinath, Oct 26 '16 at 06:33

score 0 · Answer 3 · answered Dec 27 '16 at 11:44

0

The script in the above two answers needs to be edited if you have an watch app in your project. Add /Frameworks to the $APP_PATH to avoid errors when building the project.

answered Dec 27 '16 at 11:44

hohteri

174
1
5

score -1 · Answer 4 · answered Sep 19 '14 at 16:06

-1

If you are using LiveSDK directly or via ShareKit, you will run into this problem. In my case I was using LiveSDK directly.

Check this answer on Apple Developer Forum

https://devforums.apple.com/message/1037603#1037603

answered Sep 19 '14 at 16:06

Mohan

1
2

I am experiencing this same issue, I'm not using LiveSDK or ShareKit. Nothing seems to help. – Pax Sep 20 '14 at 07:24
1

My issue was caused by the Urban Airship SDK. :/ – Pax Sep 20 '14 at 19:25
@Mohan Thank you. Indeed all was well, as soon as I removed LiveSDK! – Maxim Zakopaylov Sep 22 '14 at 09:26
1

Hi how did you resolve this issue for live sdk. No answer in the link helped – Nitesh Nov 19 '14 at 10:34
how do I solve the issue if I used Urban Airship @Pax – Farai Dec 05 '14 at 07:24
Urban Airship includes unnecessary libs, you need to delete the ones that are not needed for your version of IOS before compiling. – Pax Apr 02 '15 at 13:16

ERROR ITMS-9000: "Unsupported architectures. Your executable contains unsupported architectures '[x86_64, i386]'"

4 Answers4

Linked