"Building universal frameworks with common architectures is not possible." error #3146

arielelkin · 2021-03-12T13:09:29Z

carthage install method: [ ] .pkg, [x] homebrew, [ ] source
which carthage: /usr/local/bin/carthage
carthage version: 0.37.0
xcodebuild -version: Xcode 12.4

I've added SPM support to my library, PocketSVG, but for some reason that has broken the pre-existing Carthage support.

This is what happens when I run carthage build --no-skip-current in my library's root dir:

*** xcodebuild output can be found in /var/folders/13/jh62fb214m394xbztdjkl2vm0000gn/T/carthage-xcodebuild.tIYkoX.log
*** Building scheme "PocketSVG-Package" in PocketSVG.xcodeproj
A shell task (/usr/bin/xcrun lipo -create /Users/arielelkin/Library/Developer/Xcode/DerivedData/PocketSVG-dzlvljxmlvgxeleefahougoqtbux/Build/Intermediates.noindex/ArchiveIntermediates/PocketSVG-Package/IntermediateBuildFilesPath/UninstalledProducts/appletvos/PocketSVG.framework/PocketSVG /Users/arielelkin/Library/Developer/Xcode/DerivedData/PocketSVG-dzlvljxmlvgxeleefahougoqtbux/Build/Products/Release-appletvsimulator/PocketSVG.framework/PocketSVG -output /Users/arielelkin/PocketSVG/Carthage/Build/tvOS/PocketSVG.framework/PocketSVG) failed with exit code 1:
fatal error: /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: /Users/arielelkin/Library/Developer/Xcode/DerivedData/PocketSVG-dzlvljxmlvgxeleefahougoqtbux/Build/Intermediates.noindex/ArchiveIntermediates/PocketSVG-Package/IntermediateBuildFilesPath/UninstalledProducts/appletvos/PocketSVG.framework/PocketSVG and /Users/arielelkin/Library/Developer/Xcode/DerivedData/PocketSVG-dzlvljxmlvgxeleefahougoqtbux/Build/Products/Release-appletvsimulator/PocketSVG.framework/PocketSVG have the same architectures (arm64) and can't be in the same fat output file

Building universal frameworks with common architectures is not possible. The device and simulator slices for "PocketSVG" both build for: arm64
Rebuild with --use-xcframeworks to create an xcframework bundle instead.

The text was updated successfully, but these errors were encountered:

tmspzz · 2021-03-15T09:30:22Z

Can you clear DerivedData and try again?

arielelkin · 2021-03-15T11:14:55Z

Hi @tmspzz

The issue is still there after clearing DerivedData.

You can reproduce it by cloning the library:
https://github.com/pocketsvg/pocketsvg

and running carthage build --no-skip-current

arielelkin · 2021-03-22T10:16:59Z

Hi @tmspzz Any updates? Were you able to reproduce the issue?

tmspzz · 2021-03-22T12:22:39Z

@arielelkin No sorry, I'm not currently looking into this

command-tab · 2021-04-02T18:11:06Z

I'm also encountering this while trying to build an existing project using Alamofire 5.4.1:

$ carthage build --platform iOS
*** xcodebuild output can be found in /var/folders/j3/7pf540td3xncn7jdqtb62_ph00058y/T/carthage-xcodebuild.4j9gJ4.log
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
A shell task (/usr/bin/xcrun lipo -create /Users/callen/Library/Caches/org.carthage.CarthageKit/DerivedData/12.4_12D4e/Alamofire/4.8.1/Build/Intermediates.noindex/ArchiveIntermediates/Alamofire\ iOS/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Alamofire.framework/Alamofire /Users/callen/Library/Caches/org.carthage.CarthageKit/DerivedData/12.4_12D4e/Alamofire/4.8.1/Build/Products/Release-iphonesimulator/Alamofire.framework/Alamofire -output /Users/callen/Projects/port80/archives-library-kiosk-app/Carthage/Build/iOS/Alamofire.framework/Alamofire) failed with exit code 1:
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: /Users/callen/Library/Caches/org.carthage.CarthageKit/DerivedData/12.4_12D4e/Alamofire/4.8.1/Build/Intermediates.noindex/ArchiveIntermediates/Alamofire iOS/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Alamofire.framework/Alamofire and /Users/callen/Library/Caches/org.carthage.CarthageKit/DerivedData/12.4_12D4e/Alamofire/4.8.1/Build/Products/Release-iphonesimulator/Alamofire.framework/Alamofire have the same architectures (arm64) and can't be in the same fat output file

