realm-swift: Can't run project with RealmSwift in iOS simulator after building with Xcode 12 (after beta 3)

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is : Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS). So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined. So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates. So somewhere I found this post pod installation change but I have not tried that yet. ref: https://developer.apple.com/forums/thread/656509

post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

As Xcode 12 is GM seed now and release is expected in hours perspective it seem the right time to revive the topic.

ProductName:	Mac OS X
ProductVersion:	10.15.6
BuildVersion:	19G2021

/Applications/Xcode.app/Contents/Developer
Xcode 12.0
Build version 12A7209

/Users/illabo/.rbenv/shims/pod
1.10.0.rc.1
Realm (5.4.0)
RealmSwift (5.4.0)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin19)

carthage not found
(not in use here)

/usr/local/bin/git
git version 2.28.0

Cocoapods 1.10 (at least rc 1) doesn’t remedy this issue no matter Pods Project Base SDK and/or Supported Platform is set to macOS or iOS, Build Active Architectures Only is set to Yes for debug or to No, i386 is in Excluded Architectures or it isn’t. What steps one should take to try mitigate such an issue? BTW: tried building older project with Realm 3.17.3 and it runs in iOS 14 simulator without any problem.

Xcode 12 is not beta anymore, its oficial release and the problem persists. its not compiling anymore.

Not sure if this is happening for everyone, but for us this is becoming an increasingly time-sensitive situation — iOS 14 is coming out very soon, and we’re not able to compile our app on simulators at all right now due to this issue.

Is the realm team looking into this issue or aware of what may be causing this? cc @tgoyne

@tgoyne Sorry to say, but it isn’t a solution. Whenever the project is attempted to be built for debug in simulator (main project and Pods targets architectures are set to ARCHS_STANDARD) excluding arm64 and i386 architectures it can’t be linked as there aren’t anything actually built:

None of the architectures in ARCHS (arm64, i386, x86_64) are valid. Consider setting ARCHS to $(ARCHS_STANDARD) or updating it to include at least one value from VALID_ARCHS (armv7, arm64) which is not in EXCLUDED_ARCHS (arm64, i386).

And I’m trying with no success to run the project on old simulators (10.3.1—13.6) not only 14.0, seems Xcode 12 treat them as arm64 simulators too for some reason. E.g. it is an error I’m getting trying to run on iOS 12.1 (when arm64 isn’t excluded): could not find module 'RealmSwift' for target 'arm64-apple-ios-simulator'. Please check the last two bullets in “Actual Results” section in original issue. This mutually exceptional messages (saying a simulator could run x86 binary but Xcode can’t find arm64 module) are present only when the project imports Realm. It is the reason to file this issue and not just wait for release of production ready Xcode 12. Build Active Architecture Only: Yes not helping also on my Intel Mac whether I exclude arm64 from build archs or not. I can understand this happens because of Apple tweaked the build system, but it is a coming reality to deal with. Unfortunately it seems the time for new ‘hack’ to force-feed simulator with the correct binary and resolve this contradiction. For now I can perfectly fall back to building with Xcode 11, but I have some worries regarding upcoming releases.

Not sure if this is happening for everyone, but for us this is becoming an increasingly time-sensitive situation — iOS 14 is coming out very soon, and we’re not able to compile our app on simulators at all right now due to this issue.

Is the realm team looking into this issue or aware of what may be causing this? cc @tgoyne

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is : Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS). So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined. So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates. So somewhere I found this post pod installation change but I have not tried that yet. ref: https://developer.apple.com/forums/thread/656509

post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

In my case applying this as is broke several other Pods, but was otherwise helpful when just restricted to Realm Pods:

post_install do |installer|
      installer.pods_project.targets.each do |target|
+            if target.name.include?('Realm')
                target.build_configurations.each do |config|
                      config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
                end
+            end
      end
end

When using CocoaPods you will also need to set EXCLUDED_ARCHS on the Pods project.

Supporting the arm simulators requires cocoapods 1.10, which currently is in beta. If they don’t make a non-beta release before Xcode 12 leaves beta then I guess we’ll just bump the minimum req to that anyway, but we’d prefer not to require everyone working on things being released now to use a beta version.

We do not support the new arm64 simulators yet as they break the old “universal” simulator/device libraries hack. Currently you’ll need to exclude arm64 from the simulator architectures:

