Pod Installation Causes Build Errors for Notification Extension

[Tring-Rajaguhan]

SDK version: 5.2.0
React-Native: 0.82.1

Describe the issue
I added the Notification Extension and updated the Podfile by including the target:

target 'NotificationExtension' do
  # Notice the '-richpush' in the line below. This line is different from what was added for the main target.
  pod 'customerio-reactnative-richpush/fcm', :path => '../node_modules/customerio-reactnative'
end

After running the app, I’m getting compile errors.
I’ve also added the required code changes in the NotificationServiceExtension, but I'm still encountering errors.

Screenshots

Additional context
I have getting two issue ->

1. I’m getting compile errors above Screenshot
2. Ambiguous use of 'didReceive(_:withContentHandler:)'

[Tring-Rajaguhan]

Hello, Any update on the issue. Waiting for your response

[mahmoud-elmorabea]

Hello @Tring-Rajaguhan

Let me try to see if we can find what's going on with the errors here.

For the first issue

I don't think there is enough info for me to check what's going on, can you please share your pod file and app delegate snippet of how you initialize the SDK?

If you don't feel comfortable sharing those here, you can reach out to our support through win@customer.io and mention this issue and they will pass the info to our team.

For the notification target

In your NSE target (NotificationService class), you only need import CioMessagingPushFCM from CIO, you don't need to import CioMessagingPush which I believe is causing the issue

If you follow the docs example closely, you should be able to see the imports should look like.

[Tring-Rajaguhan]

@mahmoud-elmorabea , Having 2 targets in my application, Currently I have integrated Notification extension for ONEMusicfestStaging target and corresponding extention OneMusicfestStagingNotificationExtension.

Podfile

`def node_require(script)
  # Resolve script with node to allow for hoisting
  require Pod::Executable.execute_command('node', ['-p',
    "require.resolve(
      '#{script}',
      {paths: [process.argv[1]]},
    )", __dir__]).strip
end
    
node_require('react-native/scripts/react_native_pods.rb')
node_require('react-native-permissions/scripts/setup.rb')

platform :ios, min_ios_version_supported
prepare_react_native_project!
 
use_frameworks! :linkage => :static
setup_permissions([
  'AppTrackingTransparency',
])

target 'MainTarget' do
  config = use_native_modules!

  use_react_native!(
    :path => config[:reactNativePath],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  pod 'BVLinearGradient', :path => '../node_modules/react-native-linear-gradient'

  pod 'customerio-reactnative/fcm', :path => '../node_modules/customerio-reactnative'

  permissions_path = '../node_modules/react-native-permissions/ios'
  pod 'Permission-LocationAccuracy', :path => "#{permissions_path}/LocationAccuracy"
  pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
  pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
  pod 'AEPAnalytics', '~> 5.0'
  pod 'AEPCore', '~> 5.0'
  pod 'AEPIdentity', '~> 5.0'
  pod 'AEPSignal', '~>5.0'
  pod 'AEPLifecycle', '~>5.0'
  pod 'AEPUserProfile', '~> 5.0'
 
  
  target 'ONEMusicfestStaging' do
    inherit! :complete
    # Pods for testing
  end
  
  target 'OneMusicfestStagingNotificationExtension' do
    # Pods for testing
    pod 'customerio-reactnative-richpush/fcm', :path => '../node_modules/customerio-reactnative'
  end
  

  post_install do |installer|
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false,
      # :ccache_enabled => true
    )
  end
end
`

Appdelegate

import UIKit
import React
import React_RCTAppDelegate
import ReactAppDependencyProvider
import Firebase
import FirebaseCore
import FirebaseMessaging
import CioDataPipelines
import CioMessagingPushFCM
import CioFirebaseWrapper

typealias CioMessagingPushHandler = MessagingPushFCM

@main
class AppDelegateWithCioIntegration: CioAppDelegateWrapper<AppDelegate> {}
class AppDelegate: UIResponder, UIApplicationDelegate {
  var window: UIWindow?

  var reactNativeDelegate: ReactNativeDelegate?
  var reactNativeFactory: RCTReactNativeFactory?

