Is there no solution for this? I checked your other thread as well. Is there a way for me to remove the third party libraries from my SDK? I run the below commands to generate the SDK. xcodebuild archive \ -project Abc.xcodeproj \ -scheme "AbcSDK" \ -configuration Release \ -destination "generic/platform=iOS Simulator" \ -archivePath "BuildArtifacts/iossim.xcarchive" \ | tee build.log xcodebuild archive \ -project Abc.xcodeproj \ -scheme "AbcSDK" \ -configuration Release \ -destination "generic/platform=iOS" \ -archivePath "BuildArtifacts/ios.xcarchive" \ | tee build.log xcodebuild -create-xcframework \ -framework BuildArtifacts/iossim.xcarchive/Products/Library/Frameworks/AbcSDK.framework \ -framework BuildArtifacts/ios.xcarchive/Products/Library/Frameworks/AbcSDK.framework \ -output Frameworks/AbcSDK.xcframework As soon as I run, it gives me the list of resolved source packages that includes all the third party libraries. If I try removing the libraries, it gives error at all the import statements in my code. I even tried using the below, but it didn't help.. @_implementationOnly import GoogleMaps

I have a standalone iOS app and an SDK created out of it to distribute to a third party. During the process of creating an SDK, I created multiple framework targets for different modules. Now one fo the module depends on a third party library say ABC. I don't want to make it static and hence i moved just the ABC to a different framework and made it dynamic. Now I am getting linker errors. I don't want the ABC binary to be there in the SDK as this is giving duplicate error issue at client end.

ABC(Google Maps) is a third party library. Its a static framework thats installed via SPM. I tried using linkers and many more configurations, but it always gets bundled within the SDK that's causing the conflict at the client end. Please suggest!

It would be helpful if you could suggest a way in which this can be handled at my end. The vendor will not be providing a dynamic framework. Please suggest a way forward