Since my Apple Distribution signing certificate had expired I recently got a new one via https://developer.apple.com/account/resources/certificates/list and installed in on my login keychain. Since I had some issues with signing I suspected that codesign might still be trying to use an old expired certificate (as they have the same name "Apple Distribution: ()"). So to fix this I figured I could just delete the old expired certificate from Keychain Access so there was only the valid new certificate there with the same name. However, after doing this and trying to use it with codesign I get the following error error: The specified item is no longer valid. It may have been deleted from the keychain. In other words it seems it's not finding the new valid certificate and somehow still linking the name to the old certificate that it rightly guesses is removed. Following the tips from https://developer.apple.com/forums/thread/701514 I used security find-identity -p codesigning -v to check for installed codesigning certificates, and this listed the new certificate as expected. Using another tip in the same post I saw that you can also use the certificate hash as an identifier beside the name, and using this I can use it with codesign to sign. However, it's still not finding it via the name (or rather, it's still finding the old now removed one). What could be the reason for codesign not finding the correct new valid certificate based on the name and instead still finding the old one? Maybe there's some reference set somewhere to point the name towards specifically the old certificate?

Background I'm developing a game using a game engine that exports an (unsigned) app bundle for macOS. So to get this on the mac App Store I've managed to set up an entitlements file, embedded the required provisioning profile, codesign and finally package the app into a signed pkg that I've uploaded via the Transporter app without any errors or warnings during upload or Apple processing afterwards. With the help of https://developer.apple.com/forums/thread/725694 I was also able to add the correct additional entitlements to get Test Flight to allow (internal) testing of the app. This now works and the app is listed as "Ready to submit". XCode beta error issue However, if I try to add external testers to this build and click the Submit for review button I now get the following error: This build is using a beta version of Xcode and can’t be submitted. Make sure you’re using the latest version of Xcode or the latest seed release found on the releases tab in News and Updates Which makes no sense as the build has not been built, packaged or uploaded using Xcode and I've never had a beta version of XCode installed. Does anyone know what is causing this error with the build and how to get around it?

Background I'm developing a game using a game engine that exports an (unsigned) app bundle for macOS. So to get this on the mac App Store I've managed to set up an entitlements file, embedded the required provisioning profile, codesign and finally package the app into a signed pkg that I've uploaded via the Transporter app without any errors or warnings during upload or Apple processing afterwards. Test flight issue However, even though I've now managed to get the build up into the App Store connect system with no errors, in Test Flight the build is listed as "Not Available for Testing" with no further information. Before I managed to get the provision profile correctly embedded and signed Transporter gave me a warning saying that due to the missing profile the app would not be available for testing in Test Flight. But now that the profile is embedded there is no such warning. Does anyone have any experience with getting non-xcode project up on the App Store or Test Flight? Any hints as to what might be the cause of the "Not Available for Testing" status? And does this mean the build will also be invalid for publishing? Entitlements? This game build only has the required com.apple.security.app-sandbox: true entitlement, but when I look at macOS apps I've previously uploaded via XCode for other projects these also contain the (undocumented?) com.apple.application-identifier: and com.apple.developer.team-identifier: entitlements. And when looking at an iOS XCode build it includes the (also undocumented?) entitlement beta-reports-active: true could it be that there is some additional entitlement that is required for Test Flight? I've found no mention of them in the entitlements documentation so it's hard to know what their function is.