  func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil
  ) -> Bool {
    
    let delegate = ReactNativeDelegate()
    let factory = RCTReactNativeFactory(delegate: delegate)
    delegate.dependencyProvider = RCTAppDependencyProvider()

    reactNativeDelegate = delegate
    reactNativeFactory = factory

    window = UIWindow(frame: UIScreen.main.bounds)
    factory.startReactNative(
      withModuleName: "REVOLTSummit",
      in: window,
      launchOptions: launchOptions
    )

    FirebaseApp.configure()
    Messaging.messaging().delegate = self
    MessagingPushFCM.initialize(withConfig: MessagingPushConfigBuilder().autoTrackPushEvents(true).showPushAppInForeground(true).build())

    AdobeAnalyticsManager.shared.initializeAdobeAnalytics(application: application)
    RNSplashScreen.show()
   
    return true
  }
  
  func application(_ application: UIApplication,
                     open url: URL,
                     options: [UIApplication.OpenURLOptionsKey : Any] = [:]) -> Bool {
      return RCTLinkingManager.application(application, open: url, options: options)
  }
  
  func applicationWillEnterForeground(_ application: UIApplication) {
    AdobeAnalyticsManager.shared.lifecycleStart()
  }
  
  func applicationDidEnterBackground(_ application: UIApplication) {
    AdobeAnalyticsManager.shared.lifecyclePause()
  }
  
  func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
       // This is required for FCM. The Customer.io SDK does not make changes to other SDKs
       Messaging.messaging().apnsToken = deviceToken
   }
}

class ReactNativeDelegate: RCTDefaultReactNativeFactoryDelegate {
  override func sourceURL(for bridge: RCTBridge) -> URL? {
    self.bundleURL()
  }

  override func bundleURL() -> URL? {
#if DEBUG
    RCTBundleURLProvider.sharedSettings().jsBundleURL(forBundleRoot: "index")
#else
    Bundle.main.url(forResource: "main", withExtension: "jsbundle")
#endif
  }
}

extension AppDelegate: MessagingDelegate {
  func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {
      // Not needed when CioAppDelegateWrapper is used
//    MessagingPush.shared.messaging(messaging, didReceiveRegistrationToken: fcmToken)
  }
  
}

For the notification target, Here is the error after do pod install

Let me know if you need any any additional

[AristideVB]

@mahmoud-elmorabea I have the exact same issue, I've followed the flutter docs...

https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-setup/#swift-push

If I try to add additional imports I get the same Ambiguous use of 'didReceive(_:withContentHandler:)' as @Tring-Rajaguhan

[AristideVB]

@mahmoud-elmorabea I’m hitting the exact same issue. I followed the Flutter docs step-by-step:

https://docs.customer.io/integrations/sdk/flutter/push-notifications/push-setup/#swift-push

Even after trying the “add more imports” workaround, I still get:

• Ambiguous use of 'didReceive(_:withContentHandler:)'
• Ambiguous use of 'serviceExtensionTimeWillExpire()'

Same as @Tring-Rajaguhan: adding additional imports didn’t resolve it (and in my case it often makes things worse / introduces other conflicts).

@mahmoud-elmorabea @Shahroz16 could you please take a look ASAP? It feels like something in the 3.x + Firebase wrapper change isn’t fully reflected in the Flutter docs for the NotificationServiceExtension target.

Podfile

platform :ios, '15.5.0'

ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

Pod::PICKER_MEDIA = false
Pod::PICKER_AUDIO = false
Pod::PICKER_DOCUMENT = true

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  pod 'customer_io/fcm', :path => '.symlinks/plugins/customer_io/ios'

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

target 'NotificationServiceExtension' do
  use_frameworks!
  pod 'customer_io_richpush/fcm', :path => '.symlinks/plugins/customer_io/ios'
  pod 'CioFirebaseWrapper', '~> 1.0'
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)

    target.build_configurations.each do |config|
      config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
        '$(inherited)',
        'PERMISSION_CAMERA=1',
        'PERMISSION_NOTIFICATIONS=1',
      ]
    end
  end
end

NotificationService.swift

import CioMessagingPushFCM

