Xcode 12 building for iOS Simulator but linking in object file built for iOS for architecture arm64

Question

Trying to get a large  and working on Xcode 11   project building in Xcode 12  beta 5  to prep for iOS 14   Codebase was previously Obj-C  but now contains both Obj-C and Swift  and uses pods that are Obj-C and or Swift as well  I have pulled the new beta of cocoapods with Xcode 12 support  currently 1 10 0 beta 2   Pod install is successful   When I do a build  I get the following error on a pod framework   quot building for iOS Simulator  but linking in object file built for iOS  for architecture arm64 quot  When I go run lipo -info on the framework  it has  armv7s armv7 i386 x86 64 arm64  Previously  the project had Valid Architectures set to  armv7  armv7s and arm64  In Xcode 12  that setting goes away  as per Apple s documentation   Architectures is set to   ARCHS STANDARD    I have nothing set in excluded architectures  Anyone have an idea of what may be going on here   I have not been able to reproduce this with a simpler project yet

User · Answer

Switch Build Configuration back to Debug mode or turn on Build Active Architecture Only for both Debug and Release mode  The reason is your library framework doesn t support new Simulator architecture ARM64  run on Mac with Apple Silicon processor

User · Answer

Found a solution   https   developer apple com forums thread 657913 If you set excluded architectures for the simulator to arm64 it will compile

User · Answer

Xcode 12 Removing VALID ARCH from Build settings under User-Defined group work for me

User · Answer

Please  don t forget to clean the build folder after you add arm64 to excluded architecture

User · Answer

It worked for me when I set   ARCHS STANDARD  for VALID ARCHS for Debug for Any iOS Simulator SDK  Also I have set YES for ONLY ACTIVE ARCH for Debug

User · Answer

Basically you have to exclude arm64 for simulator architecture both from your project and the Pod project   To do that  navigate to Build Settings of your project and add Any iOS Simulator SDK with value arm64 inside Excluded Architecture     OR  If you are using custom XCConfig files  you can simply add this line for excluding simulator architecture   EXCLUDED ARCHS sdk iphonesimulator     arm64  Then You have to do the same for the Pod project until all the cocoa pod vendors are done adding following in their Podspec  s pod target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64    s user target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64     You can manually add the Excluded Architechure in your Pod project s Build Settings  but it will be overwritten when you use pod install  In place of this  you can add this snippet in your Podfile  It will write the neccessary Build Settings every time you run pod install post install do  installer    installer pods project build configurations each do  config      config build settings  quot EXCLUDED ARCHS sdk iphonesimulator   quot      quot arm64 quot    end end

User · Answer

In my case  Xcode 12 I set empty values on EXCLUDED ARCHS and set ONLY ACTIVE ARCH Debug   YES Release   NO Project s Build Setting and I included this in my Podfile  post install do  installer      installer pods project targets each do  target          target build configurations each do  config              config build settings  quot EXCLUDED ARCHS sdk iphonesimulator   quot      quot arm64 quot          end     end end  It runs on my Simulator iPhone 8  iOS 12  and iPhone 11 Pro Max  iOS 14  and on my device iPhone 7 Plus  iOS 13 4

User · Answer

I was also experiencing the same issue with specific library that was installed through carthage  For those who are using Carthage  as Carthage doesn t work out of the box with Xcode 12  this document will guide through a workaround that works for most cases  Well  shortly  Carthage builds fat frameworks  which means that the framework contains binaries for all supported architectures  Until Apple Sillicon was introduced it all worked just fine  but now there is a conflict as there are duplicate architectures  arm64 for devices and arm64 for simulator   This means that Carthage cannot link architecture specific frameworks to a single fat framework  You can follow the instruction here  Carthage XCODE 12 Then after you configure the Carthage  Put the arm64 in the  quot Excluded Architectures quot  on build settings   Try to run your project using simulator  Simulator should run without any errors

User · Answer

For Pod Developers In your Podspec  add  s pod target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64    s user target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64     Then in your sample project  See it working in this project

User · Answer

After trying almost every post on this thread and reading through apple developer forums I found only one solution worked for me  I am building a universal framework that is consumed in a swift app  I was unable to build to the Simulator without architecture errors  In my Framework project I have a Universal Framework task in my build phases  if this is the case for you  Add the following to your xcodebuild task inside the build phase  EXCLUDED ARCHS  quot arm64 quot   Next you have to change the following project Build Settings   Delete the VALID ARCHS user defined setting Set ONLY ACTIVE ARCH to YES          If you are developing a framework and have a demo app as well  this setting has to be turned on in both projects

User · Answer

