What would the intended workflow be for setting up ODR tags in a project that is generated by cmake? More generally, what are the strategies of automation and integration when using ODR? All I can find in the documetation is that tags are meant to be created and assigned in Xcode, that is by hand. It is hard to believe a feature like this would be designed and rolled out without some proper ways to utilize it.

Hi, My name is Bin, software engineer at VBreathe in Sydney. We have a mobile app developed in Ionic Angular framework and managed to use xcode cloud to build and deploy the app to TestFlight. It worked well, but the speed is a bit slow, takes around 1 hour to finish the build. After checking the logs, the ci_post_clone.sh script took over 20 minutes to finish, because it installs bunch of tools and node packages, which are necessary to build the app. My question is that is there a way to cache these tools and node packages on xcode cloud, so no need to download & install them in every build? Cheers, Bin

https://developer.apple.com/library/archive/technotes/tn2420/_index.html I found this apple doc for the versioning and that the version number can x.y.z, but I saw some apps in App Store with 4 part versions also. Can you please confirm that the 4 part version is not supported or if there is a recent update documentation for it. And also 18 char limit is including the (.) periods, and regardless of individual part but limit is on total and major.minor.patch can be any length as long total length is upto 18 chars.

Hii Everyone I have set timeoutInterval = 120 but my application got timeout earlier than this timeout anyone know the Reason for this ???

I have been trying to solve this issue for a week, and I know that there are a lot of similar questions like this already solved, but none of them works for me, I would appreciate any help. I am building a CI/CD pipeline for my React Native application, and this is the IOS part. I am trying to build from the Bitbucket Pipelines over an SSH connection on a remote Mac. I am trying to build an Xcode achieve, it works when I do it manually on the remote Mac, from Xcode, but when I run this command I get an error. xcodebuild archive -scheme dst -configuration Release -archivePath ../builds/dst.xcarchive -workspace dst.xcworkspace PROVISIONING_PROFILE_SPECIFIER="test-dst-provisioning-release" -UseModernBuildSystem=NO CODE_SIGN_STYLE="Manual" CODE_SIGN_IDENTITY="Apple Distribution: $(Team code)" This is the error I get: Ld /Users/user931603/Library/Developer/Xcode/DerivedData/dst-gisgtbcaheaxrqbgvvzueprfinbl/Build/Intermediates.noindex/ArchiveIntermediates/dst/InstallationBuildProductsLocation/Applications/dst.app/dst normal arm64 cd /Users/user931603/build/dst-mobile-prototype/ios export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/Users/user931603/.nvm/versions/node/v14.17.6/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/usr/local/munki:/Applications/Xamarin Workbooks.app/Contents/SharedSupport/path-bin" ld: warning: directory not found for option '-L-L/Users/user931603/Library/Developer/Xcode/DerivedData/dst-gisgtbcaheaxrqbgvvzueprfinbl/Build/Intermediates.noindex/ArchiveIntermediates/dst/BuildProductsPath/Release-iphoneos/BoringSSL-GRPC' ld: library not found for -lBoringSSL-GRPC clang: error: linker command failed with exit code 1 (use -v to see invocation) For a while I thought that I have a problem with the Library Search Paths These are my Target - Build settings - Library Search Paths These are my Project - Build settings - Library Search Paths But then it turned out that the achieve works from Xcode, but it doesn't work when I do it remotely on the terminal, so I think there must be an issue with the environment variables or something like this. I use Cocoapods, there can be a problem with that, the settings are the ones generated automatically by React Native. I have no clue about this issue, I would appreciate greatly if you could help!

We got the newly issue that our Test devices keeps us asking for the pin code to "Enable UI Automation". Then it works for some hours or days, but after some time it starts again. "Enable UI Automation" is already enabled in "Settings" - "Developer" menu. The devices are located remotely and we can't access them directly, so this is a big issue for us right now. Is there any way to avoid this?

In particular, network extensions, which need to be installed/activated by the containing app. I'm not particularly great at GUI stuff, so maybe there's a way one can simulate/automate that part? I'm assuming CI testing, presumably done with VMs being created on the fly to build & test. (I admit a historical failure on unit testing for my code, but most of that has historically been kernel code. I'm trying to do better!) I again apologise for my obvious ignorance at some of this.

I have an Xcode 13 project (generated with CMake) with multiple dependencies, each one pulling a different repo. I'd like to use the new Code review mode, however I can't seem to switch which repo the project is looking at. Additionally, I can use the new source control dropdown to checkout different branches however the commit hash that is displayed is from the first alphabetically ordered dependency. Is it possible to scope these features to a specific repo?