Build Active Architecture Only: Yes should also sidestep this unless you’re running on an ARM DTK, as that’s the only place the arm64 simulator is actually used.

For SwiftPM, use Realm version 10.5.0.

Anyone has this issue right now?

Every time I tried ‘pod lib lint’ and this is always the error ~/Pods/Realm/core/librealmcore-ios.a(bptree.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

The following build commands failed: Ld /Users/~/Library/Developer/Xcode/DerivedData/App-bcahkoasabrxnhbthdoimxoxletm/Build/Intermediates.noindex/Pods.build/Release-iphonesimulator/Realm.build/Objects-normal/arm64/Binary/Realm normal arm64 (1 failure)

1. I’ve added exclusion for arm64 on all my targets
2. I’ve set ‘ONLY_ACTIVE_ARCH’ to yes to both Debug and Release on all my targets
3. I’ve added both exclusion for arm64 and ONLY_ACTIVE_ARCH in podfile in post install
4. I’ve added the following code to my podspec s.user_target_xcconfig = { ‘EXCLUDED_ARCHS[sdk=iphonesimulator*]’ => ‘arm64’ } s.user_target_xcconfig = { ‘ONLY_ACTIVE_ARCH’ => ‘YES’ } s.pod_target_xcconfig = { ‘EXCLUDED_ARCHS[sdk=iphonesimulator*]’ => ‘arm64’ } s.pod_target_xcconfig = { ‘ONLY_ACTIVE_ARCH’ => ‘YES’ }
5. I’ve checked and there is no VALID_ARCH setting in my build setting

And yet I still cannot pass pod lib lint

Xcode: 12.2 Pod: 1.10.0 Realm: 3.21.0 RealmSwift: 3.21.0

@tgoyne we’re seeing a very similar issue. We’re not attempting to use RealmSwift at all, just realm-cocoa. Tried excluding arm64 to no avail:

The error is:

ld: in /.../Pods/Realm/core/librealmcore-ios.a(bptree.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

Builds properly on a real device, just not on the simulator. Laptop has processor 2.9 GHz 6-Core Intel Core i9 running Catalina 10.15.6 (19G73). Let me know if there’s any additional info about our build settings, Podfile, hardware etc. that would be helpful in debugging.

I have an MacBook Air M1, What do you suggest if I include Realm using Swift Package Manager?

BUILD Settings -> VALID_ARCHS. add “X86_64” on your project (Prolly you might have arm* series. put it with them to work)

Here is how I got rid of the problem, I bet this can not be termed as long term solution but the interesting thing is : Xcode 11 had Valid Architecture(VALID_ARCHS) while Xcode 12 has Excluded Architectures (EXCLUDED_ARCHS). So if you open the project in xcode12 then if you check-in build settings you will found that VALID_ARCHS is now moved to User-Defined. So a quick solution will simply delete the entry of VALID_ARCHS from User-Defined. And this time it should work. I am also looking for a more permanent kind of solution as this solution will break every time we perform pod install or pod updates. So somewhere I found this post pod installation change but I have not tried that yet. ref: https://developer.apple.com/forums/thread/656509

post_install do |installer|
    installer.pods_project.targets.each do |target|
          target.build_configurations.each do |config|
                config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
          end
    end
end

Please try and let me know if it helps

I tried this too and it worked great

The latest Realm version 10.4.0 has fixed the arm64-apple-ios-simulator compiler issue for me. My workaround in #6968 should no longer be necessary.

Update: The following workaround is no longer required in Realm version 10.4.0

I’ve encountered the same issue in #6968. The Realm project excludes the arm64 architecture when building for the iOS simulator. Please change the following line in your Realm project https://github.com/realm/realm-cocoa/blob/af4b201bb955736f250f5af1c1b6bc335a43c385/Configuration/Base.xcconfig#L65 to REALM_ARM_ARCHS_1200 = ; and build again with sh build.sh xcframework ios

Hi @danielrobleM, yes I`ve resolved the issue. In my case the following steps works:

1. add following code to post_install section of your podfile:

post_install do |installer|
installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64'
      end
    end
end

1. open your project settings and manually for each of your targets set Excluded Architectures setting (in my case I have two targets - main and push notification extension). Check this screenshot

@umang-simform Thank you! The Podfile snippet seems to help in our case.