-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question]: Need help with cocoapods integration #1093
Comments
@Sergozh Could you provide the error or exact issue you are seeing? Please also share your the full contains of your One suggestion is you may need to move |
Sure I'll create test project to show issue |
Here is my test environment: Project |
Update project link |
@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 |
@emawby I'll try ASAP. Thanks for your advice! |
@emawby unfortunately having the same error after removing all dependencies except |
@Sergozh You can yes, but don't use the OneSignalExtension submodule just use the OneSignalXCFramework in both the podfile and code |
Thank you! Hope we can find better solution than nesting targets and removing dependencies manually from Xcode |
i have also faced the same issue thats in release 3.11.1 thats the issue in pod release. |
Hi @umarfarooqitgcuf |
Also facing the same issue. |
Please install the pod with specific version pod 'OneSignal', '= 3.10.2'. It will be helpful for you. |
|
How can we help?
I have pods file like this:
And I meet issue when all pods where integrated onto nested
OneSignalNotificationServiceExtension
target. Could you help to resolve this issue?Code of Conduct
The text was updated successfully, but these errors were encountered: