How do I fix IPA processing failed in Xcode 11?

 I could archive the app in Xcode 12.2 DKT device.

however when I try to distribute IPA from archived files and it failed with 'IPA processing failed'.
from the log files, there is no useful information.

Does anyone have similar issues?
I appreciate any suggestions how to solve this issue.

• Xcode
 
• Universal Apps

Post not yet marked as solvedUp vote post of cloudiosDown vote post of cloudios

 3.3kviews

Asked 6 months ago by 

cloudios

Answer this Question

Add a Comment

Answers

So I ran into this. I want to clarify this seems to affect the new M1 (Apple Silicon Macs) specifically, and seems to affect Cocoapods / Carthage frameworks in a project. I'm a little bit surprised there is no legitimate response from Apple. I've spent a few evenings digging around on this. On stackoverflow there appears to be some indication that the "fix" is to target iOS 13.0. See: https://stackoverflow.com/questions/64916429/how-to-fix-ipa-processing-failed-in-xcode-12-2-with-mac-m1?noredirect=1&lq=1

I'd like to hear a response from Apple on the root cause and some work arounds.

Posted 5 months ago by 

underpug01

Up vote reply of underpug01Down vote reply of underpug01

Add a Comment

I've found a solution or two that can work but there are many variables. Xcode 12.2 / M1 / Apple Silicon combination seems to introduce this problem. I can successfully distribute by using Rosetta mode on starting Xcode. Note however this is just a work around. You cannot edit the Storyboards in Rosetta, so you would only use this for distribution. We really need someone from Apple to identify the root cause. I will look to see if there is a bug filed on the apple radar.

Posted 5 months ago by 

underpug01

Post not yet marked as solvedUp vote reply of underpug01Down vote reply of underpug01

Add a Comment

@underpug01
We really need someone from Apple to identify the root cause.

That never happens and this is not the first time we had a problem with the IPA Build:

https://stackoverflow.com/questions/57382217/how-to-fix-ipa-processing-failed-error-in-xcode-11

The root cause is trying to build something in the background before the user made his final choices.

Posted 3 months ago by 

Martin.Krischik

Up vote reply of Martin.KrischikDown vote reply of Martin.Krischik

Add a Comment

There are 2 solutions:

1) Run Xcode in Rosetta mode

• Quit Xcode completely

• Go to finder -> Applications

• Right Click on Xcode and select "Get Info"

• Check Rosetta

• Try again

2) Upgrade Xcode to 12.5

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

ipaxcode11ios13

Share

Improve this question

edited Aug 11 '19 at 0:23

Emma

1

asked Aug 6 '19 at 18:45

R.B Niranjan

58811 gold badge55 silver badges1111 bronze badges

• 1
  I am able to fix this issue after updating AppAuth.framework. – R.B Niranjan Aug 6 '19 at 20:25
• could u provide more info on how u did that process? – Catluc Aug 8 '19 at 11:08
• 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 Aug 8 '19 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 Aug 8 '19 at 20:30
• 2
  Make sure your binary frameworks and pod framework paths are not included in Build Phases -> Copy Bundle Resource – Kuvonchbek Yakubov May 27 '20 at 11:58

Show 6 more comments

15 Answers

ActiveOldestVotes

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

Share

Improve this answer

edited Mar 4 '20 at 17:53

answered Mar 2 '20 at 17:59

Dilip Mishra

1,2931111 silver badges1616 bronze badges

• 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 – Aman Gupta Jun 8 '20 at 13:33
• 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. – atulkhatri Jul 28 '20 at 14:11

Add a comment

40

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

if not , it will show IPA processing failed. 

Share

Improve this answer

answered Mar 6 '20 at 7:40

Zgpeace

2,0891717 silver badges2020 bronze badges

