I am using Xcode cloud to build flutter app and report error

When trying to create a new workflow for a project I get the following message: To create Xcode Cloud workflows, first add a remote source code repository from Bitbucket, GitHub, or GitLab. This happens to both a project that already has a workflow setup and a project that was never setup with Xcode Cloud. Anyway to fix this? P.S: Both projects DO have a remote branch in Bitbucket Cloud... P.S.S: I've tried both with Xcode 13.4.1 on macOS Monterey and Xcode 14 beta on Ventura

…and nothing more on the page. Not only on my account, but also on other teams I have access to. Is that expected? Will it be rolled out later for beta participants or is it just broken due to high demand?

not able to kick off any builds today getting error unable to connect to git repo. I have verified the git repo and its fine.

I can't use Xcode Cloud in the last days anymore. I've tried it in both Xcode 13.4.1 running on Monterey and Xcode 14 beta running on Ventura beta. All I get is a spinner with the message "Analysing Workspace" and after quite a while an error message saying "Could not load Xcode Cloud data". I've tried this on multiple projects on both apps/platforms. Anyone else having the same problem?

Hello, I am trying out Xcode Cloud for the first time. I could connect to Github in the initial setup and had a few failed builds (package resolution error), which I resolved fairly quickly. Now whenever I am trying to build, I get the following error: Xcode Cloud is unable to connect to the repository “<respository-name>”. Reconnect the repository to resume builds. I am unable to remove the connection from settings as well because it's stuck in a loading state. Is there a way to fix this?

After building my app with Jenkins for 3 years without any problems, I'm now trying to build with Xcode Cloud and I'm getting the following error: ITMS-90045: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.game-center I deleted the capability from the Xcode and the info.plist file, yet I'm still getting the error. Any ideas?

All of my builds get stuck on Archive action - it keeps running forever (10+ hours where it took 30 minutes before for a clean build), and never finishes despite having all subtasks finished (green check). This started to happen on a workflow that has worked reliably for months, right after WWDC22 start - is there a problem with a new version of Xcode Cloud?

Hi there, We've been trying out Xcode Cloud for CI for a couple of months, and it has worked pretty well for the most part, but now we've stumbled on something we just can find the answer to, and I'm hoping for some help. We have a "PR checks" workflow that runs tests and analysis for pull-requests, and a "test and deploy" workflow that runs tests and submits uploads to TestFlight from the master branch. We use custom build scripts in all the right locations to perform additional work for our builds. The problem: Our ci_scripts/ci_post_xcodebuild.sh script cannot be found (and therefore does not execute) when running tests (test-without-building) as part of a test action, but bizarrely only on our "test and deploy" master-branch-workflow. However: The script it found just perfectly in the build-for-testing step of the exact same master-branch-workflow The script is also found perfectly when running test-without-building in our "PR checks" workflow According to the documentation I can find, the ci_scripts/ci_post_xcodebuild.sh should always be available for Test actions in the test-without-building step, regardless of branch. So I don't understand why it would be suddenly missing, and only some times. Here's a log from a fully-working "PR checks" workflow run: And here's an example from a "test and deploy" master-branch-run where the scripts are found in the "Build test"/build-for-testing step, but for some reason not in the "Run test"/test-without-building step: Any help would be appreciated :)

HI there, I just started using Xcode cloud. When building Xcode cloud, two archives are being generated: iOS and macOS. The macOS archive always errors out with: xcodebuild: error: Unable to find a destination matching the provided destination specifier: {generic:1, platform:macOS} I have no intention of my app running on macOS, but if I knew how to fix that, it might be kinda neat. But really, it's unnecessary, so how do I turn it off? Thanks, Kim

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 to get Xcode Cloud?

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?