Building universal frameworks with common architectures is not possible. The device and simulator slices for "Alamofire" both build for: arm64
Rebuild with --use-xcframeworks to create an xcframework bundle instead.

carthage 0.37.0
macOS 10.15.7
Xcode 12.4
Intel Mac

kmpnz · 2021-04-07T11:25:01Z

Hey @arielelkin. I've encountered a similar problem and it is not the perfect solution, but you can use the same workaround as described here https://github.com/Carthage/Carthage/blob/master/Documentation/Xcode12Workaround.md to fix this problem. Cheers

Rolando-Barbella · 2021-04-13T10:33:28Z

I have the same issue:

carthage 0.37.0
macOS Big Sur
Xcode 12.4
Mac M1

Does it not work at all with Apple Silicon?

byzeagle · 2021-04-14T15:03:24Z

I have the same problem with Tesseract-OCR-iOS.

Carthage 0.37.0
macOS Big Sure
Xcode 12.4
Mac M1

dbmrq · 2021-04-18T21:05:44Z

Using this script worked for me (I was using it for the original issue, tried to build without it and got this problem; went back to the script and everything worked 🤷🏻‍♂️).

Rolando-Barbella · 2021-04-18T21:17:42Z

@dbmrq Do you have a Mac M1?

dbmrq · 2021-04-18T23:00:49Z

@dbmrq Do you have a Mac M1?

Nope!

And I just found out that while Carthage compiles the frameworks using the script I mentioned, the resulting frameworks do not work on the project with the latest version of Xcode! :(

nfranke · 2021-05-04T21:29:30Z

Same problem trying to build Alamofire.

springlo · 2021-06-02T05:31:44Z

./carthage.sh update --platform "iOS"

carthage.sh:

# carthage.sh
# Usage example: ./carthage.sh build --platform iOS

set -euo pipefail

xcconfig=$(mktemp /tmp/static.xcconfig.XXXXXX)
trap 'rm -f "$xcconfig"' INT TERM HUP EXIT

# For Xcode 12 make sure EXCLUDED_ARCHS is set to arm architectures otherwise
# the build will fail on lipo due to duplicate architectures.

CURRENT_XCODE_VERSION=$(xcodebuild -version | grep "Build version" | cut -d' ' -f3)
echo "EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$CURRENT_XCODE_VERSION = arm64 arm64e armv7 armv7s armv6 armv8" >> $xcconfig

echo 'EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200 = $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1200__BUILD_$(XCODE_PRODUCT_BUILD_VERSION))' >> $xcconfig
echo 'EXCLUDED_ARCHS = $(inherited) $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_$(EFFECTIVE_PLATFORM_SUFFIX)__NATIVE_ARCH_64_BIT_$(NATIVE_ARCH_64_BIT)__XCODE_$(XCODE_VERSION_MAJOR))' >> $xcconfig

export XCODE_XCCONFIG_FILE="$xcconfig"
carthage "$@"

gotev · 2021-06-09T10:48:39Z

The above is working with xcode 12.x. Just tried with XC13 beta on macOS 12 Monterey Beta:

Xcode 13.0
Build version 13A5154h
xcode-select version 2388. installed in /Applications/Xcode-beta.app/Contents/Developer
swift-driver version: 1.26 Apple Swift version 5.5 (swiftlang-1300.0.19.104 clang-1300.0.18.4)
Target: x86_64-apple-macosx12.0

and it does not work anymore, giving lipo errors.

I tried adding also this to the temporary xcconfig but with no luck:

EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300__BUILD_13A5154h = arm64 arm64e armv7 armv7s armv6 armv8
EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300 = $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300__BUILD_$(XCODE_PRODUCT_BUILD_VERSION))

not sure if the needed variable name still follows previously known patterns:

EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300
EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300__BUILD_13A5154h

Has anyone tried this?

mkotzjan · 2021-09-27T11:25:43Z

I changed my carthage.sh to match Xcode 13 as @gotev suggested:

