Build, test, and submit your app using Xcode, Apple's integrated development environment.

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

Xcode won’t link a SwiftPM package on macOS using a static library in an XCFramework.
I have a SwiftPM package that has a binary target pointing to a static XCFramework with a binary for macOS x86_64 and arm64 and one for iOS on arm64. If I set the destination to my iPhone, it builds successfully, but if the target is my Mac, it fails with a linker warning saying that it Could not find or use auto-linked library, and later terminating because some symbols are undefined. This only happens when building through Xcode; when I try using swift build, the build completes normally.
1
0
281
Oct ’24
Xcode UI test always fails to tap close button in font picker navigation bar
I'm trying to close the UIFontPickerViewController in a UI test by tapping the close button in the navigation bar. In a default iOS app, I embed the default storyboard view controller in a navigation view controller, then in code I open the font picker like this: class ViewController: UIViewController, UIFontPickerViewControllerDelegate { override func viewDidAppear(_ animated: Bool) { let picker = UIFontPickerViewController(configuration: .init()) picker.delegate = self self.present(picker, animated: true) } func fontPickerViewControllerDidPickFont(_ viewController: UIFontPickerViewController) { } } And the UI test looks like this: final class problemUITests: XCTestCase { @MainActor func testExample() throws { let app = XCUIApplication() app.launch() sleep(2) let button = app.navigationBars.element(boundBy: 1).buttons.element(boundBy: 0) print(button.debugDescription) XCTAssert(button.waitForExistence(timeout: 2)) button.tap() } } When running the UI test, the XCTAssert always fails and the button.tap() also fails with an error message Failed to tap "chiudi" Button: No matches found for Element at index 1 from input {( NavigationBar )} "chiudi" means "close" in Italian, my macOS system language. It sounds to me like I correctly get the close button, but the messages Xcode prints make no sense to me. It's particularly confusing given that the output of the print statement shows that the button is there, but somehow fails to be tapped: Attributes: Button, 0x104f44660, {{701.0, 320.0}, {43.0, 44.0}}, label: 'chiudi' Element subtree: →Button, 0x104f44660, {{701.0, 320.0}, {43.0, 44.0}}, label: 'chiudi' Image, 0x104f44780, {{709.0, 327.5}, {30.0, 30.0}}, identifier: 'UICloseButtonBackground' Path to element: →Application, 0x104f35940, pid: 29803, label: 'problem' ↳Window (Main), 0x104f376a0, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f42e10, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43100, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43220, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43340, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43460, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43580, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f436a0, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f437c0, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f438e0, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43a00, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43b20, {{0.0, 0.0}, {1032.0, 1376.0}} ↳Other, 0x104f43c40, {{276.0, 314.0}, {480.0, 748.0}} ↳Other, 0x104f43e80, {{276.0, 314.0}, {480.0, 748.0}} ↳Other, 0x104f43fa0, {{276.0, 314.0}, {480.0, 748.0}} ↳Other, 0x104f440c0, {{276.0, 314.0}, {480.0, 748.0}} ↳Other, 0x104f441e0, {{276.0, 314.0}, {480.0, 748.0}} ↳Other, 0x104f44300, {{276.0, 314.0}, {480.0, 748.0}} ↳NavigationBar, 0x104f44420, {{276.0, 314.0}, {480.0, 108.0}}, identifier: 'Scegli font' ↳Button, 0x104f44660, {{701.0, 320.0}, {43.0, 44.0}}, label: 'chiudi' Query chain: →Find: Target Application 'org.desairem.problem' Output: { Application, 0x104f781b0, pid: 29803, label: 'problem' } ↪︎Find: Descendants matching type NavigationBar Output: { NavigationBar, 0x10607c0d0, {{0.0, 24.0}, {1032.0, 50.0}}, identifier: 'UIFontPickerView' NavigationBar, 0x10607dab0, {{276.0, 314.0}, {480.0, 108.0}}, identifier: 'Scegli font' } ↪︎Find: Element at index 1 Output: { NavigationBar, 0x1064693a0, {{276.0, 314.0}, {480.0, 108.0}}, identifier: 'Scegli font' } ↪︎Find: Descendants matching type Button Output: { Button, 0x104f714a0, {{701.0, 320.0}, {43.0, 44.0}}, label: 'chiudi' Button, 0x104f71800, {{711.0, 378.0}, {17.0, 22.0}}, identifier: 'Dictate', label: 'Avvia dettatura' } ↪︎Find: Element at index 0 Output: { Button, 0x104f5d5e0, {{701.0, 320.0}, {43.0, 44.0}}, label: 'chiudi' }
0
0
373
Oct ’24
Can't extract Xcode_12.5.1.xip file
I have tried several options so far to no avail: Unarchiver shuts down silently (after ~1.5hr of trying to unarchive). xip console tool fails after ~1.5hr with this error: xip: signing certificate was "Software Update" (validation not attempted) xip: error: The archive “Xcode_12.5.1.xip” failed to be moved to the final destination due to the error: The operation couldn’t be completed. No such file or directory. extracted .app is incomplete though weighs about 30GB unxip extracts for ~1.5hr (being stuck for ~40min on Expanding items from “Xcode_12.5.1.xip”: 99%) and then shuts down. extracted .app is incomplete with the size of ~1.9GB Are there any other options I can try to extract Xcode 12.5.1 xip archive? Would external drive be an issue (I have Xcode_12.5.1.xip on external drive)?
3
0
3.8k
Mar ’25
How to correctly resolve URL bookmarks for use in Simulator UI tests?
To make UI testing easier and faster, I usually create URL bookmarks during normal app usage in the Simulator so that they can be instantly resolved on app launch during UI tests. For example, one of my apps allows browsing selected folders and stores bookmarks so they can be quickly opened again on following app launches, and instead of selecting the test folder each time at the beginning of the UI test, I select it once during normal app usage so that it's available immediately during the UI test. This usually works fine, but every now and then the UI tests fail because the tested app isn't able to resolve the stored bookmark. I don't know why this happens, but usually opening and closing the app again in the Simulator and re-running the UI tests solves the issue. The problem now is that I've just tried to setup some new UI tests for Apple Vision Pro Simulator and I'm never able to resolve bookmarks. So I created a sample project that reproduces the issue, and curiously enough the bookmarks don't even resolve when using an iPad Simulator (which usually works fine with my regular UI tests). What am I doing wrong? This can be reproduced with a default iOS project, embedding the default storyboard view controller in a navigation view controller, and this code: import UIKit class ViewController: UIViewController, UIDocumentPickerDelegate { override func viewDidLoad() { navigationItem.rightBarButtonItem = UIBarButtonItem(systemItem: .add, primaryAction: UIAction(handler: { _ in let picker = UIDocumentPickerViewController(forOpeningContentTypes: [.folder]) picker.delegate = self self.present(picker, animated: true) })) if let bookmark = UserDefaults.standard.data(forKey: "bookmark") { readBookmark(bookmark) } } func readBookmark(_ bookmark: Data) { do { let label = UILabel(frame: CGRect(x: 100, y: 100, width: 600, height: 100)) label.numberOfLines = 0 var stale = false let url = try URL(resolvingBookmarkData: bookmark, bookmarkDataIsStale: &stale) if !url.startAccessingSecurityScopedResource() { fatalError() } label.text = url.path view.addSubview(label) } catch { fatalError(error.localizedDescription) } } func documentPicker(_ controller: UIDocumentPickerViewController, didPickDocumentsAt urls: [URL]) { do { let url = urls[0] if !url.startAccessingSecurityScopedResource() { fatalError() } let bookmark = try url.bookmarkData() UserDefaults.standard.set(bookmark, forKey: "bookmark") readBookmark(bookmark) } catch { fatalError(error.localizedDescription) } } } And a default UI test, which always crashes because of the fatalError() in the catch clause of readBookmark(_:): final class problemUITests: XCTestCase { @MainActor func testExample() throws { let app = XCUIApplication() app.launch() } }
0
0
368
Oct ’24
Cannot get Xcode archive Distribution to install on iOS Device
When I airdrop my archived app to my device it runs perfectly. But when I try to share with colleagues using the manifest.plist in a website link, the app will not install (Even on the same device where the airdropped app did). I get "Unable to Install [app name]" Any help with this will be appreciated. Here is my manifest.plist: `<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>items</key> <array> <dict> <key>assets</key> <array> <dict> <key>kind</key> <string>software-package</string> <key>url</key> <string>https://www.scorcent.com</string> </dict> <dict> <key>kind</key> <string>display-image</string> <key>url</key> <string>https://www.scorcent.com/image_57x56.png</string> </dict> <dict> <key>kind</key> <string>full-size-image</string> <key>url</key> <string>https://www.scorcent.com/image_512x512.png</string> </dict> </array> <key>metadata</key> <dict> <key>bundle-identifier</key> <string>ScorCent</string> <key>bundle-version</key> <string>6.0</string> <key>kind</key> <string>software</string> <key>platform-identifier</key> <string>com.apple.platform.iphoneos</string> <key>title</key> <string>NO REGRETS</string> </dict> </dict> </array> </dict> </plist> `And here is my web url; <a href=itms-services://?action=download-manifest&url=https://www.scorcent.com/manifest.plist" Install App
0
0
189
Oct ’24
Xcode incorrectly shows warnings about missing headers in a framework's umbrella header.
When converting some of our frameworks to universal frameworks (multiple target platforms), error messages appear in Xcode that we believe are incorrect: Something like this: Umbrella header for module ‘TestFramework’ does not include header ‘iOS.h’ This post links to an example project which shows the behaviour (UmbrellaHeadersTest.zip). See the included README.txt Any suggestions on how to reliably eliminate these warnings would be greatly appreciated! UmbrellaHeadersTest.zip
1
0
265
Oct ’24
Simulator not working
Since its update to iOS 18.0, I have not been able to use the Simulator in Xcode at all. It is stuck loading for a very long time, and then it crashes. I managed to get it to start once, but it used up all of my system's memory immediately. I have not had any problems with the Simulator before the iOS 18.0 update. Additionally, after the Simulator crashing, the StoryBoard usually stops working as well, until I restart Xcode. (I use an M1 MacBook Air with 8GB of RAM)
0
0
538
Sep ’24
Xcode build failure
On Xcode when I try to build/run, I get 'React/RCTEventEmitter.h' file not found. The same works when I use yarn ios --simulator <>. I tried installing the latest version of Xcode, still same problem. I have Xcode 16.1 now. Showing Recent Messages ScanDependencies /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.o /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'RNCPushNotificationIOS' from project 'PushNotificationIOS') cd /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios Using response file: /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/e6072d4f65d7061329687fe24e3d63a7-common-args.resp builtin-ScanDependencies -o /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.o.scan -- /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -ivfsstatcache /Users/sunnalla/Library/Developer/Xcode/DerivedData/SDKStatCaches.noindex/iphonesimulator18.1-22B74-3d93aac3a03ebac1dd8474c5def773dc.sdkstatcache -fmessage-length\=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit\=0 -fno-color-diagnostics -fmodules-prune-interval\=86400 -fmodules-prune-after\=345600 -fbuild-session-file\=/Users/sunnalla/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror\=non-modular-include-in-framework-module -Wno-trigraphs -Wno-missing-field-initializers -Wno-missing-prototypes -Werror\=return-type -Wdocumentation -Wunreachable-code -Wno-implicit-atomic-properties -Werror\=deprecated-objc-isa-usage -Wno-objc-interface-ivars -Werror\=objc-root-class -Wno-arc-repeated-use-of-weak -Wimplicit-retain-self -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-float-conversion -Wnon-literal-null-conversion -Wobjc-literal-conversion -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wundeclared-selector -Wdeprecated-implementations -Wno-implicit-fallthrough -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -Wno-sign-conversion -Winfinite-recursion -Wcomma -Wblock-capture-autoreleasing -Wstrict-prototypes -Wno-semicolon-before-method-body -Wunguarded-availability -index-store-path /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Index.noindex/DataStore @/Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/e6072d4f65d7061329687fe24e3d63a7-common-args.resp -MMD -MT dependencies -MF /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.d --serialize-diagnostics /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.dia -c /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.m -o /Users/sunnalla/Library/Developer/Xcode/DerivedData/oceanmobileapp-fqewvpyrkyjkudecrdfhqvtadmcl/Build/Intermediates.noindex/PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.o -index-unit-output-path /PushNotificationIOS.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/arm64/RNCPushNotificationIOS.o /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.h:8:9: error: 'React/RCTEventEmitter.h' file not found (in target 'RNCPushNotificationIOS' from project 'PushNotificationIOS') /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.m:8:9: note: in file included from /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.m:8: /Users/sunnalla/Documents/Ocean/oma_obs_sub/src/node_modules/@react-native-community/push-notification-ios/ios/RNCPushNotificationIOS.h:8:9: 'React/RCTEventEmitter.h' file not found
1
0
686
Oct ’24
Error I can't seem to fix
Hi everyone. I am trying to build an app that's capable of displaying a RTSP stream of my IP camera. I am building it with GStreamer and using a C Bridge Header so it's Swift compatible. I keep getting this error, and I can't figure out how to solve it. I've tried everything I can think of, and everything ChatGPT can think of (lol). Anyone any idea's? Sorry if this post falls in the wrong category. I didn't see any categories that my problem fits in, so I chose this one.
1
0
236
Oct ’24
How to fix this bug?
Hi everyone. Does anyone know how to fix this error message? It pops up when I try to build the code. Changing it from my phone to the simulator doesn't help. The project is located on my Desktop, and I have full read and write access to my Desktop. I can't figure out for the life of me how to fix it :(
0
0
213
Oct ’24
Xcode UI test cannot tap menu button in form
Apparently UI tests are unable to tap menu buttons but can tap regular buttons inside forms. Earlier today I was able to see in the Simulator that the UI test tries to tap the button by tapping the center of the containing form row, which works for regular buttons, but not for menu buttons. In fact, when trying in the SwiftUI preview in Xcode it seems that menu buttons have to be tapped exactly on top of them, while regular buttons can be tapped anywhere in the form row. (Now I’m not able to see touches performed by the UI test anymore in the Simulator for an unknown reason, even though I have “Show single touches” enabled in the Simulator settings.) How can I open a menu button in a UI test? The UI code: struct ContentView: View { @State private var label1 = "Menu 1" @State private var label2 = "Menu 2" var body: some View { NavigationStack { Form { LabeledContent("Menu 1") { Button(label1) { label1 = "Menu 1 tapped" } .accessibilityIdentifier("menu1") } LabeledContent("Menu 2") { Menu(label2) { Button("Button") { } .accessibilityIdentifier("button") } .accessibilityIdentifier("menu2") } } } } } #Preview { ContentView() } And the test: final class problemUITests: XCTestCase { func testExample() throws { // UI tests must launch the application that they test. let app = XCUIApplication() app.launch() app.collectionViews.element(boundBy: 0).buttons["menu1"].tap() app.collectionViews.element(boundBy: 0).buttons["menu2"].tap() app.collectionViews.element(boundBy: 0).buttons["button"].tap() } }
2
0
674
Oct ’24
Example of creating NSView with custom bindings
Does anyone know where I can find an example of creating a NSView subclass with custom bindings. I need to be able to bind to the object in interface builder. This is the only reference in Apple documents but as is often the case there appear to be no examples. https://developer.apple.com/documentation/objectivec/nsobject/nskeyvaluebindingcreation
0
0
186
Oct ’24
iPhone device error connect to xcode
ast login: Fri Oct 25 05:07:33 on console m@ms-MacBook-Pro ~ % xcrun devicectl device info details --device Error: Missing value for '--device <uuid|ecid|serial_number|udid|name|dns_name>' Help: --device <uuid|ecid|serial_number|udid|name|dns_name> The identifier, ECID, serial number, UDID, user-provided name, or DNS name of the device. Usage: devicectl device info details --device <uuid|ecid|serial_number|udid|name|dns_name> [--verbose] [--quiet] [--timeout ] [--json-output ] [--log-output ] See 'devicectl device info details --help' for more information. m@ms-MacBook-Pro ~ % xcrun devicectl device info details --device 00008020-00111D211A41002E Gathering device information... WARNING: Unable to retrieve complete information for this device. The best available information will be returned. Error: The tunnel connection failed while the system tried to connect to the device. Current device information: • identifier: DEF927A2-8A74-4AC2-860B-41971982EAB5 • tags: ▿ hardwareProperties: • cpuType: arm64e (type: 16777228, subtype: 2) • deviceType: iPhone • ecid: 4817102615674926 • hardwareModel: N841AP • platform: iOS • productType: iPhone11,8 • supportedDeviceFamilies: [1] • udid: 00008020-00111D211A41002E ▿ deviceProperties: • ddiServicesAvailable: false • name: iPhone • osBuildUpdate: 22A3370 • osVersionNumber: 18.0.1 ▿ connectionProperties: • authenticationType: manualPairing • isMobileDeviceOnly: false ▿ potentialHostnames: • 00008020-00111D211A41002E.coredevice.local: 00008020-00111D211A41002E.coredevice.local • DEF927A2-8A74-4AC2-860B-41971982EAB5.coredevice.local: DEF927A2-8A74-4AC2-860B-41971982EAB5.coredevice.local • pairingState: paired • transportType: wired • tunnelTransportProtocol: tcp • tunnelState: disconnected ▿ capabilities: • Acquire Usage Assertion (com.apple.coredevice.feature.acquireusageassertion): Acquire Usage Assertion (com.apple.coredevice.feature.acquireusageassertion) • Unpair Device (com.apple.coredevice.feature.unpairdevice): Unpair Device (com.apple.coredevice.feature.unpairdevice) • Connect to Device (com.apple.coredevice.feature.connectdevice): Connect to Device (com.apple.coredevice.feature.connectdevice) • visibilityClass: default m@ms-MacBook-Pro ~ %
0
0
471
Oct ’24
Re: "Unknown Apple ID" entries in Xcode Accounts settings
Hello! This post is a response to another post from Oct 17 that has already been locked for some reason: https://forums.developer.apple.com/forums/thread/766500 After upgrading to Xcode 16.0, our build machine was no longer able to archive and upload builds to App Store Connect automatically, as every single time it would say: `IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account` I tried using the workaround in the post above as suggested, but it does not help the problem. Removing and signing out of the account just results in Xcode not being able to do automatic signing because it no longer has access to the account with privileges to do that automatic signing. error: exportArchive No Accounts error: exportArchive No signing certificate "iOS Distribution" found I also tried Xcode 16.1 beta 3 as suggested and now the build machine's account is actually removed after every build via our build system! I have to log on after every build, log back in, and then upload the build to App Store Connect manually. I'm guessing that this "workaround" was added to Xcode itself, which is not serving its intended purpose and has actually made things worse. Not sure if there is a more official venue to send a bug report, but I'm posting here for help since that's where I originally found the post and it appeared to be written by an Apple engineer. Any other possible workarounds? Should I try one of the newer beta releases? Any help would be appreciated as this is becoming very cumbersome and a routine update of Xcode on our build machine has caused a ton of headaches.
6
0
914
Oct ’24
Unable to run test in devices with MDM Profiles
Requirement : We wanted to run UI Automation using xcuitest in devices with MDM profiles. Steps : We have created a test target for our app and signed with MDM profile (in-house) Generated app and testbundle-Runner along with xctestrun files using “xcodebuild build-for-testing -scheme “App-TestRelease" -configuration “Release” -derivedDataPath "${CURDIR}/derivedData" -workspace "${PROJECT_NAME}.xcworkspace" -sdk iphoneos” Tried running “xcodebuild test-without-building -destination platform=iOS,id=000842883-**** -xctestrun App-TestRelease_iphoneos17.5-arm64.xctestrun -derivedDataPath /derived/“ Facing below issues xcodebuild[35481:3588352] IDELaunchReport: e2934a094f300d40:e2934a094f300d40: Finished with error: Unable to launch com.org.mdm.XCTest.xctrunner Domain: com.apple.platform.iphoneos Code: -12 User Info: { IDERunOperationFailingWorker = IDELaunchiPhoneLauncher; } -- Request to launch com.org.mdm.XCTest.xctrunner failed. Domain: com.apple.dt.deviceprocesscontrolservice Code: 2 Failure Reason: The request to open "com.org.mdm.XCTest.xctrunner" failed. : Failed to launch process with bundle identifier 'com.org.mdm.XCTest.xctrunner'. -- The request to open "com.org.mdm.XCTest.xctrunner" failed. Domain: FBSOpenApplicationServiceErrorDomain Code: 1 Failure Reason: The request was denied by service delegate (SBMainWorkspace) for reason: Security ("Unable to launch com.org.mdm.XCTest.xctrunner because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user"). User Info: { BSErrorCodeDescription = RequestDenied; FBSOpenApplicationRequestID = 0x9f9; } -- The operation couldn’t be completed. Unable to launch com.org.mdm.XCTest.xctrunner because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. Domain: FBSOpenApplicationErrorDomain Code: 3 Failure Reason: Unable to launch com.org.mdm.XCTest.xctrunner because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user. User Info: { BSErrorCodeDescription = Security; }
1
0
687
Oct ’24