How to fix "IPA processing failed" error in xcode 11?

Question

When I tried to create IPA file using Distribute APP option. It gave "IPA processing failed" error.

I have checked logs file: IDEDistribution.standard.log file.

2019-08-06 18:36:52 +0000 warning: Configuration issue: platform iPhoneSimulator.platform doesn't have any non-simulator SDKs; ignoring it Scanning IPA... 2019-08-06 18:36:52 +0000 Assertion failed: Expected 4 archs in otool output: /var/folders/4t/rpjk7pd55t16jfrd32y98gf0lb2t68/T/IDEDistributionOptionThinning.~~~a4cZJc/Payload/demo.app/Frameworks/AppAuth.framework/AppAuth: Mach header magic cputype cpusubtype caps filetype ncmds sizeofcmds flags MH_MAGIC_64 X86_64 ALL 0x00 DYLIB 23
3680 NOUNDEFS DYLDLINK TWOLEVEL NO_REEXPORTED_DYLIBS Load command 0

I am able to fix this issue after updating AppAuth.framework. — R.B Niranjan
– R.B Niranjan, Commented Aug 6, 2019 at 20:25
This problem was because of APPAuth.framework was not compatible with xcode11. I updated the framework and not it is working fine. — R.B Niranjan
– R.B Niranjan, Commented Aug 8, 2019 at 16:34
i am having a similar error with Alamofire5 beta 7 and earlier versions of the beta, tried ur way but didnt work out. Thanks anyway!! — Catluc
– Catluc, Commented Aug 8, 2019 at 20:30
Make sure your binary frameworks and pod framework paths are not included in Build Phases -> Copy Bundle Resource — Kuvonchbek Yakubov
– Kuvonchbek Yakubov, Commented May 27, 2020 at 11:58

Dilip Mishra · Accepted Answer · 2020-03-04 17:53:57Z

58

I faced same issue.I have fix this issue used this script.
Please follow the same steps.

Build Phases -> plus button -> to create New Run Script Phase

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

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"
echo $(lipo -info "$FRAMEWORK_EXECUTABLE_PATH")

FRAMEWORK_TMP_PATH="$FRAMEWORK_EXECUTABLE_PATH-tmp"

case "${TARGET_BUILD_DIR}" in
*"iphonesimulator")
    echo "No need to remove archs"
    ;;
*)
    if $(lipo "$FRAMEWORK_EXECUTABLE_PATH" -verify_arch "i386") ; then
    lipo -output "$FRAMEWORK_TMP_PATH" -remove "i386" "$FRAMEWORK_EXECUTABLE_PATH"
    echo "i386 architecture removed"
    rm "$FRAMEWORK_EXECUTABLE_PATH"
    mv "$FRAMEWORK_TMP_PATH" "$FRAMEWORK_EXECUTABLE_PATH"
    fi
    if $(lipo "$FRAMEWORK_EXECUTABLE_PATH" -verify_arch "x86_64") ; then
    lipo -output "$FRAMEWORK_TMP_PATH" -remove "x86_64" "$FRAMEWORK_EXECUTABLE_PATH"
    echo "x86_64 architecture removed"
    rm "$FRAMEWORK_EXECUTABLE_PATH"
    mv "$FRAMEWORK_TMP_PATH" "$FRAMEWORK_EXECUTABLE_PATH"
    fi
    ;;
esac

echo "Completed for executable $FRAMEWORK_EXECUTABLE_PATH"
echo $(lipo -info "$FRAMEWORK_EXECUTABLE_PATH")

done

edited Mar 4, 2020 at 17:53

answered Mar 2, 2020 at 17:59

Dilip Mishra

1,45214 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Aman Gupta Over a year ago

I have done the same as explained. Build is created successfully. But when i installed it on my real device, app has been installed but the app icon is disabled. I didn't get any error. And unable to open the application

atulkhatri Over a year ago

The most important thing to keep in mind is to add this Run script at the very end of BuildPhases. Specifically after 'Embed Frameworks' so that it makes sure that the unwanted architectures are stripped from all frameworks.

Zgpeace · Accepted Answer · 2020-03-06 07:40:09Z

49

1.uncheck "Rebuild from bitcode", 2.click next fast fast fast. (speed is also important.)

if not , it will show IPA processing failed.

answered Mar 6, 2020 at 7:40

Zgpeace

4,49340 silver badges34 bronze badges