#!/bin/bash

# carthage.sh
# Usage example: ./carthage.sh build --platform iOS

set -euo pipefail

xcconfig=$(mktemp /tmp/static.xcconfig.XXXXXX)
trap 'rm -f "$xcconfig"' INT TERM HUP EXIT

# For Xcode 12 make sure EXCLUDED_ARCHS is set to arm architectures otherwise
# the build will fail on lipo due to duplicate architectures.

CURRENT_XCODE_VERSION=$(xcodebuild -version | grep "Build version" | cut -d' ' -f3)
echo "EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300__BUILD_$CURRENT_XCODE_VERSION = arm64 arm64e armv7 armv7s armv6 armv8" >> $xcconfig

echo 'EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300 = $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_simulator__NATIVE_ARCH_64_BIT_x86_64__XCODE_1300__BUILD_$(XCODE_PRODUCT_BUILD_VERSION))' >> $xcconfig
echo 'EXCLUDED_ARCHS = $(inherited) $(EXCLUDED_ARCHS__EFFECTIVE_PLATFORM_SUFFIX_$(EFFECTIVE_PLATFORM_SUFFIX)__NATIVE_ARCH_64_BIT_$(NATIVE_ARCH_64_BIT)__XCODE_$(XCODE_VERSION_MAJOR))' >> $xcconfig

export XCODE_XCCONFIG_FILE="$xcconfig"
/usr/local/bin/carthage "$@"

This worked for me on macOS 11.6 using Xcode Version 13.0 beta (13A5154h)

gotev · 2021-09-27T11:55:34Z

I also confirm it now works on xcode 13.0

oligazar · 2021-10-19T13:23:28Z

Tried the version of the script of @mkotzjan with Xcode 13.0 and getting " and getting: "The file “Cartfile.resolved” couldn’t be opened because there is no such file.".

Any ideas how to overcome this?

Failed to read file or folder at /Users/Admin/Development/elie/DuoTone/materials/ios/parts/duotone-academy-ios/Cartfile.resolved: Error Domain=NSCocoaErrorDomain Code=260 "The file “Cartfile.resolved” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Users/Admin/Development/elie/DuoTone/materials/ios/parts/duotone-academy-ios/Cartfile.resolved, NSUnderlyingError=0x7fe7bc426900 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}```

stale · 2022-01-09T08:59:55Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

command-tab · 2022-01-09T16:35:47Z

Poke

nrj · 2022-02-03T10:11:50Z

This is still an issue for me on an M1 Mac.

mkotzjan · 2022-02-03T11:38:38Z

This is still an issue for me on an M1 Mac.

@nrj I do not have a M1 for testing. Does the solution I posted before work for you? probably not since the architecture differs...

stale · 2022-04-16T11:03:57Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

gnachman · 2022-04-24T20:45:46Z

This is still happening. Should I commit to using the workaround script indefinitely? Based on the ongoing breakage and the lack of recent updates, I'm concerned that Carthage may be sunset soon. Is it a good idea to begin using it?

adamlaska · 2022-04-26T09:58:37Z

Отправлено из Yahoo Почты для Android сб, 16 апр. 2022 в 14:04 ***@***.***> написал(-а): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

nfranke · 2022-05-17T19:22:22Z

This is still a problem with a fresh install of Xcode 13 on ARM Macs.

gotev · 2022-05-17T20:02:53Z

Since my last post here, all the projects on which I'm working have been fully switched to SPM, so I sunsetted Carthage. A great experience so far with SPM. Specially from Swift 5.5 onwards, things have been vastly improved.

Carthage has been a huge part of my day by day for a long time and served its purpose very well, allowing me to have clean projects and to stick to apple standards more easily, without messing around. Carthage also made migration to SPM easier to do. A big thanks to this community and kudos to all the people which contributed to and runs this project.

nfranke · 2022-05-17T21:14:26Z

I later read the README that says "and require XCFrameworks when building on an Apple Silicon Mac" which does fix the issue (while causing others.)

alex-fos · 2023-09-14T20:07:18Z

Bye, Carthage! It was always a pain to use. Switching all projects to SwiftPM.

arielelkin mentioned this issue Mar 22, 2021