This a repost from https://stackoverflow.com/questions/68872891/xcode-13-beta-xcrun-error-failed-to-locate-instruments Please note, I'm looking for /Applications/Xcode.app/Contents/Developer/usr/bin/instruments util (lower-case), not the Instruments app which can be found in Xcode.app/Contents/Applications. I have both Xcode12 and Xcode13-beta-5 on my computer. When run xcrun instruments -w <device id>, Xcode13 says xcrun: error: Failed to locate 'instruments'. Locating the "instruments" in Xcode12: olia@Olhas-MacBook-Pro % ls /Applications/Xcode.app/Contents/Developer/usr/bin/*instruments* # output ✅ /Applications/Xcode.app/Contents/Developer/usr/bin/instruments Locating the "instruments" in Xcode13: olia@Olhas-MacBook-Pro % ls /Applications/Xcode-beta.app/Contents/Developer/usr/bin/*instruments* # output ❌ zsh: no matches found: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/*instruments* Here, Xcode-beta.app is Xcode13, and Xcode.app is Xcode12.

On XCode 12.0.1, I have this intermittent error, is there any way to fix this? t = 0.19s Open <bundle_id> t = 0.29s Launch <bundle_id> <unknown>:0: error: -[<test_name>] : activate application '<XCUIApplicationImpl: 0x600000842d00 <bundle_id> at <app_path>' (current state: Running Background) t = 61.11s Setting up automation session t = 61.13s Wait for <bundle_id> to idle The test continues running for a while, but it failed because of the error during the launch step (0.29s - 61.11s). Also, notice an unexpected long launching here, it normally just takes 10-15s for this step. Thanks

I wrote a few unit test cases using XCTest by mocking the data? Is there any best practice to have multiple test profiles with different data sets? Sometime mock should return nil, sometimes an array with 2 elements and sometimes an array with 10 elements. How to have multiple test profiles?

I've noticed that my app's build number I set in the project doesn't seem to be respected anymore in TF using Xcode Cloud. Is this a new requirement that the build. number follow the CI_BUILD_NUMBER set by Xcode Cloud? Our build process uses the build number to tie into our other build processes (cross-platform). Thanks

I can’t seem to create any bot with Xcode 13 on macOS Monterey. The error message was “The server is currently unable to build for any platforms...” The app I was trying to build was the standard macOS SwiftUI application, straight from the template code. What seems to be the problem here?

Hi everyone, I'm struggling to access a certificate stored in keychain when using LaunchDaemons and would appreciate any advise to improve over my current workaround with an agent. I'm maintaining an M1-based Mac Mini with macOS Big Sur 11.4 as a build client for Gitlab CI. The machine makes itself known to the orchestrating Gitlab server through the so-called gitlab-runner process which regularly polls the Giltab server for build job requests. It would then eventually call xcodebuild to generate artifacts and upload them to Gitlab. In order to have this process startup automatically, I've loaded it through a /Library/LaunchDaemons/gitlab-runner.plist file in launchctl. This setup has been working greatly for months, making the build client immediately available after a reboot without the need to log into it. I've now started to deploy codesign tasks to the build client and encountered issues with keychain access to the certificate. I installed the certificate and performed security find-identity -v -p codesigning in the Terminal to validate correct installation. I have ensured that the codesign tasks succeed when performed through Terminal manually. A popup was shown on first try about codesign wanting to access to the local keychain, which I always allowed. Codesign then reported success: signed Mach-O universal. The behavior is different for my LaunchDaemons-based codesign tasks (spawned under the same user). I've tried multiple permutations for sudo launchctl load -w /Library/LaunchDaemons/gitlab-runner.plist: SessionCreate=true, local keychain: FAIL (errSecInternalComponent) SessionCreate=true, System keychain: FAIL (errSecInternalComponent) SessionCreate=false, local keychain: FAIL (error: The specified item could not be found in the keychain.) SessionCreate=false, System keychain: FAIL (errSecInternalComponent) I've then tried a user agent launchctl load -w ~/Library/LaunchAgents/gitlab-runner.plist: SessionCreate=true, local keychain: FAIL (errSecInternalComponent) SessionCreate=false, local keychain: OK (Popup -> Always allow, signed Mach-O universal) So apparently, the last variant works reliably. However, it has the severe downside that I now need to log in the user after a reboot in order to kick off the agent. Is there a way to make this work with /Library/LaunchDaemons, possibly through some plist property? As a test I've tried to "Allow all applications" to access the private key associated with the Certificate but that didn't change anything. Best regards Maik

