iOS framework target doesn't work when included as workspace dependency on Xcode 11 about plcrashreporter HOT 1 CLOSED

Hi @erikr98 ,

Thanks for getting in touch and pointing this out.
Yes, it was intentional before to get proper internal framework structure. This target is used just as a container for lipo script that packages static libraries into .framework. It doesn't compile any sources for this target, so it should not affect anything.
However, I reproduced this error on usage of this framework in the same workspace in Xcode 11. It worked well with Xcode 10, but it looks like Xcode 11 brings some additional checks for dependent targets.
Also, I want to note that it reproduces only if include framework that built from sources in the same workspace. Integrating with binaries that published in releases page works fine. So, I agree that the thing that we should address, but I don't think that it's a integration blocker for now.

from plcrashreporter.