class NotificationService: UNNotificationServiceExtension {
  override func didReceive(
    _ request: UNNotificationRequest,
    withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void
  ) {
    MessagingPushFCM.initializeForExtension(
      withConfig: MessagingPushConfigBuilder(cdpApiKey: "YourCdpApiKey")
        .region(.EU)
        .build()
    )

    MessagingPush.shared.didReceive(request, withContentHandler: contentHandler)
  }

  override func serviceExtensionTimeWillExpire() {
    MessagingPush.shared.serviceExtensionTimeWillExpire()
  }
}

AppDelegate.swift

import UIKit
import Flutter
import CioMessagingPushFCM
import CioFirebaseWrapper
import FirebaseMessaging
import FirebaseCore

@main
class AppDelegateWithCioIntegration: CioAppDelegateWrapper<AppDelegate> {}

class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    GeneratedPluginRegistrant.register(with: self)

    MessagingPushFCM.initialize(
      withConfig: MessagingPushConfigBuilder()
        .build()
    )

    UNUserNotificationCenter.current().delegate = self as UNUserNotificationCenterDelegate
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }

  override func application(
    _ application: UIApplication,
    didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data
  ) {
    super.application(application, didRegisterForRemoteNotificationsWithDeviceToken: deviceToken)
    Messaging.messaging().apnsToken = deviceToken
  }
}

If you have a known-good import combination / target pod combination for the service extension in Flutter + iOS + FCM (3.x), I’m happy to test immediately.

[mahmoud-elmorabea]

Hello folks,

Thank you so much for providing those extra details! Much appreciated.

I suspect the culprit to be in the NSE target declaration. I believe in both cases it's nested within your main target. I believe you have two options:

1. Follow the docs suggestion. Be sure to select Swift/FCM and declare the NSE target at the root level
2. If you have reasons to want it be nested that way, you can mark it with inherit! :none so that it doesn't inherit your main target's dependencies.

Can you please try this out and let me know how it works out? And if there are any other issues other than NSE code not able to find CIO types?

[AristideVB]

Hi @mahmoud-elmorabea @Shahroz16,

Thanks for the suggestion, but My NSE target is already declared at root level – it's not nested inside the Runner target.

[Tring-Rajaguhan]

@mahmoud-elmorabea My NSE target is also at the root level, Verified with your suggestion but I'm still facing the same issue.

[mahmoud-elmorabea]

Hello,

Apologies for not being clear enough. I meant the NSE declaration within the pod file not the file hierarchy. Full snippet in the docs but something like this:

target 'YourApp' do # Look for the main app target. 
  ..
  pod 'customerio-reactnative/fcm', :path => '../node_modules/customerio-reactnative'
..
end 

target 'NotificationServiceExtension' do
  pod 'customerio-reactnative-richpush/fcm', :path => '../node_modules/customerio-reactnative'
end

Instead of NotificationServiceExtension declared inside the main target.

[AristideVB]

Hi @mahmoud-elmorabea

I think you may have missed the Podfile in my earlier comment. My NSE is not nested inside the Runner target – it's already at root level, exactly as you're suggesting.

Podfile extract (from earlier post)

target 'Runner' do
  use_frameworks!
  use_modular_headers!
  
  pod 'customer_io/fcm', :path => '.symlinks/plugins/customer_io/ios'

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

target 'NotificationServiceExtension' do
  use_frameworks!
  pod 'customer_io_richpush/fcm', :path => '.symlinks/plugins/customer_io/ios'
end

The NSE target is a sibling to Runner, not a child. The nesting issue you're describing doesn't apply here.

[Tring-Rajaguhan]

@mahmoud-elmorabea @Shahroz16 I have created the new app in react-native 0.82.1 and add customer.iO and firbase package, Still I'm facing the same issue.

please download the source code in the drive link.

https://drive.google.com/file/d/18eJ9Unk0FF7rpuMJhveBYPRGtEVsfTwi/view?usp=sharing

Steps to Reproduce the Issues:

1. Download the app from the Drive.
2. Run yarn install followed by pod install.
3. Review the Pod files and the NotificationService.swift file.
4. You will be able to see the second issue (NotificationService.swift).
5. Next, Remove code form NotificationService.swift and replace with below code and try running the app — you will then encounter the first issue.

Use the below code for NotificationService

import UserNotifications

class NotificationService: UNNotificationServiceExtension {

