I’ve an app with 5 extensions, and I am including pods to all 6 targets.
I had linking points with one of many extensions and I found the Library Search Path part for its goal was completely different from all the opposite targets, and this was the reason for the construct situation. After manually updating it to match the opposite targets, it constructed, linked, and ran.
My query is – as this part will get up to date robotically by the pod file/command, why is it not getting up to date for one goal however it’s for all of the others? The pod spec is similar. I attempted working pod deintegrate after which pod set up once more, nevertheless it makes no distinction.
I need to know why the Xcode construct part is not getting set for this particular goal.
Here is a piece of the pod file, exhibiting the extension in query (the CallExtension), and a few different extensions too.
workspace 'CeqProject'
<snip>
goal 'CallExtension' do
venture 'CeqProject.xcodeproj'
pod 'Firebase/Crashlytics', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
pod 'CocoaLumberjack/Swift'
finish
goal 'UnwantedCommunicationExtension' do
venture 'CeqProject.xcodeproj'
pod 'PhoneNumberKit'
pod 'Firebase/Crashlytics', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
pod 'CocoaLumberjack/Swift'
finish
goal 'NotificationContentExtension' do
venture 'CeqProject.xcodeproj'
pod 'PhoneNumberKit'
pod 'RealmSwift'
pod 'Firebase/Crashlytics', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
pod 'CocoaLumberjack/Swift'
finish
<snip>
After working pod set up, inside Xcode the Library Search Path for the Name Extension is like this:
Nevertheless, for all the opposite targets, its like this:
Why is pod set up not setting/updating the Name Extension goal’s Library Search Paths however it’s for all the opposite targets?