No such module 'OneSignal' - XCode Swift Compiler Error

Question

I'm currently trying to add OneSignal to my react native expo (bare) IOS build and have followed OneSignal's guide as shown here: https://documentation.onesignal.com/docs/react-native-sdk-setup

However, Xcode has flagged up a compiler error of: No such module 'OneSignal'

Here is my Podfile that includes the OneSignalXCFramework import:

require File.join(File.dirname(`node --print "require.resolve('expo/package.json')"`), "scripts/autolinking")
require File.join(File.dirname(`node --print "require.resolve('react-native/package.json')"`), "scripts/react_native_pods")
require File.join(File.dirname(`node --print "require.resolve('@react-native-community/cli-platform-ios/package.json')"`), "native_modules")

platform :ios, '12.0'

require 'json'
podfile_properties = JSON.parse(File.read('./Podfile.properties.json')) rescue {}

target '<NAME>' do
  use_expo_modules!
  config = use_native_modules!

  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => podfile_properties['expo.jsEngine'] == 'hermes'
  )

  # Uncomment to opt-in to using Flipper
  #
  # if !ENV['CI']
  #   use_flipper!('Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1')
  # end

  post_install do |installer|
    react_native_post_install(installer)

    # Workaround `Cycle inside FBReactNativeSpec` error for react-native 0.64
    # Reference: https://github.com/software-mansion/react-native-screens/issues/842#issuecomment-812543933
    installer.pods_project.targets.each do |target|
      if (target.name&.eql?('FBReactNativeSpec'))
        target.build_phases.each do |build_phase|
          if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
            target.build_phases.move(build_phase, 0)
          end
        end
      end
    end
    
    target.build_configurations.each do |config|
    # some older pods don't support some architectures, anything over iOS 11 resolves that
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
    end
  end

  post_integrate do |installer|
    begin
      expo_patch_react_imports!(installer)
    rescue => e
      Pod::UI.warn e
    end
  end

end

target 'OneSignalNotificationServiceExtension' do
  pod 'OneSignalXCFramework', '>= 3.0', '< 4.0'
end

As a side note, I've already tried to add pod 'OneSignal' or use_frameworks! into the PodFile. Has anyone else experienced this issue before?

use SPM (Swift Package Manager) to install. documentation.onesignal.com/docs/swift-package-manager-setup — Giau Huynh
– Giau Huynh, Commented Jun 30, 2022 at 9:49

MALIKK HABIB UR REHMAN · Accepted Answer · 2022-10-17 13:13:27Z

11

Xcode 14.0.1 update & Swift 5.7 - Using SPM(Swift Package Manager)

Recently I have integrated one signal into my project using SPM. it worked fine until I tried to upload the build to app store connect and it started showing me the same error. Here's how I fixed this issue.

Step 1: Removed the one signal dependency

Step 2: added again one signal Notification framework as a dependency.

On the Choose package products popup.

Select OneSignal to add to the project as a target.
Select OneSignalExtension to be added to the oneSignalNotificationService extension as a target.
Now go to "NotificationService.swift" file in OneSignalNotificationExtension and replace > import Onesignal with >import OneSignalExtension.
Also replace oneSignal in code with OneSignalExtension.
Add Package and build.

edited Oct 17, 2022 at 13:13

answered Oct 17, 2022 at 12:43

MALIKK HABIB UR REHMAN

89210 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

jarrodparkes Over a year ago

In order to see both of the Package Products, you must be using github.com/OneSignal/OneSignal-iOS-SDK instead of github.com/OneSignal/OneSignal-XCFramework

mtl Over a year ago

This was annoying and preventing me from distributing my app. Thank you!

Jorn Rigter Over a year ago

I'm surprised they didn't update their setup documentation yet to mention this

Remoo · Accepted Answer · 2023-05-04 13:52:40Z

0

In my case, which may not be the reason for many of you but may help someone, the first time I've added it, all works well, but after merging the code into my main branch I get this error. My problem was that I have added podfile to .gitignore so it was working the first time but after merging it, podfile of course doesn't have the needed last section which is

target 'OneSignalNotificationServiceExtension' do
  pod 'OneSignalXCFramework', '>= 3.0', '< 4.0'
end

So make sure you have it.

answered May 4, 2023 at 13:52

Remoo

7478 silver badges19 bronze badges

Comments

Fiyifoluwa · Accepted Answer · 2023-05-30 16:20:37Z

0

If you're like me and use an Apple Silicon Mac i.e M1/M2 and the Pros, you would need to turn on Rosetta. To do this, in your Xcode menu, select Product > Destination > Destination Architectures > Show Rosetta Destinations. Build in Rosetta after running the following command:

pod deintegrate && pod install

answered May 30, 2023 at 16:20

Fiyifoluwa

394 bronze badges

2 Comments

Burak Mete Erdoğan Over a year ago

finally it's worked!!

Erick Over a year ago

I don't see the option for the Destination Architectures in the Destination dropdown. I am using xcode version 14.2

Mostafa Alazhariy · Accepted Answer · 2025-05-06 02:48:49Z

0

If you're working with Flutter, have followed all the steps and solutions, and are still experiencing an issue.

Ensure you've opened the iOS project in Xcode using `Runner.xcworkspace` instead of `Runner.xcodeproj`.

As stated in the updated OneSignal documentation

You must exclusively use the .xcworkspace file to open the project.

Similar issues may occur in other libraries if you didn't open the project using Runner.xcworkspace.

answered May 6 at 2:48

Mostafa Alazhariy

4995 silver badges13 bronze badges

Collectives™ on Stack Overflow

No such module 'OneSignal' - XCode Swift Compiler Error

4 Answers 4

3 Comments

Comments

2 Comments

Ensure you've opened the iOS project in Xcode using `Runner.xcworkspace` instead of `Runner.xcodeproj`.

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

3 Comments

Comments

2 Comments

Ensure you've opened the iOS project in Xcode using Runner.xcworkspace instead of Runner.xcodeproj.

Comments

Your Answer

Sign up or log in

Post as a guest

Related

Ensure you've opened the iOS project in Xcode using `Runner.xcworkspace` instead of `Runner.xcodeproj`.