Carthage installation error pocketsvg/PocketSVG#190

Closed

DmitriyKirakosyan mentioned this issue Jun 8, 2021

Fix architecture issue when building on m1 for iOS simulator microsoft/plcrashreporter#185

Merged

3 tasks

code-gabriel added a commit to gamechanger/Moya that referenced this issue Jun 10, 2021

Add script to fix Carthage/Carthage#3146

0be9183

scannillo mentioned this issue Nov 1, 2021

Fix Carthage Release Steps for .Frameworks braintree/braintree_ios#752

Merged

stale bot added the stale label Jan 9, 2022

stale bot removed the stale label Jan 9, 2022

soapgu mentioned this issue Jan 18, 2022

RxSwift学习与第三方网络库RxAlamofire结合使用——（二） soapgu/PlayPen#101

Open

stale bot added the stale label Apr 16, 2022

stale bot removed the stale label Apr 24, 2022

brototyp mentioned this issue Oct 13, 2023

Carthage installation failed matomo-org/matomo-sdk-ios#440

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"Building universal frameworks with common architectures is not possible." error #3146

"Building universal frameworks with common architectures is not possible." error #3146

arielelkin commented Mar 12, 2021 •

edited

tmspzz commented Mar 15, 2021

arielelkin commented Mar 15, 2021

arielelkin commented Mar 22, 2021

tmspzz commented Mar 22, 2021

command-tab commented Apr 2, 2021 •

edited

kmpnz commented Apr 7, 2021

Rolando-Barbella commented Apr 13, 2021 •

edited

byzeagle commented Apr 14, 2021

dbmrq commented Apr 18, 2021

Rolando-Barbella commented Apr 18, 2021

dbmrq commented Apr 18, 2021

nfranke commented May 4, 2021

springlo commented Jun 2, 2021 •

edited

gotev commented Jun 9, 2021 •

edited

mkotzjan commented Sep 27, 2021

gotev commented Sep 27, 2021

oligazar commented Oct 19, 2021 •

edited

stale bot commented Jan 9, 2022

command-tab commented Jan 9, 2022

nrj commented Feb 3, 2022

mkotzjan commented Feb 3, 2022 •

edited

stale bot commented Apr 16, 2022

gnachman commented Apr 24, 2022

adamlaska commented Apr 26, 2022 via email

nfranke commented May 17, 2022

gotev commented May 17, 2022

nfranke commented May 17, 2022

alex-fos commented Sep 14, 2023

"Building universal frameworks with common architectures is not possible." error #3146

"Building universal frameworks with common architectures is not possible." error #3146

Comments

arielelkin commented Mar 12, 2021 • edited

tmspzz commented Mar 15, 2021

arielelkin commented Mar 15, 2021

arielelkin commented Mar 22, 2021

tmspzz commented Mar 22, 2021

command-tab commented Apr 2, 2021 • edited

kmpnz commented Apr 7, 2021

Rolando-Barbella commented Apr 13, 2021 • edited

byzeagle commented Apr 14, 2021

dbmrq commented Apr 18, 2021

Rolando-Barbella commented Apr 18, 2021

dbmrq commented Apr 18, 2021

nfranke commented May 4, 2021

springlo commented Jun 2, 2021 • edited

gotev commented Jun 9, 2021 • edited

mkotzjan commented Sep 27, 2021

gotev commented Sep 27, 2021

oligazar commented Oct 19, 2021 • edited

stale bot commented Jan 9, 2022

command-tab commented Jan 9, 2022

nrj commented Feb 3, 2022

mkotzjan commented Feb 3, 2022 • edited

stale bot commented Apr 16, 2022

gnachman commented Apr 24, 2022

adamlaska commented Apr 26, 2022 via email

nfranke commented May 17, 2022

gotev commented May 17, 2022

nfranke commented May 17, 2022

alex-fos commented Sep 14, 2023

arielelkin commented Mar 12, 2021 •

edited

command-tab commented Apr 2, 2021 •

edited

Rolando-Barbella commented Apr 13, 2021 •

edited

springlo commented Jun 2, 2021 •

edited

gotev commented Jun 9, 2021 •

edited

oligazar commented Oct 19, 2021 •

edited

mkotzjan commented Feb 3, 2022 •

edited