Hi! I have a big problem about crash feedback. In my app, "Open in Xcode" is not showing when user devices are more than iOS 16.4(maybe 16.5). There are screenshots. I archive my app by Xcode Cloud. iOS16.6 iPhone13 iOS 16.3.1 iPhone SE iOS 16.5 iPhone SE

I'm encountering an authorization issue while attempting to build my app project using Xcode Cloud. My project includes a Git submodule hosted on our self-hosted GitLab instance (the main repository is on the same instance). During the build process, I receive the following error message: "An additional repository requires authorization." The logs are are showing that there was an attempt to clone the submodule via ssh. When I created the workflow, It managed to establish the connection between App Store Connect and the Gitlab instance. For both the main repository and the submodule. The settings of my app shows the primary repository but no additional repositories. Adding the submodule to the primary repositories did not help. Changing the cloning configuration for the submodule from SSH to HTTPS is NOT an option. Are there any additional steps which need to be taken?

I have an macOS app, where the user can open/drag a folder so that the contents can be listed and used. The app saves the bookmark data for these folders and restores them the next time the app runs. This works perfect on the development machines and on thousands of users' Macs. Recently I added UI tests which perform a couple if happy path tests and they are helping a lot. One of the tests adds a folder and tries to use an image which is in the folder. The folder is copied from the test bundle to the Desktop at the beginning of the test. This works both locally (on my Mac) and on two CI "servers" (latest macOS, Xcode Server). At the moment I try to migrate to Xcode Cloud. Unit tests run fine (after disabling the Hardened Runtime). However, I do not get the UI tests to succeed. They run and add the folder, however, the URL's bookmark data creation fails. I tried to track the differences during the build and found Xcode Cloud builds always being adhoc-signed. Running the UI tests locally but signing the app (and the tests) adhoc too does not result in the same problem. Problem in short: user selects folder (using NSOpenPanel or Drag'n'Drop) url.bookmarkData() works locally and in Xcode Cloud url.bookmarkData(options: [.withSecurityScope]) only works locally but not in Xcode Cloud This is easily reproducible with a very simple project which I can hand-out if needed. Anybody a hint or idea? Since those folders are essential for the app, not solving this would render Xcode Cloud completely useless for me. Thanks! Daniel

I am trying to Integrate of Xcode Cloud with Flutter iOS project. But, getting the error of Command PhaseScriptExecution failed with a nonzero exit code. Kindly find the screenshot for the same and share the your valuable suggestions. Thank!

Hello! In Xcode 15 beta 1-5, a large number of old Xcode Cloud entries are displayed in the Report Navigator. These old entries do not contain any content. This issue does not occur when viewing the same project in Xcode 14.

It seems that Xcode Cloud currently only uses Intel machines for running the workflow jobs. When will Apple Silicon machines be available and supported?

I'm trying to connect my Developer Account in App Store Connect with Slack for CI notifications from Xcode Cloud. Apple docs for reference: https://developer.apple.com/documentation/xcode/connecting-xcode-cloud-to-slack#Install-the-Slack-app-for-Xcode- Cloud-using-App-Store-Connect I've tried connecting to the Slack workplace from the App Store Connect User settings and from Xcode Cloud in Xcode and on App Store Connect but no luck so far. The process always goes through and the Xcode Cloud Slack app gets installed on the Slack workspace. However it does not show up on the App Store Connect. I’ve attached a screenshot of the App Store Connect Notification Settings page after I went through the “Slack | Connect” flow successfully. It states “Your Slack account for has been connected”. However The Slack account still does not show as connected on the same page under "Send To”. Any help appreciated! Was anyone able to connect successfully?

Hello, I am attempting to use Xcode Cloud to build my application (specifically running the 'xcode archive' command); however, have been running into an issue relating to certificate signing. All the questions/documentation surrounding this issue seem to be related to local builds. For the project, I'm using automatic signing with my org as the 'Team' without a Provisioning Profile. I have 'Apple Development' set as the 'Code Signing Identity' with 'Code Signing Style' set to 'Automatic'. The error I'm getting: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "<TEAM_ID>" with a private key was found. (in target '<PROJECT_NAME>' from project '<PROJECT_NAME>') Any would would be greatly appreciated. Thanks!