12 Comments

Booharin Over a year ago

Thnx, man, I have react native frameworks in my app, they don't work with bitcode

Aman Gupta Over a year ago

I have done the same as explained. Build is created successfully. But when i installed it on my real device, app has been installed but the app icon is disabled. I didn't get any error. And unable to open the application.

Zgpeace Over a year ago

Hi @AmanGupta, I think you can debug you app in real device firstly with develop certificate.

Aman Gupta Over a year ago

@Zgpeace can you let me know how to change it and run in the real device?

Mihir Oza Over a year ago

Not able to Uncheck. Before uncheck itself ipa processing fail screen comes.

|

nullLululi · Accepted Answer · 2019-10-10 10:02:13Z

17

You should check the Embed Frameworks under Xcode > build phases.

If your framework is introduced here, you can't use i386\x86_64 in your framework. Because the Embed Frameworks are copied to the application. To control the size of the application, the frameworks in the Embed Frameworks are required to be the most streamlined.

You can use Link Binary With Libraries to introduce your framework, as described here: https://github.com/Carthage/Carthage/issues/1046

Note that you need to add a new Run Script and add your framework to it, or it will crash.

edited Oct 10, 2019 at 10:02

answered Oct 10, 2019 at 8:46

nullLululi

1941 silver badge7 bronze badges

Comments

wkukielczak · Accepted Answer · 2020-02-26 14:55:24Z

14

To solve similar problem on my end I used the following:

In app's target I went to the Build Phases
After the Embed Frameworks and Embed App Extensions sections I've added Run script with the following script:

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

The script I took from here: https://medium.com/@maximbilan/ios-submission-unsupported-architectures-issues-733917a98cc3, credits goes to Daniel Kennet!

Also, be aware that this script could also cause compilation errors. In such case, here's the solution: Errors building Xcode Project after adding in Run Script fatal error: lipo: input file

On my end I also noticed that I have to turn off this script when compiling app locally (on development devices/simulator)

Hope that helps!

answered Feb 26, 2020 at 14:55

wkukielczak

5194 silver badges8 bronze badges

2 Comments

Morten Holmgaard Over a year ago

I was just about to write the exact same answer :)

Maciej Stramski Over a year ago

This plus removing all static libs from copy-carthage step did the trick. Thanks!

chenfeng · Accepted Answer · 2019-09-27 08:26:49Z

8

It seems that a dynamic library with i386 or x86_64 architecture is not allowed when archive in Xcode 11. And I fixed it by removing those architectures from the mentioned frameworks

answered Sep 27, 2019 at 8:26

chenfeng

937 bronze badges

3 Comments

Tonny Xu Over a year ago

Actually I fixed the problem by adding a script to remove the simulator binary

JhonnyTawk Over a year ago

@TonnyXu I have the same issue can you provide me with the script

Lean van Heerden Over a year ago

The script from @Varrry in this so article did the trick to remove the architectures and solved the problem for me

MobileMon · Accepted Answer · 2019-11-20 12:41:26Z

6

I had to uncheck "Rebuild from bitcode"

answered Nov 20, 2019 at 12:41

MobileMon

8,6915 gold badges60 silver badges80 bronze badges

4 Comments

Benjohn Over a year ago

This immediately worked for me – thanks! I've no idea what the underlying reasons are (and it could well be to do with other architectures), but this seems worth a try.

Martin Over a year ago

Is there a way to do this without having to click? My computer fails much to fast.

Martin Over a year ago

Yes that works. But of a fast machine the error comes faster the you can click the checkbox. You need to try dozen's of times. There must be a better way.

mhammad alkhalaf Over a year ago

If Bitcode disabled , Firebase Crashlytics will not work

Muzahid · Accepted Answer · 2021-09-28 05:31:00Z

4

For those who try with M1 Chip (Silicon)

Quit Xcode completely (Close and Quit From the Menu Bar) and remove existing archived one.

Go to finder -> Applications

Right Click on Xcode and select "Get Info"

Check Rosetta

Try again opening Xcode

edited Sep 28, 2021 at 5:31

Muzahid

5,1862 gold badges26 silver badges45 bronze badges

answered May 10, 2021 at 9:58

Chamin Thilakarathne

4471 gold badge7 silver badges24 bronze badges

Comments

David Němec · Accepted Answer · 2019-10-09 14:25:41Z

3

