What is the proper way of distributing a dynamic framework with a dependency on a static framework?

I’m building a closed source dynamic framework. It has a dependency on a 3rd party closed source static framework.

I link the static dependency framework to my framework’s project/target as described in this Apple tech note:

  • iPhone won't connect in Xcode 6 beta
  • Cancel All Operations + AFNetworking 3.0
  • Install ios 5 simulator to xcode 5.1?
  • Custom font for iPad - iOS 3.2 isn't working
  • ios - How to add checkbox list to UITextView
  • Opening import file for module 'Swift': Permission denied
  • enter image description here

    That same Apple tech note mentions:

    The app target is responsible for embedding all of the frameworks,
    including any frameworks that other frameworks depend on.

    So I also give my clients a copy of the framework I depend on. However, further down in the same tech note, Apple (referring to embedding static libraries/frameworks) states:

    Since the binary in these situations is a static library, apps cannot
    embed it in the app bundle.

    …The library should remain in the “Link Binary with Libraries”

    That’s fine – so I just have my clients link the static framework dependency instead of embed it and everything works fine.

    However, problems arise when my client needs the -ObjC linker flag for other libraries they use. This linker flag causes my (objective-c) static framework dependency to load all of its classes twice and the client sees duplicate class logs everywhere in their console.

    One possible solution here would be to have the client identify the libraries they use which need the -ObjC linker flag and instead specify the force_load flag for those libraries. But this solution also causes problems in the case of the client using CocoaPods since CocoaPods will overwrite any changes to their linker flags with -ObjC again with each pod install. Are there any other solutions/ideas anyone has to this problem?

    P.S. I know the Apple tech note from before also mentions:

    Static frameworks are not a supported way of sharing static libraries.

    but unfortunately my hands are tied from business constraints at the moment, and I must include this static framework dependency.