Hey folks, Is it possible to integrate CBL as a dynamic library when acquiring it via CocoaPods?
Our app has an action extension and a shared embedded framework, all of which use CBL. Despite in the Podfile confining 'couchbase-lite-ios' to the framework target only, the CBL classes nonetheless end up duplicately linked in both the framework and the app proper. (This is manifest by a spew of "Class CBLxxx is implemented in both X and Y. One of the two will be used. Which one is undefined." messages on launch.) Perhaps due to sheer luck, CBL 1.2.1 seems to work despite the duplicate linkage. Unfortunately (but not surprisingly) CBL 1.3 does not work properly this way, so we have been forced to pin to 1.2.1 for the time being. Obviously, this is not a good state of affairs. When I last tried to find a solution for this a few months ago, I was led to conclude that this is simply impossible via CocoaPods, because for some reason only an opaque static binary is distributed, rather than source that builds into a proper dynamic library. Has this situation changed? Is there a proper solution I've overlooked that will allow me to use CBL acquired via CocoaPods in a non-trivial app? thanks, -ben -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/E851FD20-7C5C-40FD-A2B2-C7D2F116072A%40kashoo.com. For more options, visit https://groups.google.com/d/optout.