Xcode 12 3 I solved this problem by setting Validate Workspace to Yes

User · Answer

In you xxx framework podspec file add follow config avoid pod package contains arm64 similator archs s pod target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64    s user target xcconfig      EXCLUDED ARCHS sdk iphonesimulator      gt   arm64

User · Answer

In my case  I had 4 configurations   DebugQa and ReleaseQa  Cocoapods is used as a dependency Manager For Debug  I gathered on the device and in the simulator  and on qa only on the device  It helped to set BuildActiveArchitecture to yes in PodsProject

User · Answer

After excluding arm64 I always got ARCHS     unbound variable  For me the only solution was to add x86 64 to the target build setting as mentioned here Problems after upgrading to Xcode 12 ld  building for iOS Simulator  but linking in dylib built for iOS  architecture arm64 You also might remove the exclude arm64 you added before

User · Answer

I was having issues building frameworks from the command line  My framework depends on other frameworks that were missing support for ARM-based simulators  I ended up excluding support for ARM-based simulators until I upgrade my dependencies  I needed the EXCLUDED ARCHS arm64 flag when building the framework for simulators from CLI  xcodebuild archive -project  project  -scheme  scheme  -destination  quot generic platform iOS Simulator quot  -archivePath  quot archives  scheme -iOS-Simulator quot  SKIP INSTALL NO BUILD LIBRARY FOR DISTRIBUTION YES EXCLUDED ARCHS arm64

User · Answer

To get this working for Calabash automated tests There is a pull request up to fix the issue of xcode 12 not working with calabash https   github com calabash run loop pull 757 A temporary solution is to use this WIP branch  although it is not great to have to use this as it is a draft PR  Xcode 12 support for Calabash will hopefully come in the future  Change in your Gemfile gem  quot run loop quot   to gem  run loop   git   https   github com calabash run loop git   branch   xcode 14 support

User · Answer

After trying a lot useless answers online  This works for me  First  generates x86 64 for Pod projects     post install do  installer      installer pods project targets each do  target          target build configurations each do  config              config build settings  ARCHS      quot arm64 x86 64 quot          end     end end  Second  add  quot x86 64 quot  for VALID ARCHS

User · Answer

Updates  Oct 2020 You can simply set arm64 only for Debug  gt  Simulator - iOS 14 O SDK under Excluded Architecture

User · Answer

I believe I found the answer   Per the Xcode 12 beta 6 release notes   quot The Build Settings editor no longer includes the Valid Architectures build setting  VALID ARCHS   and its use is discouraged  Instead  there is a new Excluded Architectures build setting  EXCLUDED ARCHS   If a project includes VALID ARCHS  the setting is displayed in the User-Defined section of the Build Settings editor   15145028  quot  I was able to resolve this issue by manually editing the project file  I could not figure out how to remove the item from the project file using Xcode  and removing all lines referring to VALID ARCHS   After that  I am able to build for the simulator fine

User · Answer

1 Add arm64 to Build settings - gt  Exclude Architecture in all the targets   2 Close Xcode and follow the steps below to open  Right-click on Xcode in Finder Get Info Open with Rosetta

User · Answer

In my case I was trying to run on an watchOS 7 simulator in Relese mode but the iOS 14 simulator was in Debug mode  So simply putting both sims in Debug Release mode solved the problem for me

User · Answer

After upgrading to Xcode 12 I was still able to build for a real device  but not the simulator  The Podfile build was working only for the real device  I deleted VALID ARCHS under Build Settings  gt  User-Defined and it worked  Bashing my head for some time before finding this

User · Answer

I realise this question is a little old  but the proposed answers are outdated incorrect  You should initially try to update both CocoaPods and the dependencies for your library app  and then  if that doesn t work  contact the vendors of any dependencies you are using to see if they have an update in progress to add support for arm64 Simulator slices on M1 Macs  There are a lot of answers on here marked as correct suggesting that you should exclude arm64 from the list of supported architectures  This is at best a very temporary workaround  and at worst it will spread this issue to other consumers of your libraries  If you exclude the arm64 Simulator slice  there will be performance impacts on apps that you re developing in the Simulator  which in turn can lead to reduced battery time for your shiny new M1 kit while you re developing your amazing ideas

User · Answer

Set the  quot Build Active Architecture Only quot  ONLY ACTIVE ARCH  build setting to yes  xcode is asking for arm64 because of Silicon MAC architecture which is arm64  arm64 has been added as simulator arch in Xcode12 to support Silicon MAC    Applications Xcode app Contents Developer Platforms iPhoneSimulator platform Developer SDKs iPhoneSimulator sdk SDKSettings json

