I'm getting asked questions by our security team about Xcode Cloud. They want to do an audit before we let it have access to our locally hosted gitlab repo. Is there any kind of security white paper for this product that I can point them at? Web searches haven't turned anything up for me to show to them.

I work on a lot of projects that are multi-platform projects using codebases based in ReactNative or NativeScript, both which could benefit from the cloud build for the iOS based applications. Is there a plan to add programmatic access to Xcode Cloud Build to allow access to the build pipeline from something like a GitHub action?

Hi! In my Xcode Cloud workflow, I have the TestFlight Internal Testing post-action with “App Store Connect Users” included in Groups. I expected the action would make the builds available for internal testing automatically (just as the builds uploaded from Xcode are). However, they don’t appear in TestFlight: in build history, I don’t see the ASC Users group next to my Xcode Cloud build, and in order to make it available for testing, I have to add the group manually. After the group is added, the build is published right away, without any extra steps (e.g. export compliance certification, etc.). Am I doing something wrong here? I’ve tried removing and re-adding the group in the post-action, and even re-creating the entire workflow—all to no avail.

Hi, I am creating a workflow in Xcode Cloud for a duplicated react-native application. I have changed the bundle identifier and created a new application in App Center with the same bundle identifier. in cloud when I am trying to proceed with the step "Archive-IOS" it throws following errors, but those are not thrown in "Build-IOS" step. Please provide me some suggestions. Error details: ITMS-90053: This bundle is invalid - The bundle identifier is already in use by a different software package. ITMS-90055: This bundle is invalid - The bundle identifier cannot be changed from the current value, '(duplicated.app.build.identifier)'. If you want to change your bundle identifier, you will need to create a new application in App Store Connect. ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in (Old App Name) [Payload/(oldappName)].

My team account has reached limitations, What can we do for building an app more than limitations in this month? I can’t find any information about it.

How do we increase our Xcode cloud usage limit? We are getting a warning that we are approaching our limit for the month.

I'm trying to archive my app via Xcode Cloud and auto-deploy to TestFlight but it fails during "Prepare Build for App Store Connect" with the following error message: ITMS-90334: Invalid Code Signature Identifier. The identifier "CoreImageExtensions-dynamic-555549444e09e22796a23eadb2704bf219d5c1fa" in your code signature for "CoreImageExtensions-dynamic" must match its Bundle Identifier "CoreImageExtensions-dynamic" CoreImageExtensions-dynamic is a .dynamic library target of a package that we are using. It seems that at some point a UUID is added to the library's identifier, which messes with code signing. When archiving and uploading the app in Xcode directly, everything works just fine. Any idea why this is happening and how I could fix it?

This is related to a Mac App. I would like to be able to make my build in Xcode Cloud available to my users in TestFlight. I would expect to be able to click the build in Xcode Cloud and see some kind of "Publish to TestFlight" action. Does this exist? Am I missing it? If not, how is this supposed to work?

Hi, this is what i got from Apple. our app includes incomplete features that users are required to use, such as login service. Next Steps To resolve this issue, revise your app so that it is appropriate for public distribution and provides users a complete experience. If your app is not ready for public distribution or is intended to demonstrate an app concept, use TestFlight. So may I know that what to do next?

I am having problems registering an IOS developer Account on Appium Studio. I have 2 different paying development accounts and both are failing to register. I have upgraded the Appium Studio version to the latest version (22.1.8625) and tried different computers in different networks. “The error message is: Failed to add apple developer account with appleid: *******@*****.net and teamid: ********** reason: Bad response from server. 200: OK Server says: Authentication Error. XCode 7.3 or later is required to continue developing with your Apple ID . (3019). Please make sure you are not using a free acount, as it is not supported.” So, I’m using a paying account with the latest Appium Studio version but getting this message. please provide some help on this issue? Regards

XCode Provisioning Profile report error "Provisioning Profile "my Provisioning Profile Name" doesn't include the New itementitlement."

In the last few days my Xcode cloud builds are failing with error 65. After downloading the logs and digging thru them, I am seeing the following error - line 6: $(CURRENT_PROJECT_VERSION) + 1: syntax error: operand expected (error token is "$(CURRENT_PROJECT_VERSION) + 1") This started after I did a check in of my code via the GIT Desktop app instead of Xcode. Since then I have deleted my workflow, recreated it, and reset my release # to try and clear this message, but every build fails with the exact same error. I have raised a feedback, but I am currently stuck to building and distributing my app to my TestFlight users. (I don't want to go back to the manual method, I am really enjoying Xcode cloud). Any suggestions on how to resolve this?

We're looking to test, and build, some CLI tools on Apple Silicon. The landscape for this among all the other classic hosts (GitHub Actions, Azure, etc) is looking pretty sad at the moment (mostly due to Apple's "24-hour" virtualization policy.) If we want to compile for M1 in the cloud, it's looking like Xcode Cloud is the only place to do it. Has anyone established a workflow for this? Is it necessary to create a fake "app" or something like that, or can one run arbitrary compilation-tasks on the M1 hosts?

When I select the Create Workflow option, I get a dialog saying "This operation couldn’t be completed." I am an Admin user. Xcode 13.3

I use Xcode Cloud Beta since around half a year and had sometimes the problem that only the progress indicator was shown in Xcode when opening the "Cloud" tab but it was always fixed the next day. Now I have the problem that it doesn't load since many days. I tried it with the newest release version of Xcode (13.2.1) and the newest Xcode Beta 3 (13.3) but both are not working. In App Store Connect everything works fine, there I can edit my workflows. Does anyone else have these problems?

I applied for XCloud waitlist yesterday. Is there any specific no of days after it gets approved?