Apple notarisation process - LC_VERSION_MIN_MACOSX

Ryan Schmidt ryandesign at
Wed Mar 3 02:36:57 UTC 2021

On Mar 2, 2021, at 12:45, Adrian Georgescu wrote:

> After rebuilding a lot of port libs until I obtained the LC_VERSION_MIN_MACOSX, I ran into this new Apple rejection reason:

Are you saying that *just* rebuilding from source on your computer was sufficient to get LC_VERSION_MIN_MACOSX to be used? If so, why did building from source on your computer work but building from source on our build machines did not work? Is this a feature introduced in Xcode after version 12.2? I have not updated our Big Sur build machines past Xcode 12.2 yet.

Or did you have to modify the Portfiles in some way to get LC_VERSION_MIN_MACOSX to be used?

> Guideline 2.5.1 - Performance
> Your app links against the following non-public framework(s):
> • Contents/Frameworks/libcrypto.1.1.dylib/___sprintf_chk
> • Contents/Frameworks/libp11-kit.0.dylib/___sprintf_chk
> • Contents/Frameworks/libmpfr.6.dylib/___sprintf_chk
> • Contents/Frameworks/libgnutls.30.dylib/___sprintf_chk
> • Contents/Frameworks/libgnutls.30.dylib/_p11_kit_space_strdup
> • Contents/Frameworks/libgnutls.30.dylib/_p11_kit_space_strlen
> • Contents/Frameworks/libidn2.0.dylib/_sprintf
> • Contents/Frameworks/libx264.157.dylib/___sprintf_chk
> • Contents/Frameworks/libssl.1.1.dylib/___sprintf_chk
> • Contents/Frameworks/libxml2.2.dylib/___sprintf_chk
> Next Steps
> The use of non-public APIs is not permitted on the App Store as it can lead to a poor user experience should these APIs change.
> Is it possible to rebuild those libs without those symbols?

You tell us; we've never heard of this before.

More information about the macports-users mailing list