Post

Replies

Boosts

Views

Activity

Reply to App not launch on an M1 mac
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.
Nov ’21
Reply to App not launch on an M1 mac
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>
Dec ’21
Reply to App not launch on an M1 mac
TSI Support is not for free. The App works correct on all Intel test devices. I'm no longer able to test the release version of the App. Only debug in Xcode is working. TestFlight for internals is not possible. TestFlight for externals is not a solution. Sorry but this is not acceptable!
Feb ’22