Build fails with XCode 26 on ARM64

[AdrienPoupa]

We've updated to 2.0.3 and while we're able to build our project locally on XCode 26.0.1, it fails in GitHub Actions:

2025-10-27T00:07:19.0216240Z ld: warning: Could not find or use auto-linked library 'swiftCompatibility56': library 'swiftCompatibility56' not found
2025-10-27T00:07:19.0318870Z ld: warning: Could not find or use auto-linked library 'swiftCompatibilityPacks': library 'swiftCompatibilityPacks' not found
2025-10-27T00:07:19.0421100Z ld: warning: Could not find or use auto-linked framework 'UIUtilities': framework 'UIUtilities' not found
2025-10-27T00:07:19.0523940Z ld: warning: Could not parse or use implicit file '/Applications/Xcode_26.0.1.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/Frameworks/SwiftUICore.framework/SwiftUICore.tbd': cannot link directly with 'SwiftUICore' because product being built is not an allowed client of it
2025-10-27T00:07:19.0626250Z Undefined symbols for architecture arm64:
2025-10-27T00:07:19.0728130Z   "__swift_FORCE_LOAD_$_swiftCompatibility56", referenced from:
2025-10-27T00:07:19.0830070Z       __swift_FORCE_LOAD_$_swiftCompatibility56_$_IterableAppExtensions in IterableAppExtensions[4](ITBNotificationServiceExtension.o)
2025-10-27T00:07:19.0900810Z ld: symbol(s) not found for architecture arm64
2025-10-27T00:07:19.1004000Z clang: error: linker command failed with exit code 1 (use -v to see invocation)

We've tried using MacOS 26 runners with XCode 26.0.1 with no success. Any idea what is going on? It works fine when using XCode 16.4.

I have tried the suggestion to use dynamic linking in Cocoapods, but not only is it much slower than dynamic linking, it errors out on a different dependency, so I'm not sure it's the right solution: [!] The 'app' target has transitive dependencies that include statically linked binaries: (/Users/runner/work/app/native/ios/Pods/GoogleMaps/Base/Frameworks/GoogleMapsBase.xcframework, /Users/runner/work/app/native/ios/Pods/GoogleMaps/Maps/Frameworks/GoogleMaps.xcframework, and /Users/runner/work/app/native/ios/Pods/GoogleMaps/Maps/Frameworks/GoogleMapsCore.xcframework)

[lposen]

@AdrienPoupa -- we're actively looking into this. Unfortunately, XCode removed a lot of their base tooling in 26.x, so we have run into several issues since they released 26. I'll circle back when I have a solution.

Side note: if/when you update Iterables RN SDK to 2.1.0, you actually have to use dynamic linking for our libraries. However, you can confine it to just our libraries by doing the following in your podfile:

	pod 'Iterable-iOS-SDK', :linkage => :dynamic
 	pod 'Iterable-iOS-AppExtensions', :linkage => :dynamic

[lposen]

@AdrienPoupa -- for clarity, does this run properly outside of github actions?

IE: Does compile properly when you do the following in your terminal:

npx react-native start --reset-cache
## new tab
npx react-native run-ios

[dazlious]

We combined the dynamic linking with installing cocoapods-pod-linkage and we still get

Cycle in dependencies between targets 'Iterable-iOS-SDK' and 'Iterable-iOS-SDK-Resources'; building could produce unreliable results.
Cycle path: Iterable-iOS-SDK → Iterable-iOS-SDK-Resources → Iterable-iOS-SDK
Cycle details:
→ Target 'Iterable-iOS-SDK' has an explicit dependency on Target 'Iterable-iOS-SDK-Resources'
→ Target 'Iterable-iOS-SDK-Resources' has an implicit dependency on Target 'Iterable-iOS-SDK' because 'Iterable-iOS-SDK-Resources' defines the option '-lIterable-iOS-SDK' in the build setting 'OTHER_LDFLAGS'

[AdrienPoupa]

I did not have the time to come back to this, but I wonder if this would help: xcodebuild -downloadComponent MetalToolchain see actions/runner-images#13080

[lposen]

@dazlious @AdrienPoupa -- I'd just like to confirm, is this happening in Github Actions? If so, are you able to run it successfully on your computer using XCode or yarn ios?

[AdrienPoupa]

@dazlious @AdrienPoupa -- I'd just like to confirm, is this happening in Github Actions? If so, are you able to run it successfully on your computer using XCode or yarn ios?

Yes, local build is working but not GitHub Actions.

[lposen]

@AdrienPoupa Unfortunately, it sounds like this is an issue with Github's Xcode image. Below are two potential workarounds.

Option 1: Force-install the missing components in the workflow (Recommended)

- name: Install missing Xcode components
  run: |
    sudo xcodebuild -downloadComponent MetalToolchain
    sudo xcodebuild -runFirstLaunch

Option 2: Use an earlier / different Xcode on CI

runs-on: macos-15

steps:
  - uses: maxim-lobanov/setup-xcode@v1
    with:
      xcode-version: '16.4'

Let me know if this works. You're the first person to report this, but I'm sure you won't be the last!

[pbryl]

@AdrienPoupa -- we're actively looking into this. Unfortunately, XCode removed a lot of their base tooling in 26.x, so we have run into several issues since they released 26. I'll circle back when I have a solution.

Side note: if/when you update Iterables RN SDK to 2.1.0, you actually have to use dynamic linking for our libraries. However, you can confine it to just our libraries by doing the following in your podfile:

pod 'Iterable-iOS-SDK', :linkage => :dynamic
pod 'Iterable-iOS-AppExtensions', :linkage => :dynamic

are you sure that linkage works well now?

you will get:
[!] Unknown external source parameters for Iterable-iOS-SDK: {linkage: :dynamic}
[!] Unknown external source parameters for Iterable-iOS-AppExtensions: {linkage: :dynamic}

so if you have to use:
use_frameworks! :linkage => :static

you will have:
node_modules/@iterable/react-native-sdk/ios/RNIterableAPI/RNIterableAPI.mm:20:9: fatal error: 'Iterable_React_Native_SDK-Swift.h' file not found
20 | #import "Iterable_React_Native_SDK-Swift.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~