-
Notifications
You must be signed in to change notification settings - Fork 263
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
Pod error 'shared' is unavailable. use viewcontroller based solutions #288
Comments
@fnrbh Is this the full exact error? |
@jkasten2 thank you for your response. The error is : 'shared' is unavailable: use view controller based solutions where appropriate instead. TwitterPagerTabStripSettings.swift My podfile is as follows: platform :ios, '9.0'
target 'mopa' do
use_frameworks!
# Pods for mopa
pod 'Alamofire', '~> 4.4'
pod 'FSPagerView'
pod 'SDWebImage'
pod 'SwiftKeychainWrapper'
pod 'CHIPageControl', '~> 0.1.3'
pod 'XLPagerTabStrip', :git => 'https://github.com/xmartlabs/XLPagerTabStrip.git'
pod 'ActiveLabel'
pod "Koloda"
pod 'RxSwift', '~> 3.0'
pod 'RxCocoa', '~> 3.0'
pod 'RxDataSources', '~> 1.0'
pod 'RxAlamofire'
pod 'RSKImageCropper'
pod 'OneSignal', '>= 2.5.2', '< 3.0'
target 'mopaTests' do
inherit! :search_paths
# Pods for testing
end
target 'OneSignalNotificationServiceExtension' do
pod 'OneSignal', '>= 2.5.2', '< 3.0'
end
end |
I have the same error when pods aren't extension compliant. |
I solved the problems of other pods. I didn't use "shared" directly but used different ways to achieve the same result. |
i don't think this should have been closed. thats not a really solution, just a workaround. Anytime you update your pods, all your changes would be lost, otherwise one has to manually import all of the non compliant pods to the project itself. |
Also seeing this error. Surely OneSignal doesn't expect all of your other pods to be extension compliant in order to use it? |
I solved it the other way around and imported the OneSignal framework locally to the project. Since i have several pods that were not extension compliant, it was easier this way. But if there's an update i'll have to do it manually, so it's not a great solution, just a quick fix. |
I am facing same issue.. |
I had same problem . So setting require only app-extension-safe api to No to other pod setting helped |
I had the same problem too. |
Any one got the solution? |
Hi, we are planning to fix this - there is already an open issue for the app-extension-unsafe code (#396) and we will be addressing it by making our extension-specific code its own subspec framework. In the mean time, setting the Because there is already an issue for this I won't be reopening the ticket |
Hi @Nightsd01 ! |
Hi @RishiRaj27 , i could't solve it that way either. As i said above I ended up importing the onesignal pod content to my project and using it inside instead of using a pod. Not an ideal solution, but it did the job. |
@RishiRaj27 can you post your Podfile? |
Thanks @Nightsd01 and @vanessaguapo !
|
@RishiRaj27 we have been working on a 3.0 release that will resolve this issue entirely. In the mean time manually including the framework should also resolve the problem |
@Nightsd01 i have import in manually in one signal notification but same error in shared' is unavailable: use view controller based solutions where appropriate instead then i have change require only app-extension safe api To NO then all issue resolved. any issue in upload in app store. |
I am having the same problem here, it happens whenever I add one signal in my OneSignalNotificationServiceExtension target target 'OneSignalNotificationServiceExtension' do |
Any update here? Running into the same issue and none of the provided fixes resolve the issue. |
Hey All, Flagging "Require Only App-Extension-Safe API" did not work for me. I solved this by putting the following code at the bottom of my Pods file:
Also, making sure my OneSignalNotificationServiceExtension target is a child of my app target:
People still facing this issue? @ZakSingh @RishiRaj27 @vanessaguapo |
had this problem today too what a royal pain. thanks @lukebrandonfarrell that script saved having to manually update a bunch of pod files Build Settings. |
None of these solutions works for me. The issue for me comes from React-Core. |
Still facing the same issue with the Onesignal version (2.11.2). Using Xcode 11 and swift. |
@abhishek-gangwar I too had similar issue spent 2 days to figure it out...ended by adding for example `platform :ios, '10.0' use_frameworks! target 'mopa' do target 'mopaTests' do target 'OneSignalNotificationServiceExtension' do end` this should work, do not forget to update OneSignal SDK, it has the latest iOS13.2 notification bug fix |
any better solution yet? |
@danial096 I had the same problem and solved it by removing additional pods that dealt with notifications. For example, I had OneSignal, Firebase Messaging, and Firebase InAppMessaging all in my podfile. I removed the 2 Firebase pods and then my project worked. |
@Samuelford24 i dont have other pod that handle notification. The problem appear after I install onesignal pod to my notification extension. for now i just set |
It's 2020 and I just got this error today after setting up using Swift. The script worked. |
@lawgimenez I have the same issue. Which script worked for you? |
@houmie the one below sir, with the most upvotes post_install do |installer| |
@lawgimenez Thank you. I missed that somehow. That worked for me too. |
Finally something that worked!!! |
Hello,
I followed the instructions on IOS sdk setup page. After 'pod install', i cleaned and built my project and got "'shared' is unavailable: Use view controller based solutions where appropriate instead" errors on my other pods.
When i remove onesignal from podfile and install, the errors disappear.
Anybody has seen this error?
thanks...
The text was updated successfully, but these errors were encountered: