We have an app company.app and it is loading dynamic library from a thirdparty vendor - let's call it vendor.dylib.company.app is signed by our organisation's developer ID certificate. We have notarized company.app with hardened runtime enabled.vendor.dylib is signed and notarised by vendor's certificate.Now, when company.app tries to load the dylib using dlopen, we get an error "not valid for use in process using Library Validation: mapping process and mapped file (non-platform) have different Team IDs"I read about disabling library validation entitlement https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_disable-library-validation?language=objc and https://forums.developer.apple.com/thread/126895I added this in the info.plist file <key>com.apple.security.cs.disable-library-validation</key> <true/>After building the app and notarising it, i can still see the value com.apple.security.cs.disable-library-validation set to true in the final app's Info.plist.Yet, i get the same error "not valid for use....... mapped file have different Team IDs". It's as if 'disabling library validation entitlement' didn't take effect.Any pointers how to go about this?Note : I cannot opt for a solution where we take vendor.dylib and sign it with our certificate because even though it does seem to solve the loading problem, the vendor's code itself is doing some checksum verification which breaks if vendor.dylib is re-signed with our cert.

Hello, We have a macOS App Store app that uses network extension. One of the users is not able to install it since the App Store says "Requires a Mac running macOS 10.15 or later with an Intel 64-bit processor or additional software not available in your country or region" That user has a Macbook Pro with Apple M1 Max chip and is on Monterey (12.2.1). However, our app is supported and has been working with M1 chips. We checked with two other users - one with Macbook Air and Apple M1 chip and another one with Macbook Pro/ Apple M1 Max chip / 12.2.1 (same as the problematic user). Both these users are able to install it. So, we have inconsistency where one user is able to install it and is working fine while for the other user, we get an incompatibility warning. Does anyone have any idea how to go about this? Also, do we need to collect some logs like Console logs or something?