I’m trying to integrate our app with the iXGuard obfuscation tool, which needs to run in the archive post-actions step in Xcode Cloud. The issue is: iXGuard takes a long time to complete and, during its execution, does not generate any console output or logs in the Archive Post-actions step. Problem: When Archive Post-actions runs for a long time without producing log output, Xcode Cloud triggers a timeout and the workflow stops before running the next CI step (e.g., ci_post_xcodebuild.sh). Even though the script continues running in the background, the workflow is aborted due to inactivity in the logs. Workaround Tried: As a workaround, I have ci_post_xcodebuild.sh print the logs generated by archive post-actions. However, this does not help in my case since the timeout occurs before ci_post_xcodebuild.sh even runs. Error: The step invocation hit a user timeout. The xcodebuild archive invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Question: Is there a recommended way to prevent Xcode Cloud from timing out during long-running steps that do not produce log output? Are there best practices for keeping the workflow alive with periodic logs during Archive Post-actions? Any support or workaround for integrating tools like iXGuard that require significant processing time after the archive step? Thanks in advance for your help!

Good morning all, We have an on-premise instance of Bitbucket (v8.19.25), using a custom port. We'd like to try using Xcode Cloud, compare to our current CI/CD provider. Once I have to select my source control provider to grant access, I select Bitbucket Server. If I try to input the Host Name with, or without a port, I'm receiving this response: { "message": "An error occurred", "details": [ { "message": "An error occurred", "source": "host" } ], "actions": [], "recovery_actions": [ { "dismiss_label": "OK" }, { "feedback_label": "Provide Feedback", "feedback_component": "Xcode Cloud | New Bugs" } ], "should_show_error": true } Which, of course, doesn't help me in the slightest to understand why the connection fails. I do notice that the request to https://appstoreconnect.apple.com/ci/api/teams/<id>/setup-flow/scm-repositories in the web inspector already includes a host and port that I use to clone the repository locally. However, the web-based interface of Bitbucket doesn't include that port. So, if I clone a repo: ssh://<bitbucket-instance>:<port>, but if I look at pull requests: https://`. My colleagues have already determined that there shouldn't be any firewall rules or gateway limits, so Bitbucket should be reachable. No VPN either. How can I continue to fix this?

My workflow is using Xcode 16.4 and macOS Tahoe 26.2 (25C56). I am trying to change Xcode version to 26.2. When I click Save after some time I get "Something went wrong" error message without any additional details (see screenshot). I get the same error for the following cases: Tried changing a different workflow Tried to deactivate a workflow Tried various combinations of Xcode (26.1, 26.1.1, 26.2) + mac OS (26.1, 26.2) Tried creating a new workflow with Xcode 26.2 (haven't tried any other Xcode versions though)