Hello Apple team, We're having a problem submitting one of our apps to TestFlight via Xcode Cloud. We have over 10 apps with the same codebase and all of them build successfully. However, one application fails to build in Xcode Cloud, although there is no problem with manual build. We would appreciate your help in resolving this situation. Can you please help us resolve this issue? We are ready to provide additional information or logs to clarify the causes of the error. Sincerely, Anton Babich Xcode Cloud Archive - iOS encountered a failure that caused the build to fail. Prepare Build for App Store Connect Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “moBiel Live.app/Frameworks/grpcpp.framework/grpcpp” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. Prepare Build for App Store Connect Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “moBiel Live.app/Frameworks/Braintree.framework/Braintree” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing.

I've noticed that, as of a couple of weeks ago (8 July 2023 for me), I'm unable to export my iOS app via Xcode Cloud for TestFlight. Locally, I'm able to build, archive, and publish normally, and Xcode Cloud can still run unit tests just fine. I looked at some forum posts here to look for similar behaviors, but it's mixed. There was a suggestion to try removing the entitlements file, but that didn't change anything. Looking into the logs, I notice this small section (redacted sensitive information): 2023-07-15T22:36:04.870127483Z 2023-07-15 15:36:03.163 xcodebuild[6074:28093] [MT] DVTServices: No capabilities user data file found for team [REDACTED], appID Optional("[REDACTED]") and appIDType DVTPortalAppIDType(rawValue: 0) 2023-07-15T22:36:04.870197463Z 2023-07-15 15:36:03.163 xcodebuild[6074:28093] [MT] DVTServices: Platform " iOS" is provisioning with the following filtered set of entitlements, "[:]" 2023-07-15T22:36:04.914691936Z error: exportArchive: codesign command failed (/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~LNLf0B/Root/Payload/Fedigardens.app: replacing existing signature 2023-07-15T22:36:04.914761632Z /Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~LNLf0B/Root/Payload/Fedigardens.app: Operation not permitted 2023-07-15T22:36:04.915067844Z ) 2023-07-15T22:36:04.915208428Z 2023-07-15T22:36:04.915743970Z DVTFoundation.DVTCodeSignerError.signingFailed("/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~LNLf0B/Root/Payload/Fedigardens.app: replacing existing signature\n/Volumes/workspace/tmp/XcodeDistPipeline/XcodeDistPipeline.~~~LNLf0B/Root/Payload/Fedigardens.app: Operation not permitted\n") 2023-07-15T22:36:04.915864076Z Has anyone else run into this issue recently? My environment for Xcode Cloud: Xcode Version: 15.0 beta 4 macOS Version: 14.0 (Sonoma) beta 2

I have a repo with hundreds of tags (we make a tag for every build and for every version, and it has a browser extension project pulled in as a subtree where all those commits can and do have version tags of their own). I am trying to create a simple tag-triggered workflow to release my app to the external users and the app store, so I want to trigger it every time I update and push an e.g. latest tag. I created a workflow and setup the tag trigger accordingly, but, in the workflow config, it says it can't find the tag. I saved the workflow anyway, however, when I try to manually trigger the workflow and browse the Tags tab, I only see a subset of the repo's tags. I suspect Xcode Cloud might be limiting the number of tags it pulls and consequently shows when searching tags. I think this is a bug/shortcoming of Xcode Cloud. Is there any way to work around this?

Though everything works fine locally, while trying to build a project in xcode cloud, i get the error archive of binary target 'libjsoncpp.a' does not contain expected binary artifact named 'libjsoncpp.a' It is referenced in a Package.swift file as so .binaryTarget( name: "libjsoncpp.a", url: "https://github.com/Imajion/libjsoncpp.a/releases/download/r3/libjsoncpp.a.xcframework.zip", checksum: "f29acc8d9e5b983fde90d2f8b8c8091bed8c25d42cc58d487ef0b8f7db303ba6" ), I've also tried checking the .zip into the project and referencing locally as such .binaryTarget(name: "libopen3d.a", path: "./PreBuilt/libopen3d.a.xcframework.zip"), However I get the same error. Can anyone offer any insight? The error is quite vauge. The link above is valid if anyone would like to check the archive.