    var contentHandler: ((UNNotificationContent) -> Void)?
    var bestAttemptContent: UNMutableNotificationContent?

    override func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {
        self.contentHandler = contentHandler
        bestAttemptContent = (request.content.mutableCopy() as? UNMutableNotificationContent)
        
        if let bestAttemptContent = bestAttemptContent {
            // Modify the notification content here...
            bestAttemptContent.title = "\(bestAttemptContent.title) [modified]"
            
            contentHandler(bestAttemptContent)
        }
    }
    
    override func serviceExtensionTimeWillExpire() {
        // Called just before the extension will be terminated by the system.
        // Use this as an opportunity to deliver your "best attempt" at modified content, otherwise the original push payload will be used.
        if let contentHandler = contentHandler, let bestAttemptContent =  bestAttemptContent {
            contentHandler(bestAttemptContent)
        }
    }

}

For the first issue

NotificationService file issue

Let me know if you need anything. I am happy to share.

[AristideVB]

After thoroughly investigating, I found the root cause @mahmoud-elmorabea

The issue is Swift 6's MemberImportVisibility feature, which is enabled by default in Xcode 16+.

When SWIFT_UPCOMING_FEATURE_MEMBER_IMPORT_VISIBILITY = YES (the default in new Xcode 16+ projects), Swift requires explicit imports for all modules that define symbols you use.

Your MessagingPush.shared is defined in CioMessagingPush, but your docs tell users to only import CioMessagingPushFCM. This causes:

error: class property 'shared' is not available due to missing import of defining module 'CioMessagingPush'

But here's the catch: if I add import CioMessagingPush alongside import CioMessagingPushFCM, I get:

Ambiguous use of 'didReceive(_:withContentHandler:)'
Ambiguous use of 'serviceExtensionTimeWillExpire()'

So both modules expose the same method signatures, and Swift can't resolve which one to use. This is a bug in your SDK architecture.

The Only Workaround

The only fix right now is to disable the Swift 6 feature in the Xcode project:

SWIFT_UPCOMING_FEATURE_MEMBER_IMPORT_VISIBILITY = NO

This is not a real solution – it's a workaround for a broken SDK.

Why You Couldn't Reproduce It @mahmoud-elmorabea

This exact same issue was reported back in December 2024 in customerio/customerio-ios#841.

Your response at the time was:

"I created a new app from scratch and added a rich push extension target using steps in the docs and was able to add the code snippet and build the project successfully."

And then the issue was closed for inactivity without more investigation.

The reason you couldn't reproduce it is most likely because you were using Xcode 15.x while users were already on Xcode 16 (released September 2024). Xcode 16 enables Swift 6 upcoming features by default, including MemberImportVisibility. If you're still testing on Xcode 15.x, you'll never see this issue.

We're now in December 2025 with Xcode 26.

Suggestions @mahmoud-elmorabea

1. Test the SDK with Xcode 16+ to reproduce the issue
2. Consider testing with Xcode betas before releases to catch these compatibility issues early
3. Fix the module architecture so CioMessagingPushFCM properly re-exports MessagingPush without causing ambiguity
4. In the meantime, update docs to mention this Xcode 16+ workaround

Summary

• My Podfile structure was correct (NSE at root level, not nested)
• The error "missing import of defining module 'CioMessagingPush'" points to a module visibility issue
• Adding the missing import causes ambiguity errors due to duplicate symbol exposure
• Root cause: SDK isn't fully compatible with Xcode 16+ / Swift 6 strict imports

Hope this helps track down the fix!

Thanks.

[mahmoud-elmorabea]

Thank you so much for looking into it, I will follow your steps to reproduce and look into the issue today!

[mahmoud-elmorabea]

Hey,

@AristideVB @Tring-Rajaguhan I was able to reproduce the issue by turning the build config SWIFT_UPCOMING_FEATURE_MEMBER_IMPORT_VISIBILITY ON. Thank you for your help surfacing this!

We are working on a finding a solution but we don't have an ETA for now.

Can you please try turning this flag off for now and see if that unblocks you from moving forward with the integration please? SWIFT_UPCOMING_FEATURE_MEMBER_IMPORT_VISIBILITY = NO

I know this is not the ideal way to go but it does workaround that compilation error for now.