Hello, thanks for the answer. com.apple.quarantine -> CHECK codesign -v -> CHECK UUID -> CHECK extract-certificates -> CHECK codesign -d -> CHECK But no success. here my commandline to build my app xcodebuild -archivePath ~/aaa.xcarchive -workspace ~/aaa.xcworkspace -scheme aaa archive -configuration Release -destination 'platform=OS X' xcodebuild -exportArchive -archivePath ~/aaa.xcarchive -exportPath ~/aaa -exportOptionsPlist ~/exportOptionsMacDev.plist exportOptionsMacDev.plist -> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>destination</key> <string>export</string> <key>method</key> <string>development</string> <key>provisioningProfiles</key> <dict> <key>com.aa.aaa</key> <string>DEV-profile</string> </dict> <key>signingCertificate</key> <string>Apple Development</string> <key>signingStyle</key> <string>manual</string> <key>teamID</key> <string>XXXX</string></dict> </plist>

I have done also the steps of the official documentation. This option "--entitlements AA.entitlements" creates a damaged executable for Apple Silicon. No issue on intel! aa.txt

Thanks for the info. The Xcode capabilities / sandbox settings are only: outgoing connections (client) user selected file (read/write) The testers machine UUIDs are in the provisioning profile. I think you have overseen one important thing. This is an M1 issue only because the exported test app works on an intel machine.

` codesign --force --deep -s - "APP1.app" APP1.app: replacing existing signature ` This is not a solution because the app is a sandbox app and after the new codesign it's no longer a sandbox app.

Looks like Ad-hoc Development export to send the MacOS App to tester is no longer possible for Apple M1 (Mac OS 12). VERY BAD !!!

Any News? codesign -s "Apple Distribution" -o runtime --entitlements AA.entitlements -f "AA" ./AA zsh: illegal hardware instruction  ./AA

Today a get the mail again. Why do i don't get any help here?

Today a get the mail again. Dear Developer, We identified one or more issues with a recent delivery for your app, ... Your delivery was successful, but you may wish to correct the following issues in your next delivery: ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: de ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: nl ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: nb ITMS-90626: Invalid Siri Support - Localized description for custom intent: 'Configuration' not found for locale: en ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: tr ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: ru ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: el ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: es ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: pl ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: fr ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: pt ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: da ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: sv ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: it ITMS-90626: Invalid Siri Support - Localized title for custom intent: 'Configuration' not found for locale: cs After you’ve corrected the issues, you can upload a new binary to App Store Connect. Best regards, The App Store Team