Ambiguous use of 'performAndWait'

[nasmithan]

Expo EAS builds started failing last week, same error from: Iterable/iterable-swift-sdk#945

Looks like the pod dependency needs updated in react-native-sdk?

[nasmithan]

Attempted to override the podfile:

[!] CocoaPods could not find compatible versions for pod "Iterable-iOS-SDK":
  In Podfile:
    Iterable-React-Native-SDK (from `../node_modules/@iterable/react-native-sdk`) was resolved to 2.0.2, which depends on
      Iterable-iOS-SDK (= 6.5.4)
    Iterable-iOS-SDK (= 6.6.1)
Specs satisfying the `Iterable-iOS-SDK (= 6.6.1), Iterable-iOS-SDK (= 6.5.4)` dependency were found, but they required a higher minimum deployment target.

[ccdwyer]

@nasmithan I was able to get past this (temporarily) by updating this line to require version 6.6.1, deleting my podfile.lock, and reinstalling pods.

[sam23796]

@ccdwyer We are still running into an issue even with patching the specs to use 6.6.1. During build it runs into the following error. Did you run into anything similar?

type 'ReactIterableAPI' does not conform to protocol 'IterableAuthDelegate'

[ccdwyer]

@ccdwyer We are still running into an issue even with patching the specs to use 6.6.1. During build it runs into the following error. Did you run into anything similar?

type 'ReactIterableAPI' does not conform to protocol 'IterableAuthDelegate'

Hm, I didn't see that -- I'm on Expo 52 currently, building on a mac running 26.0 (25A354).

Edit: Actually I did fix that, I just didn't even remember doing it:

    func onAuthFailure(_ authFailure: IterableSDK.AuthFailure) {
        // Do nothing
    }

I just added this function to extension ReactIterableAPI: IterableAuthDelegate {

[sam23796]

Thanks a lot @ccdwyer! Also on expo 52 but just saw your reply. Indeed we also had to apply a similar patch on the ReactIterableAPI!

[eppisapiafsl]

We are also encountering this issue when building our project using Xcode 26. Specifically, the following error appears:

ios/Pods/Iterable-iOS-SDK/swift-sdk/Internal/IterableCoreDataPersistence.swift:189:34: error: ambiguous use of 'performAndWait'

Could you provide insight into where Xcode 26 support currently stands on your roadmap?

[nasmithan]

I fixed this by patching the package: patches/@iterable+react-native-sdk+2.0.2.patch

diff --git a/node_modules/@iterable/react-native-sdk/Iterable-React-Native-SDK.podspec b/node_modules/@iterable/react-native-sdk/Iterable-React-Native-SDK.podspec
index 14c6d59..c549388 100644
--- a/node_modules/@iterable/react-native-sdk/Iterable-React-Native-SDK.podspec
+++ b/node_modules/@iterable/react-native-sdk/Iterable-React-Native-SDK.podspec
@@ -39,6 +39,6 @@ Pod::Spec.new do |s|
     end
   end

-  s.dependency "Iterable-iOS-SDK", "6.5.4"
+  s.dependency "Iterable-iOS-SDK", "6.6.1"

 end
diff --git a/node_modules/@iterable/react-native-sdk/ios/RNIterableAPI/ReactIterableAPI.swift b/node_modules/@iterable/react-native-sdk/ios/RNIterableAPI/ReactIterableAPI.swift
index 4db314f..2dcb478 100644
--- a/node_modules/@iterable/react-native-sdk/ios/RNIterableAPI/ReactIterableAPI.swift
+++ b/node_modules/@iterable/react-native-sdk/ios/RNIterableAPI/ReactIterableAPI.swift
@@ -680,6 +680,13 @@ extension ReactIterableAPI: IterableAuthDelegate {
         }
     }

+    func onAuthFailure(_ authFailure: AuthFailure) {
+        ITBInfo("Auth failure: \(authFailure)")
+        
+        self.sendEvent(withName: EventName.handleAuthFailureCalled.rawValue,
+                       body: ["reason": String(describing: authFailure.failureReason)])
+    }
+    
     func onTokenRegistrationFailed(_ reason: String?) {

     }

[Bay102]

+1

[CharithaDhananjaya251]

The above patch by @nasmithan worked 🫡

[Summys]

@lposen Thanks for taking care of this, when is the release scheduled?

[lposen]

Hey guys. We're working on incorporating a permanent fix into the SDK. In the meanwhile, here is a workaround:

In your Podfile, add the following to your application target:

pod 'Iterable-iOS-SDK', :git => 'https://github.com/Iterable/iterable-swift-sdk.git', :branch => 'hotfix/MOB-12091-Fix-coredata-util-method'

EG, if your app name is MyCoolApp, it would look like this:

target 'MyCoolApp' do
  // ...
  pod 'Iterable-iOS-SDK', :git => 'https://github.com/Iterable/iterable-swift-sdk.git', :branch => 'hotfix/MOB-12091-Fix-coredata-util-method'
  // ...
end

I would highly recommend not updating Iterable-iOS-SDK to 6.6.1. As some of you have noticed after doing this update, there are breaking changes in this updated version which do not align with our current SDK.

I will be sure to circle back when a permanent fix is released.

[Summys]

I appreciate the commitment on having this solved quickly, wouldn't be better to create a small patch from 2.0.2 tag and cherry-picking only your commits?

[Rehubbard]

@lposen thanks for the quick response. What about the Iterable-iOS-AppExtensions pod? Using your suggestion above I'm able to get past the performAndWait build error. However, my app uses the Iterable Notification Extension target set up according to these docs.

Its been working fine until I upgraded to xcode 26. The Notification extension target wont build, or if it does (using Swift) the notification extension isn't functioning correctly. Seeing a swiftCompatibility56 build error:

Thanks for the help!

[lposen]

I appreciate the commitment on having this solved quickly, wouldn't be better to create a small patch from 2.0.2 tag and cherry-picking only your commits?

The issue is not within our React Native SDK itself, but rather with the underlying iOS SDK it depends on. Unfortunately, we’re unable to publish a hotfix to iOS at this time because the required patch version has already been used. Unlike npm, iOS does not support more granular versioning (e.g., 6.5.4-hotfix.0), which limits our ability to release the fix immediately. We are actively exploring a workaround, but in the meantime we wanted to provide this update to help keep everyone unblocked.