When trying to build other branch than develop it says that my branch may only exist locally. All branches are published in the remote, so i don't know why is this happening... here is a screenshot of what i'm getting same goes for the scheme which is marked as shared and pushed to the repo...

When trying to create a new workflow for a framework product, Xcode fails, displaying the error: “MyFramework” could not be added to Xcode Cloud.” This framework previously had a workflow running on Xcode Cloud, but it is no longer visible, both in Xcode and App Store Connect. I was trying to recreate the workflow, as well as setup some additional ones, but I get the same error for every single product. No other details are provided by Xcode, so I’m unable to determine what steps I should take to correct the issue. I'm able to reproduce this with every xcworkspace file I have tried so far. Using Xcode 13.1 (13A1030d) It would be great if Xcode could provide some sort of detail with these error messages so that devs would know whether there is something wrong on the Cloud side, or if it's something that I can try fixing on my side.

Today, playing with Xcode cloud I came across a really nasty, undesirable effect of executing steps in an undocumented order. I had a project with a brand new workflow, I had it linked to my SCM (gitlab self-hosted) and it worked. Today, it didn't work so I thought, OK, this thing is beta and something must not be working that well, let's reset everything and start over. I deleted the workflow, then cleared the Xcode cloud data (this removes everything from your Xcode cloud tabs on your product and, unfortunately, from your profile as well). Then proceed to navigate to your profile to unlink the SCM connection and it appears to be empty. Because of this, I removed my application in gitlab (which is the token provider for oath) to start again, thinking I did something wrong and I want to follow the steps brand new again. I went to Xcode, tried to create a new workflow and link my source control provider and... I get a "continue to authorise your repository" button, which is now broken because that application doesn't exist. The question is, does anybody know of a way to unlink my SCM from my account? The Xcode cloud tab under my profile tells me I need to create a workflow to access anything from there, but I am completely unable to complete that creation as the workflow requires it to be connected to a self hosted instance. This was extremely easy to get wrong.

When we provide gitlab API key & secret in xcode cloud using an appstoreconnect account, will other appstoreconnect user be able to access that source code using that key/secret info?

Hey i have been trying to test out Xcode cloud integration with our project code base hosted in bitbucket cloud. But i can seem to get ti to work correctly. Eg : i have set up a work flow for Every Change to pull request and added a target branch, but the work flow doesn't get triggered at all. Only when i do a manual In addition some for the Xcode 13 source code management features don't seem to work like viewing and raising pull requests etc. As you can seen below no option for create pull request Is butbucket cloud fully supported or am i missing something here

It is not clear on what architecture Xcode cloud executes Mac tests. Ideally, I would like to run a test on both platforms and compare the results. Am I missing something or is this just not there yet?

Hello, We got invited to the Xcode Cloud beta and I added one of our projects. It looks like the archive succeeds but it always reports an error. How can I get this looked at? Thank you

When I first create workflow, I want to connect my source code to bitbucket server, but I was stuck in connecting step, just look the images below. I keep getting 500 error. How can I connect to Github or Gitlab? I can't find a way to switch or change, please help me, thank you.

I am trying to run macOS unit test on XCode Cloud, but failed with following message. It runs smoothly locally on my Mac. Tests macOS-Runner (29166) encountered an error (Failed to check for UI testing permission for the test runner process. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundle.xcresult. (Underlying Error: Unable to run UI Tests because Xcode Helper does not have permission to use Accessibility. To enable UI testing, go to the Security & Privacy pane in System Preferences, select the Privacy tab, then select Accessibility, and add Xcode Helper to the list of applications allowed to use Accessibility))

I have uploaded iOS and macOS builds with Xcode Cloud, and I can't pass "ready to submit" status. A internal testing group is grayed and I can't select it. External testing group don't show. Trying to add an individual and hit "submit to review" I get "There was an error processing your request. Please try again."

Frequently when Xcode builds our app we end up (after two hours) getting a build failure: The archive action was stopped because it has exceeded the maximum time allowed to run. Actions are limited to 120 minutes. Other times, it completely successfully in about 35 minutes. It seems to randomly happen. Is this a known issue?

I see that the cache function is not working. I want to cache some build folders, cocoapods,...Please help me. Thanks!

When setting up my first workflow, I am prompted to grant XCode Cloud access to our BitBucket Server. I press Grant and appstore connect opens up and prompts me to enter a personal access token. After adding that token and pressing register, the button spins for a bit, then stops and an error in the Javascript console appears (500-Aborted). We've added the necessary IPs to our Firewall whitelist but still no luck. Does anyone know how to solve this? Thanks!

We are deploying development builds on a staging environment with multiple feature branches. Using testflight is very handy for our team, but we have a real issue in identifying which build is using which branch. Currently, I have to manually write in the "Test Details" for every build that i upload if i want to let other testflight users from the team know what feature is on what build. This would be easily solved by having an option to automatically use the branch name as the default "Test Details" message, so they can easily be identified in Testflight among the builds list. Is there any plan to add such an option?

