Hello! Our situation is the following: We have an app which depends on an SPM library 1 which in turn depends on SPM library 2 with resources We override codesigning settings by passing them directly to xcodebuild via arguments during archiving Our setup used to archive successfully in Xcode 13.4. However, it fails in Xcode 14 beta 5. Sample app with the simplified setup can be found here https://github.com/dymv/SPMBundleSign A series of errors that we're getting when trying to archive our app via CLI: Running the same archive xcodebuild command that used to work in Xcode 13 causes this issue ⬇️ spm-bundle-sign-package_TargetWithResources requires a development team. Select a development team in the Signing & Capabilities editor. Passing a development team via DEVELOPMENT_TEAM="1234567890" causes another issue ⬇️ spm-bundle-sign-package_TargetWithResources has conflicting provisioning settings. spm-bundle-sign-package_TargetWithResources is automatically signed for development, but a conflicting code signing identity Apple Distribution has been manually specified. Set the code signing identity value to "Apple Development" in the build settings editor, or switch to manual signing in the Signing & Capabilities editor. Passing provisioning profile via PROVISIONING_PROFILE_SPECIFIER causes another issue ⬇️ spm-bundle-sign-package_TargetWithResources does not support provisioning profiles. spm-bundle-sign-package_TargetWithResources does not support provisioning profiles, but provisioning profile SPMBundleSign Distribution has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. AFAICS, the only way forward is to avoid any codesigning overrides via xcodebuild command. Are there any workarounds in case there's a requirement to provide such overrides via CLI? Please help us understand if there's anything that we can do in Xcode 14 to support our app setup. Thank you!