OneSignal-iOS-SDK [question]: Need help with cocoapods integration

How can we help?

I have pods file like this:

target 'Main iOS App' do
    pod 'OneSignalXCFramework', '>= 3.0.0', '< 4.0'

  target 'OneSignalNotificationServiceExtension' do
    use_frameworks!
    pod 'OneSignalXCFramework/OneSignalExtension', '>= 3.0.0', '< 4.0'
  end

    pod 'Moya'
    pod 'KeychainAccess'
    pod 'Firebase/Crashlytics'
    pod 'Firebase/RemoteConfig'
    pod 'Amplitude', '~> 8.0'
    pod 'Firebase/Analytics'
end

And I meet issue when all pods where integrated onto nested OneSignalNotificationServiceExtension target. Could you help to resolve this issue?

Code of Conduct

[X] I agree to follow this project's Code of Conduct

May 21 '22 14:05 Sergozh

@Sergozh Could you provide the error or exact issue you are seeing? Please also share your the full contains of your Podfile and Podfile.lock files.

One suggestion is you may need to move use_frameworks! to the main target.

May 21 '22 20:05 jkasten2

Sure I'll create test project to show issue

May 23 '22 08:05 Sergozh

Here is my test environment: Project

May 23 '22 15:05 Sergozh

Update project link

May 25 '22 08:05 Sergozh

@Sergozh I am getting errors in that project even after removing all OneSignal references, however I see what you mean where by nesting the targets the Notification Service Extension now also depends on all of the pods in your app target. You can try removing all of the dependencies from the Pods-OneSignalNotificationServiceExtension framework except for OneSignalXCFramework

May 31 '22 18:05 emawby

@emawby I'll try ASAP. Thanks for your advice!

Jun 01 '22 08:06 Sergozh

@emawby unfortunately having the same error after removing all dependencies except OneSignalXCFramework. Could I revert to previous structure of pod file without nesting or not after update 3.11.0?

Jun 02 '22 16:06 Sergozh

@Sergozh You can yes, but don't use the OneSignalExtension submodule just use the OneSignalXCFramework in both the podfile and code

Jun 02 '22 17:06 emawby

Thank you! Hope we can find better solution than nesting targets and removing dependencies manually from Xcode

Jun 02 '22 17:06 Sergozh

i have also faced the same issue thats in release 3.11.1 thats the issue in pod release. i have solved the issue by downgrading the pod for onesignal pod 'OneSignal', '= 3.10.2' and changing code related to pod version 3.10.2.