Hi, I'm running a CD/CI pipeline with Gitlab which builds and deploy a flutter app via a mac mini M1. Recently we have upgraded xcode to 12.5.1 and our flutter app from v1 to v2, which involved a painful amount of dependencies upgrade. This upgrade has created some issues only on computer with M1 chip. As much as we have fixed most of the issue, 1 remaing is fixable ONLY by manually changing the Target > Build Settings > Architecture from ARCHS_STANDARDS to 'arm64' only. Because each time we deploy a new instance of XCode is created, we can't manually make this change and we need to make it from the code. I've applied this into my Podfile: post_install do |installer| installer.pods_project.targets.each do |target| flutter_additional_ios_build_settings(target) target.build_configurations.each do |config| config.build_settings['ARCHS'] = 'arm64' end end end but unfortunately it doesn't force the ARCHS to change to arm64. Is there a way to do that from the Podfile or any other files in the code? Thanks Matt

My CircleCI workflow has started failing with an error I can't seem to find any documentation for: Could not compute signing task inputs - operation was cancelled. ... and then a reference to a 3rd party library's product, eg.: (in target 'Appboy_iOS_SDK_AppboyKit' from project 'Appboy_iOS_SDK'). I'm using SPM to manage dependencies and I'm trying to modularize my Xcode project by adding a local SPM package. Below is the relevant part of the CircleCI output. I can't seem to figure out what these errors are referring to and they don't seem to occur when I remove UI tests from the scheme, so I'm assuming this has something to do with the "Copy Bundle Resources" step of the "MyAppUITests" target. Any help would be much appreciated. Xcode version: 12.5.1 [00:00:45]: Running Tests: ▸ Touching MyApp.app (in target 'MyApp' from project 'MyApp') [00:00:45]: ▸ Build Succeeded [00:00:45]: ▸ 2021-07-22 00:00:45.521 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa5036121a0> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:45]: ▸ 2021-07-22 00:00:45.526 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa50305bb20> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:45]: ▸ 2021-07-22 00:00:45.531 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa50306a230> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:45]: ▸ 2021-07-22 00:00:45.536 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa503076680> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:45]: ▸ 2021-07-22 00:00:45.549 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa503660a10> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:45]: ▸ 2021-07-22 00:00:45.555 xcodebuild[1629:69156] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-18212/IDEFoundation/Testing/IDETestRunSpecificationBuilder.m:678 [00:00:45]: ▸ Details: Failed to compute path to baseline file during test run spec construction: <XCTHTestRunSpecification: 0x7fa50366c6a0> [00:00:45]: ▸ Object: <IDETestRunSpecificationBuilder> [00:00:45]: ▸ Method: +testRunSpecificationsForTestingSpecifiers:scheme:buildables:withBuildParameters:additionalEnvironmentVariables:additionalCommandLineArguments:testRerunPolicy:includeClangProfileParameters:shouldDebugAppExtensions:error: [00:00:45]: ▸ Thread: <NSThread: 0x7fa4f9618f70>{number = 1, name = main} [00:00:45]: ▸ Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide. [00:00:51]: ▸ ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'Appboy_iOS_SDK_AppboyKit' from project 'Appboy_iOS_SDK') [00:00:51]: ▸ ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'Appboy_iOS_SDK_AppboyUI' from project 'Appboy_iOS_SDK') [00:00:51]: ▸ ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'Mixpanel_Mixpanel' from project 'Mixpanel') [00:00:52]: ▸ Testing failed: [00:00:52]: ▸ Could not compute signing task inputs - operation was cancelled. [00:00:52]: ▸ Testing cancelled because the build failed. [00:00:52]: ▸ ** TEST FAILED **```

There is a question on stackoverflow for that too: https://stackoverflow.com/questions/66143815/xcode-12-5-spm-dependency-cache-location Xcode 12.5 release notes mention the "per-user-basis" cache for SPM dependencies: https://developer.apple.com/documentation/xcode-release-notes/xcode-12_5-beta-release-notes Is the location outside of DerivedData folder so cache still persists somewhere in ~/Library/Caches and can be reused even for clean build? It's very important to know for CI performance! Any guidance/help is appreciated.

After updating the XCode to version 11.4 (11E146), I stopped seeing repository branches in the bot settings. But I see these repository branches in Source Controll Navigator. Does anyone know how I can fix it?