Access to infrastructure from another structure and target application

Question

I'm not sure how to properly configure the build settings for how I want to split the infrastructure between the other infrastructure and my goal of the application - in this case, the common infrastructure is the Facebook SDK, but I'm not sure if this is about the problems I'm having encounter or not.

How I would like the work to be: I would like my frameworks to include the Facebook SDK, and since my application imports my framework, it can access the Facebook SDK. Unfortunately, I cannot use this configuration.

Firstly, I get an unresolved identifier build error when I try to link to something from the Facebook SDK from My Application.

If you enable import FBSDKLoginKit , this build error will disappear, but I cannot compile with FBSDKLoginKit is not a dylib . If I enable the Facebook SDK frameworks in the settings of the target installation “My application”, I can finally create and run, but at runtime I get console logs warning that all FBSDK classes are implemented as in “My application, My Framework” and that one of the two will be used. Which one is undefined. " This makes sense, as I currently mainly compiled the Facebook SDK twice.

I think that what I described above is an umbrella structure, which, as I understand it, is discouraged by Apple. Given that "my application" needs to access "FBSDK" and "My Framework", and "My Framework" needs to access "FBSDK", then how to properly configure the build settings for "My application" and "My framework" without getting console logs about duplicate implementations?