Hi community: I'm coming across two error types on Xcode cloud during ui tests. encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal kill before starting test execution. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/resultbundlexcresult)) encountered an error (Failed to prepare device 'Clone 7 of iPhone 14 Pro' for impending launch. If you believe this error represents a bug, please attach the result bundle at /Volumes/workspace/ resultbundle.xcresult. (Underlying Error: Unable to boot the Simulator. launch failed to respond. (Underlying Error: Failed to start launch_ sim: could not bind to session, launchd_sim may have crashed or quit responding))) Any ideas on how to solve them? Thanks

Hello, I am inquiring about the custom build script of Xcode Cloud. I added ci_post_xcodebuild.sh to the Post-Xcodebuild step according to the guide in the official document. I have some questions while using environment variables in Custom script. Will the IPA files stored in the environment variables CI_AD_HOC_SIGNED_APP_PATH, CI_APP_STORE_SIGNED_APP_PATH, CI_DEVELOPMENT_SIGNED_APP_PATH be uploaded to the App Store? If not, I wonder how the IPA files uploaded to the AppStore are processed and saved in which path. Also, if number 1 is wrong, for what purpose are these environment variables provided? I'll be waiting for the reply. Thank you.

Xcode cloud builds were failing with the following error. It wasn't the problem before yesterday morning 26.Apr.2023 before 1:00 PM. Please let me know what the issue is or if there is anything I can do to solve this. Additional information: The app is a react-native app. error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 fatal: expected flush after ref listing info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. [in /Volumes/workspace/repository/ios] [!] Invalid Podfile file: cannot load such file -- /Volumes/workspace/repository/node_modules/react-native/scripts/react_native_pods. from /Volumes/workspace/repository/ios/Podfile:1 ------------------------------------------- require_relative '../node_modules/react-native/scripts/react_native_pods' require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules' ------------------------------------------- Error Command exited with non-zero exit-code: 1

I am developing my project in expo. I manage to generate the development build on the emulator and on my device.. I can also send the .ipa file to Apple connect but the build never arrives on the panel. I opted for xcode cloud but when trying to generate the build I come across this error unable to open configuration settings file Pods-project.release.xcconfig:1, could someone help me?

After creating a new build and release with XCode Cloud, uploading a zip of the dSYMs to Firebase Crashlytics no longer gets processed. Despite uploading several times I'm still seeing errors like: This app has 15 unprocessed crashes. Upload 1 dSYM file to process them. Has something changed in the last 2-4 weeks in this process that I'm unaware of? TIA

I'm new to Xcode cloud and I am having trouble granting my GitHub repository access to Xcode cloud on my corresponding iOS app project, and I discovered that the username specified in the grant access window is listed my old GitHub username. Therefore, when trying to grant access to the corresponding source code, it gives me an error. I already unlinked and relinked my GitHub account to Xcode and it doesn't resolve. How can I relink my GitHub account so that on Xcode it will show as my current GitHub username? Also my repository is private. Does it only work when it's public?

I have created a Swift package build tool plugin for colour generation. The plugin takes two input files from a project or swift package and from them generates a new Swift file containing references to all of the generated UIColors. When building locally and when using Github Actions the plugin is able to generate the required file within the pluginWorkDirectory and the project that references it can then access it as an input file during its build process. However, when building my project using Xcode Cloud, the plugin appears to be unable to create the file, it fails with the following error: Error while generating colours Files encountered an error at '/Volumes/workspace/DerivedData/SourcePackages/plugins/GLA.output/GLA/ColorGeneratorPlugin/GeneratedColors/Colors.swift'. 2022-11-22T15:46:11.344345498Z Reason: fileCreationFailed 2022-11-22T15:46:11.344390826Z LLVM Profile Error: Failed to write file "default.profraw": Operation not permitted` This then means that the build of the project fails with this error: Error opening input file '/Volumes/workspace/DerivedData/SourcePackages/plugins/GLA.output/GLA/ColorGeneratorPlugin/GeneratedColors/Colors.swift' (No such file or directory) It appears that Xcode Cloud is blocking the creation of files in the pluginWorkDirectory, even though locally it can. Has anyone faced a similar issue? Is there anything I can do to make it work in Xcode Cloud?

Can we get a new feature? Ability to set the bundle ID via the API for Xcode Cloud? When we run multiple version - we want to set it to be the same as our Bitbucket bundle number. And we do a ton of builds that are not sent to Xcode Cloud. So if we could set the next build number (the UX already has this - but need it programmatically). https://developer.apple.com/documentation/appstoreconnectapi/xcode_cloud_workflows_and_builds