Xcode Cloud seems to be stuck at Xcode 13.2 beta 2 even if the release candidate (13C90) came a week ago and got realeased yesterday. It builds fine but the builds are rejected by App Store Connect because they were built with an obsolete version. Any tricks to convince Xcode Cloud to use the Xcode 13.2 (13C90)?

We're getting this error with Xcode Cloud, it is failing due to SSL issues while it's passing locally and works fine on another CI platforms with Instabug’s deployment server. Here's the error xcodebuild: error: Could not resolve package dependencies: failed downloading 'https://ios-releases.instabug.com/release/Instabug/10.11.0/archive.zip' which is required by binary target 'Instabug': downloadError("Error Domain=NSURLErrorDomain Code=-1200 \"An SSL error has occurred and a secure connection to the server cannot be made.\" UserInfo={NSErrorFailingURLStringKey=https://ios-releases.instabug.com/release/Instabug/10.11.0/archive.zip, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDownloadTask <E64EE5B2-BC4A-4181-A386-6AC2BBD8FBF6>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(\n \"LocalDownloadTask <E64EE5B2-BC4A-4181-A386-6AC2BBD8FBF6>.<1>\"\n), NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., NSErrorFailingURLKey=https://ios-releases.instabug.com/release/Instabug/10.11.0/archive.zip, NSUnderlyingError=0x600001f31f80 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 \"(null)\" UserInfo={_kCFStreamPropertySSLClientCertificateState=0, _kCFNetworkCFStreamSSLErrorOriginalValue=-9836, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9836, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: utun3, ipv4, dns}}, _kCFStreamErrorCodeKey=-9836}") fatalError

I am using a cocoapod script that does the following on postinstall: sed -i -e $'s/ && (__IPHONE_OS_VERSION_MIN_REQUIRED < __IPHONE_10_0)//' Pods/RCT-Folly/folly/portability/Time.h This works perfectly when doing pod install locally. However, on Xcode Cloud this is the result: sed: Pods/RCT-Folly/folly/portability/Time.h: No such file or directory This makes me think the pod install command is receiving the wrong CWD or something really weird. I had to manually add the sed command to the ci_post_clone.sh script like this: sed -i -e $'s/ && (__IPHONE_OS_VERSION_MIN_REQUIRED < __IPHONE_10_0)//' /Volumes/workspace/repository/ios/Pods/RCT-Folly/folly/portability/Time.h It appears to find the file only with the volume path in front within xcode cloud. If this isn't fixed, React Native developers are going to be very confused why builds are failing. I just happened to see the sed error when running pod install after spending a while debugging this.

While local builds and builds on virtual machines as e.g. GitHub Actions work well, our native iOS apps do not build with Xcode cloud. The failure is as following - the config files are available in local builds. I wonder why Xcode cloud has trouble finding or opening them? 2021-11-27T10:58:30.190661Z /Volumes/workspace/repository/ios/Pods/Target Support Files/Pods-TreecounterApp/Pods-TreecounterApp.release.xcconfig:1:1: error: unable to open file (in target "TreecounterApp" in project "TreecounterApp") 2021-11-27T10:58:30.190714Z /Volumes/workspace/repository/ios/Pods/Target Support Files/Pods-TreecounterApp/Pods-TreecounterApp.release.xcconfig:1:1: error: unable to open file (in target "TreecounterApp" in project "TreecounterApp") 2021-11-27T10:58:30.190763Z /Volumes/workspace/repository/ios/Pods/Target Support Files/Pods-TreecounterApp/Pods-TreecounterApp.release.xcconfig:1:1: error: unable to open file (in target "TreecounterApp" in project "TreecounterApp") 2021-11-27T10:58:30.190820Z 2021-11-27T10:58:30.191118Z Result bundle written to path: 2021-11-27T10:58:30.191243Z /Volumes/workspace/resultbundle.xcresult 2021-11-27T10:58:30.191297Z 2021-11-27T10:58:30.191345Z ** ARCHIVE FAILED **

Builds worked fine until yesterday, and now we're getting this error about the logs. Seems the build goes fine, just no logs artifacts are generated: Save artifacts 5.5s Upload ERN Build 200101 Logs for ERN archive 0.2s An internal error occurred while this artifact was being saved. Upload ERN Build 200101 XCResult for ERN archive.xcresult 0.0s Upload ERN Build 200101 Archive for ERN on iOS.xcarchive 0.0s Upload ERN 5.6.0 app-store 0.0s Upload ERN 5.6.0 ad-hoc 0.0s Upload ERN 5.6.0 development 0.0s Anyone else experienced this?

Is there a way I can have multiple build/archive actions on my Xcode Cloud workflow that passes in the -configuration flag to the xcodebuild command. I want to build 2 or more build configurations in my workflows.