SPM resource management is not working about lnpopupcontroller HOT 6 CLOSED

What do you mean “dynamic setting prevent to build on Xcode Cloud”? That makes no sense, I’m sorry. Your PR complicates the package, but I see no reason why it’s necessary.

from lnpopupcontroller.

Post the exact error you are getting when building.

from lnpopupcontroller.

@LeoNatan
🫡Okay, let me explain in detail.

The exact error message is below.

ITMS-90334: Invalid Code Signature Identifier. The identifier "LNPopupController-55554944823d173b292035d5a9f68255954da87b" in your code signature for "LNPopupController" must match its Bundle Identifier "LNPopupController"

This error is caused by explicitly specifying LibraryType.
Removing the library type means Xcode will link the package statically if the package is only imported by one target.

To be more specific, please see thread below.

https://developer.apple.com/forums/thread/708284?answerId=732491022#732491022

from lnpopupcontroller.

So this is an Apple bug 🤦‍♂️ what a silly, garbage company. They are really incapable of doing anything right these days.

But I'm not convinced I should accept the PR. Perhaps just remove the static altogether. It was needed in the past due to another Apple bug. 🤦‍♂️

from lnpopupcontroller.

refactor how your targets are structured, reducing the reliance on the package to a single target, so that this becomes the first scenario I described where Xcode can safely link the library statically while avoiding the code signing error, as well as avoiding duplicate symbol issues.

This isn't possible for my library, because SPM does not support mixed languages. 🤦‍♂️

from lnpopupcontroller.

I'm sorry, I won't dirty up the framework and package for Apple bugs. Please fork, if you must, and make the change for your builds. I'd suggest using a proper CI solution, one not build by Apple.

from lnpopupcontroller.