User · Answer

Add line  quot arm64 quot   without quotes  to path  Xcode - gt  Project - gt  Build settings - gt  Architectures - gt  Excluded architectures Also  do the same for Pods  In both cases for both debug and release fields  or in detail    Errors mentioned here while deploying to simulator using Xcode 12 are also one of the things which have affected me  Just right-clicking on each of my projects and showing in finder  opening the  xcodeproj in Atom  then going through the  pbxproj and removing all of the VALIDARCHS settings  This was is what got it working for me  Tried a few of the other suggestions  excluding arm64  Build Active Architecture Only  which seemed to get my build further but ultimately leave me at another error  Having VALIDARCH settings lying around is probably the best thing to check for first

User · Answer

I understand the issue with arm64 and Xcode 12 and I was able to resolve build issues by excluding the arm64 architecture for iPhone Simulator or by setting ONLY ACTIVE ARCH for Release scheme  However I still have problems to push my framework using pod repo push  I found out that setting s pod target xcconfig in my podspec does not apply this setting to dependencies defined in the same podspec  I can see it in the dummy App project that Cocoapods is generating during the validation  Cocoapods validation is running release scheme for simulator and this is failing when one or more dependencies doesn t exclude arm64 or is not set to build active architecture only  A solution could be to force Cocoapods to add post install script while validating the project or let it build Debug scheme  because the Debug scheme is only building active architecture  I ended up using Xcode 11 to release my pod to pass the validation  You can download Xcode 11 from developer apple com  copy it to Applications folder as Xcode11 app and switch using sudo xcode-select --switch  Applications Xcode11 app Contents Developer  Don t forget to switch back when done

User · Answer

TL DR  Set  quot Build Active Architecture Only  ONLY ACTIVE ARCH  quot  to Yes for your libraries apps  even for release mode   While trying to identify the root cause of the issue I realized some fun facts about Xcode 12   Xcode 12 is actually the stepping stone for Apple Silicon which unfortunately is not yet available  when the answer was written   But with that platform we are gonna get arm64 based macOS where simulators will also run on arm64 architecture unlike the present Intel based x86 64 architecture   Xcode usually depends on the  quot Run Destination quot  to build its libraries apps  So when a simulator is chosen as the  quot Run Destination quot   it builds the app for available simulator architectures and when a device is chosen as the  quot Run Destination quot  it builds for the architecture that the device supports  arm     xcodebuild  in the Xcode 12  build system considers arm64 as a valid architecture for simulator to support Apple Silicon  So when a simulator is chosen as the run destination  it can potentially try to compile link your libs apps against arm64 based simulators  as well  So it sends clang     some -target flag like arm64-apple-ios13 0-simulator in  lt architecture gt - lt os gt - lt sdk gt - lt destination gt  format and clang tries to build link against arm64 based simulator that eventually fails on Intel based mac   But xcodebuild tries this only for Release builds  Why  Because   quot Build Active Architecture Only  ONLY ACTIVE ARCH  quot  build settings is usually set to  quot No quot  for the  quot Release quot  configuration only  And that means xcodebuild will try to build all architectural variants of your libs apps for the selected run destination for release builds  And for the Simulator run destination  it will includes both x86 64 and arm64 now on  since arm64 in Xcode 12  is also a supported architecture for simulators to support Apple Silicon    Simply putting  Xcode will fail to build your app anytime it tries the command line  xcodebuild   which defaults to release build  see the general tab of your project setting  or otherwise and tries to build all architectural variants supported by the run destination  So a simple workaround to this issue is to set  quot Build Active Architecture Only  ONLY ACTIVE ARCH  quot  to Yes in your libraries apps  even for release mode    If the libraries are included as Pods and you have access to  podspec you can simply set   spec pod target xcconfig      ONLY ACTIVE ARCH    gt   YES      spec user target xcconfig      ONLY ACTIVE ARCH    gt   YES      not recommended  I personally don t like the second line since pods shouldn t pollute the target project and it could be overridden in the target settings  itself  So it should be the responsibility of the consumer project to override the setting by some means  However  this could be necessary for successful linting of podspecs  However  if you don t have access to the  podspec  you can always update the settings during installation of the pods  post install do  installer    installer pods project targets each do  target      target build configurations each do  config        config build settings  quot ONLY ACTIVE ARCH quot      quot YES quot      end   end end  One thing I was concerned about that what will be the impact of this when we actually archive the libs apps  During archiving apps usually take the  quot Release quot  configuration and since this will be creating a release build considering only the active architecture of the current run destination  with this approach  we may lose the slices for armv7  armv7s  etc from target build  However  I noticed the documentation says  highlighted in the attached picture  that this setting will be ignored when we choose  quot Generic iOS Device Any Device quot  as the run destination  since it doesn t define any specific architecture  So I guess we should be good if we archive our app choosing that as a run destination