We've solved this problem by setting Always Embed Swift Standard Libraries to NO in all frameworks, that are being used in our app.

answered Oct 9, 2019 at 14:25

David Němec

896 bronze badges

1 Comment

DragonCherry Over a year ago

Thank you. Setting it to default 'NO' made it work and exported ipa file successfully. I guess swift libraries embedded in framework might cause app fail to enable bitcode for whole application.

Josef Vancura · Accepted Answer · 2019-12-10 10:36:33Z

3

I had to select "Do not embed" in Frameworks to solve this

answered Dec 10, 2019 at 10:36

Josef Vancura

1,19911 silver badges20 bronze badges

Comments

Bijoy Thangaraj · Accepted Answer · 2021-03-04 04:21:44Z

2

Having Bitcode enabled caused the issue in my case. Go to

Build Settings -> Enable Bitcode and set it to NO.

Try archiving again and it should work.

answered Mar 4, 2021 at 4:21

Bijoy Thangaraj

5,5464 gold badges46 silver badges73 bronze badges

1 Comment

mhammad alkhalaf Over a year ago

If Bitcode disabled , Firebase Crashlytics will not work

miletliyusuf · Accepted Answer · 2020-07-06 20:10:57Z

1

In my case, app thinning was failing and the reason was my internal framework was depending Alamofire and it's binary was embedding and signing. Changing it's Embed option from Embed & Sign -> Do Not Embed solved my issue immediately.

In my opinion, all logic behind this issue is keep app bundle size lower as much as Apple can but embedding your frameworks increase this size. I think that's all App Thinning complains about. So, the general solution to this issue, check every external frameworks that can increase your app bundle. Especially, if you're using Carthage.

answered Jul 6, 2020 at 20:10

miletliyusuf

1,0221 gold badge12 silver badges15 bronze badges

Comments

MD. · Accepted Answer · 2019-12-04 07:20:35Z

0

I found issue with SDWebImageMapKit framework available with SDWebImage. I just removed it and got success.

answered Dec 4, 2019 at 7:20

MD.

1,16711 silver badges18 bronze badges

Comments

Xaxxus · Accepted Answer · 2020-11-05 00:40:54Z

0

My issue was that I had a single embedded binary framework.

I removed it from the project to update it. Which caused Xcode to delete the embed frameworks build phase (because there were no more frameworks to embed).

After adding the new version of our framework, the embed binaries phase was at the bottom of the build phase order. Which ended up being the reason it was failing.

I had to re-order embed frameworks before my run script to fix the problem.

answered Nov 5, 2020 at 0:40

Xaxxus

2,02917 silver badges25 bronze badges

Comments

Kyle L · Accepted Answer · 2021-04-23 00:36:37Z

0

I haven't updated my cocoapods for a while, fixed it by updating and re-installing the pods.

sudo gem install cocoapods
pod update
pod deintegrate
pod install

answered Apr 23, 2021 at 0:36

Kyle L

6916 silver badges9 bronze badges

Comments

Husam · Accepted Answer · 2022-08-10 22:07:11Z

-1

My solution was to set all frameworks dependencies to "Do Not Embed"

answered Aug 10, 2022 at 22:07

Husam

8,5793 gold badges40 silver badges45 bronze badges

Comments

Gopal Gupta · Accepted Answer · 2020-04-02 03:45:15Z

-2

Open Terminal 
Open your project drag path of respective framework to Terminal  For example.

cd /Users/xxxxx/Desktop/MyProject/ABC.framework 
Set your Framework name in below command and run

 lipo -remove i386 ABC -o ABC && lipo -remove x86_64 ABC -o ABC

answered Apr 2, 2020 at 3:45

Gopal Gupta

1

1 Comment

Alan Over a year ago

Welcome to StackOverflow. When answering a question, please also provide an explanation that explains why the problem exists and how your solution solves it, so that people can actually understand rather than just making the problem go away.

Collectives™ on Stack Overflow

How to fix "IPA processing failed" error in xcode 11?

16 Answers 16

2 Comments

12 Comments

Comments

2 Comments

3 Comments

4 Comments

Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

My solution was to set all frameworks dependencies to "Do Not Embed"

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

16 Answers 16

2 Comments

12 Comments

Comments

2 Comments

3 Comments

4 Comments

Comments

1 Comment

Comments

1 Comment

Comments

Comments

Comments

Comments

My solution was to set all frameworks dependencies to "Do Not Embed"

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related