Do you use the Virtual Machine to run the macOS? If so, this configuration is not supported, unfortunately.

@Artem_XZ can you describe how did you manage to work Cloud-managed distribution certificates, please? Even using the Admin API key, I get the following error: Error Domain=IDEDistributionErrorDomain Code=10 "Failed to log in." UserInfo={IDEDistributionErrorsAccountIssues=( ), NSLocalizedDescription=Failed to log in., NSLocalizedRecoverySuggestion=App Store Connect access for “$TEAM_ID” is required. Ensure that your Apple ID account usernames and passwords are correct in the Accounts preference pane.} Does the API key-based distribution still work for you?

I don't have a developer program without any iOS devices so cannot check it.It seems that you cannot create a development provision profile with an empty device list. As a workaround, I suppose you can register iOS device with some random UDID (possibly you have to look up some record on the internet, for example, '00008020-008D4548007B4F26') and include this device in generated provisions.

I suppose both. The project is going to be opensource repo available as a buildable SPM target. Also, I consider CocoaPods practice with precompiled tool to simplify workflow (e.g. swiftlint).

I would like to setup identities and few generic passwords (Xcode-Token and Xcode-AlternateDSID) to the login keychain with allowed access for /usr/bin/codesign, /usr/bin/security and /usr/bin/productbuild (application list taken from fastlane). This terminal application designed to be called mostly on CI machines with initial credentials (.p12 files and source keychain with included SecItems) stored inside the private repository. I see two already available alternatives:1. Create SecAccess with nil trustedApplicationList to make default Restricted ACL available for any application. I would like to avoid such a case because of security concerns.2. Call terminal app /usr/bin/security import with -T argument to pass required apps. While this solution will work, it still feels alien in the Swift macOS application. Another point is the influence of the same deprecation on security tool. 3. The weirdest solution (not guaranteed also, and not encouraged by Apple) to look for workaround based on Security opensource project. It's absolutely should be avoided in 99,9% of cases but still worth a point in the list.

Do you have an iPhone or iPad? You have to connect it first to your mac computer and press the "Register Device" button in General tab of your Target. Xcode will generate the required certificates and provisionings.