• Thnx, man, I have react native frameworks in my app, they don't work with bitcode – Booharin Mar 18 '20 at 7:11
• 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. – Aman Gupta Jun 8 '20 at 13:33
• Hi @AmanGupta, I think you can debug you app in real device firstly with develop certificate. – Zgpeace Jun 9 '20 at 2:40
• @Zgpeace can you let me know how to change it and run in the real device? – Aman Gupta Jun 9 '20 at 3:10
• @AmanGupta Could you let me know whether you can debug your app in real device with develop certificate? I suggest that you can debug your app to find more logging in real device. – Zgpeace Jun 9 '20 at 3:26

Show 7 more comments

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.

Share

Improve this answer

edited Oct 10 '19 at 10:02

answered Oct 10 '19 at 8:46

nullLululi

19511 silver badge66 bronze badges

Add a comment

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!

Share

Improve this answer

answered Feb 26 '20 at 14:55

wkukielczak

35922 silver badges77 bronze badges

• I was just about to write the exact same answer :) – Morten Holmgaard Feb 27 '20 at 9:41
• This plus removing all static libs from copy-carthage step did the trick. Thanks! – Maciej Stramski Jul 23 '20 at 15:15

Add a comment

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

Share

Improve this answer

answered Sep 27 '19 at 8:26

chenfeng

9377 bronze badges

• 2
  Actually I fixed the problem by adding a script to remove the simulator binary – Tonny Xu Oct 2 '19 at 10:24
• @TonnyXu I have the same issue can you provide me with the script – JhonnyTawk Nov 4 '19 at 9:00
• 3
  The script from @Varrry in this so article did the trick to remove the architectures and solved the problem for me – Lean van Heerden Nov 5 '19 at 3:22

Add a comment

5

I had to uncheck "Rebuild from bitcode"

Share

Improve this answer

answered Nov 20 '19 at 12:41

MobileMon

7,28944 gold badges4646 silver badges6666 bronze badges

• 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. – Benjohn Nov 21 '19 at 10:14
• This helped me. thanks – Habib Ali Nov 29 '20 at 12:05
• Is there a way to do this without having to click? My computer fails much to fast. – Martin Feb 24 at 11:45
• 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. – Martin Mar 3 at 13:22

Add a comment

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.

Share

Improve this answer

answered Oct 9 '19 at 14:25

David Němec

8966 bronze badges

• 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. – DragonCherry Jan 15 '20 at 6:00

Add a comment

3

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

Share

Improve this answer

answered Dec 10 '19 at 10:36

Josef Vancura

81188 silver badges1616 bronze badges

Add a comment

2

For those who try with M1 Chip (Silicon)

Quit Xcode completely (Close and Quit From the Menu Bar)

Go to finder -> Applications

Right Click on Xcode and select "Get Info"

Check Rosetta

Try again opening Xcode

Share

Improve this answer

edited May 10 at 10:03

answered May 10 at 9:58

Chamin Thilakarathne

21555 silver badges1616 bronze badges

Add a comment

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.

Share

Improve this answer

answered Jul 6 '20 at 20:10

miletliyusuf

37633 silver badges88 bronze badges

Add a comment

1

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.

Share

Improve this answer

answered Mar 4 at 4:21

Bijoy Thangaraj

4,96033 gold badges3535 silver badges6464 bronze badges

Add a comment

0

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

Share

Improve this answer

answered Dec 4 '19 at 7:20

MD.

1,1471111 silver badges1818 bronze badges

Add a comment

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.

Share

Improve this answer

answered Nov 5 '20 at 0:40

Xaxxus

39033 silver badges1212 bronze badges

Add a comment

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

Share

Improve this answer

answered Apr 23 at 0:36

Kyle Liu

61866 silver badges99 bronze badges

Add a comment

-2

1. Open Terminal


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

    cd /Users/xxxxx/Desktop/MyProject/ABC.framework


3. Set your Framework name in below command and run

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

Share

Improve this answer

answered Apr 2 '20 at 3:45

Gopal Gupta

1

• 1
  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. – Alan Apr 2 '20 at 6:18