![]() Thus, in most cases the correct answer here is to remove the static library from your shipping product.Īs to the actual symptoms you’re seeing, I looked into the situation with static libraries just yesterday as part of a DTS incident and thus I can explain the observed behaviour: The vast majority of folks who end up shipping static libraries (. ![]() ![]() Get a version of that framework that’s built against a modern SDK. Remove your dependency on the Growl framework. There’s only two supported ways to fix this: Notarisation requires modern code signing and, in order to be guaranteed that it has modern code signing, it requires that your components link with the 10.9 SDK or later. "The binary is not signed for " libchilkatCocoa.a".Ĭould you please help me understand how I can resolve these issues or if there is any workaround for this as I cannot recompile these as they are 3rd party framework. Error "The binary uses an SDK older than the 10.9 SDK" for "amework".Ģ. Now when I try to notarize this app by signing and recompile it, I few errors for 3rd party package "amework" and for a static library " libchilkatCocoa.a".ġ. We have a macOS package that was built 7-8 years back by some other organization.
0 Comments
Leave a Reply. |