User · Answer

Sharing the solution which worked for me  which may help someone Issue when compiling for simulator   building for iOS Simulator  but linking in object file built for iOS  for architecture arm64  XCODE 12 1  POD 1 9 1  My Project structure  Main Target Share Extension Notifiction service extension Submodule  Custom Framework Podfile   Add arm64 to Build settings - gt  Exclude Architecture in all the targets     Removed arm64 from VALID ARCHS and added x86 64 in all the targets     Add following code in podfile post install do  installer      installer pods project build configurations each do  config      config build settings  quot EXCLUDED ARCHS sdk iphonesimulator   quot      quot arm64 quot   end end   Did pod update  deleted podfile lock  and did pod install  Do clean build

User · Answer

I solve problem by adding  quot arm64 quot  in  quot Excluded Architectures quot  for both project target and pod target  Xcode - gt  Target Project - gt  Build Setting - gt  Excluded Architectures  gt   quot arm64 quot  Xcode - gt  Pod Target - gt  Build Setting - gt  Excluded Architectures  gt   quot arm64 quot

User · Answer

After trying and searching different solutions  I think the most safest way is adding the following code at the end of the Podfile post install do  pi     pi pods project targets each do  t         t build configurations each do  bc            bc build settings  ARCHS sdk iphonesimulator         uname -m         end    end end  This way you only override the iOS simulator s compiler architecture as your current cpu s architecture  Compared to others  this solution will also work on computers with Apple Silicon

User · Answer

If you have trouble in Xcode 12 with simulators  not real device  yes you have to remove VALID ARCHS settings because it s not supported anymore  Go to  quot builds settings quot   search  quot VALID ARCHS quot  and remove the user-defined properties  Do it in every target you have  Still  you may need to add a script at the bottom of your podfile to have pods compiling with the right architecture and deployment target   post install do  installer    installer pods project targets each do  target      target build configurations each do  config        config build settings delete  IPHONEOS DEPLOYMENT TARGET        config build settings  ONLY ACTIVE ARCH      NO       end   end end

User · Answer

The Valid Architectures build setting has been removed in Xcode 12   If you had values in this build setting  they re causing a problem and need to be removed  I was able to  quot clear out quot  the VALID ARCHS build setting by adding it back in as a User-Defined build setting  with no values   running the project  which failed   and then deleting the VALID ARCHS build setting   After that  I was able to run on the simulator  My Architectures build setting is Standard Architectures  You can add a User-Defined Setting from the plus button in Build Settings

User · Answer

The problem here are the Valid architectures in Xcode 11  open the project in Xcode 11 and change the Valid architectures value to   ARCHS STANDARD  for both your project  target and Pods  re-open the project in Xcode 12 and build

User · Answer

For me the following setting worked  Build Settings  gt  gt  Excluded Architectures added  quot arm64 quot  to both Release and Debug mode for  quot Any iOS Simulator SDK quot  option

User · Answer

Only add Any iOS Simulator SDK - gt  x86 64 to Project s Build Settings - gt  VALID ARCHS works for me  Xcode version  12 1  12A7403   If your project includes some frameworks that don t support x86 64   You can add these framework names xxx framework  to Target - gt  Build Settings - gt  Excluded Source File Names - gt  Debug - gt  Any iOS Simulator SDK  And then modify the Framework Search Paths to delete the paths of these frameworks for Debug - gt  Any iOS Simulator SDK   These two settings can avoid Xcode to build and link these frameworks on simulator mode

User · Answer

On Build Settings search VALID ARCH then press delete  This should work for me with Xcode 12 0 1

User · Answer

I found that  Using Rosetta  Find Xcode in Finder  gt  Get Info  gt  Open using Rosetta  Build Active Architecture Only set to YES for everything  in both Project and Target And including this in the podfile   post install do  installer    installer pods project targets each do  target      target build configurations each do  config        config build settings  quot ONLY ACTIVE ARCH quot      quot YES quot      end   end end  worked for me  We had both Pods and SPM and they didn t work with any of the combinations of other answers  My colleagues all use Intel MacBooks and we haven t tested this config on their computers  though

[ios] Xcode 12, building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

Examples related to ios

Examples related to xcode

Examples related to xcode12

Examples related to xcode12beta5

Examples related to xcode12beta6