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

Posts under Xcode tag

200 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

Xcode 15.4 (15F31d) build error: The file “BuildProductsPath” couldn’t be opened because there is no such file.
Hello, When I try to build my project using Xcode 15.4, I get this error: $ xcodebuild BUILD_DIR=/Volumes/C931_SSD/mkl/src/dsym_test/build OBJROOT=/Volumes/C931_SSD/mkl/src/dsym_test/.objs SYMROOT=/Volumes/C931_SSD/mkl/src/dsym_test/.sym -configuration Release -hideShellScriptEnvironment -project /Volumes/C931_SSD/mkl/src/dsym_test/dsym_test.xcodeproj build archive -scheme dsym_test -archivePath /Volumes/C931_SSD/mkl/src/dsym_test/build/dsym_test.ios.xcarchive -sdk iphoneos SKIP_INSTALL=NO Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild BUILD_DIR=/Volumes/C931_SSD/mkl/src/dsym_test/build OBJROOT=/Volumes/C931_SSD/mkl/src/dsym_test/.objs SYMROOT=/Volumes/C931_SSD/mkl/src/dsym_test/.sym -configuration Release -hideShellScriptEnvironment -project /Volumes/C931_SSD/mkl/src/dsym_test/dsym_test.xcodeproj build archive -scheme dsym_test -archivePath /Volumes/C931_SSD/mkl/src/dsym_test/build/dsym_test.ios.xcarchive -sdk iphoneos SKIP_INSTALL=NO User defaults from command line: HideShellScriptEnvironment = YES IDEArchivePathOverride = /Volumes/C931_SSD/mkl/src/dsym_test/build/dsym_test.ios.xcarchive IDEPackageSupportUseBuiltinSCM = YES Build settings from command line: BUILD_DIR = /Volumes/C931_SSD/mkl/src/dsym_test/build OBJROOT = /Volumes/C931_SSD/mkl/src/dsym_test/.objs SDKROOT = iphoneos17.5 SKIP_INSTALL = NO SYMROOT = /Volumes/C931_SSD/mkl/src/dsym_test/.sym ... Touch /Volumes/C931_SSD/mkl/Library/Developer/Xcode/DerivedData/dsym_test-dvvdlvvpbksoxtdglgoqprywugha/Build/Intermediates.noindex/ArchiveIntermediates/dsym_test/InstallationBuildProductsLocation/Library/Frameworks/dsym_test.framework (in target 'dsym_test' from project 'dsym_test') cd /Volumes/C931_SSD/mkl/src/dsym_test /usr/bin/touch -c /Volumes/C931_SSD/mkl/Library/Developer/Xcode/DerivedData/dsym_test-dvvdlvvpbksoxtdglgoqprywugha/Build/Intermediates.noindex/ArchiveIntermediates/dsym_test/InstallationBuildProductsLocation/Library/Frameworks/dsym_test.framework warning: Stale file '/Volumes/C931_SSD/mkl/src/dsym_test/build/Release-iphoneos/dsym_test.framework/Info.plist' is located outside of the allowed root paths. warning: Stale file '/Volumes/C931_SSD/mkl/src/dsym_test/build/Release-iphoneos/dsym_test.framework/dsym_test' is located outside of the allowed root paths. 2024-06-10 17:04:45.163 xcodebuild[30341:2118659] Writing error result bundle to /var/folders/0n/s18rzzz559b9pptn33bs0yz00000gq/T/ResultBundle_2024-10-06_17-04-0045.xcresult xcodebuild: error: The file “BuildProductsPath” couldn’t be opened because there is no such file.: The operation couldn’t be completed. No such file or directory $ The project is called dlsym_test and is an iOS Framework project, language Objective C, containing a single C++ source file named file.cpp. Builds and archives fine, when done via GUI, I get this error, when doing the operation on the command line. :-( The same project builds and archives fine, when I transfer it to an older Mac running Xcode 14.2. Any help would be appreciated. Thanks in Advance, Mario
1
0
335
Jun ’24
macOS app crashes on first launch from TestFlight
2024_06_09_testflight_launch_crash_log.txt Running my macOS app the first time after installing via TestFlight crashes on launch. Every subsequent run works fine (including completely quitting the app and re-running it). Also, building and running directly in XCode both in Debug and Release mode works fine. I'm on a Mac M2 and the app excludes x86_64 arch. Here is the trimmed crash log (sanitised full log is attached) Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: CamHero-macOS-v2-Release [12876] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18c81d11c __pthread_kill + 8 1 libsystem_pthread.dylib 0x18c854cc0 pthread_kill + 288 2 libsystem_c.dylib 0x18c764a40 abort + 180 3 libglib-2.0.0.dylib 0x1061e5bd0 g_assertion_message + 464 4 libglib-2.0.0.dylib 0x1061e5c44 g_assertion_message_expr + 116 5 libgstlibav.dylib 0x10549ede0 gst_ffmpeg_cfg_init + 776 6 libgstlibav.dylib 0x10548a4f4 plugin_init + 140 7 libgstreamer-1.0.0.dylib 0x10646a458 gst_plugin_register_func + 636 8 libgstreamer-1.0.0.dylib 0x106469fe4 gst_plugin_register_static + 212 9 libgstlibav.dylib 0x10548a45c gst_plugin_libav_register + 92 10 CamHero-macOS-v2-Release 0x104a01624 gst_ios_init + 900 (gst_ios_init.m:1072) 11 CamHero-macOS-v2-Release 0x104a80590 specialized CamHeroMacOSApp.init() + 68 (CamHeroMacOSApp.swift:19) 12 CamHero-macOS-v2-Release 0x104a804a4 CamHeroMacOSApp.init() + 4 [inlined] 13 CamHero-macOS-v2-Release 0x104a804a4 protocol witness for App.init() in conformance CamHeroMacOSApp + 20 (<compiler-generated>:16) 14 SwiftUI 0x1b7f134e0 0x1b7163000 + 14353632 15 CamHero-macOS-v2-Release 0x104a804d8 static CamHeroMacOSApp.$main() + 24 [inlined] 16 CamHero-macOS-v2-Release 0x104a804d8 main + 36 17 dyld 0x18c4d90e0 start + 2360 Thread 1: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 2: 0 libsystem_pthread.dylib 0x18c84fe28 start_wqthread + 0 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000600000755680 x5: 0x0000000000000020 x6: 0x0000600000755680 x7: 0xffffffff00008600 x8: 0x8ddd1ea266cd729b x9: 0x8ddd1ea3846d2c5b x10: 0x0000000000001620 x11: 0x00000000dbe367fb x12: 0x00000000000007fb x13: 0x00000000000007fd x14: 0x00000000dc03683c x15: 0x000000000000003c x16: 0x0000000000000148 x17: 0x00000001eb9f3da0 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x00000001e2a05ec0 x21: 0x0000000000000103 x22: 0x00000001e2a05fa0 x23: 0x000000016b407508 x24: 0x0000000000000000 x25: 0x00000001064f8450 x26: 0x000060000080d511 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x000000016b407460 lr: 0x000000018c854cc0 sp: 0x000000016b407440 pc: 0x000000018c81d11c cpsr: 0x40001000 far: 0x0000000000000000 esr: 0x56000080 Address size fault It seems that the initialisation of one of the gstreamer plug-ins doesn't go well. But, I wonder what might lead to that happening only the first time after launch? Will appreciate any clues! EDIT / UPDATE: If i remove the app completely and install the same version again from TestFlight, app doesn't crash. So it seems the crashing is limited to the very first launch of a new /updated version.
3
0
402
Jun ’24
Managing app version releases for single Target with different platforms
I have a multiplatform app with a single target. I’ve been focused on making release updates for just visionOS where the new version doesn’t really have any changes to the iOS/iPadOS content. When I build and archive a new version and build number for my single app target, is it an ok practice to only release the new version and build to visionOS and not iOS? The reason I ask, is that the next time I get around to releasing a version and build that has any iOS changes that I want to release on the iOS App Store, it will have skipped one or more version numbers (due to only visionOS releases) from the last time that version was seen on the iOS App Store because I was only doing visionOS releases and versions prior to that.
1
0
301
Jun ’24
get the error even though enabled Hardened Runtime
Hello there. I'm having trouble with notarization in Xcode. I'm developing a Swift Mac app with Xcode 14, but even when I enable Hardened Runtime and perform notarization, it displays the message "Hardened Runtime is not enabled" and I can't proceed. The steps for notarization are [Window] -> [Organizer] -> [Distribute App] -> [Developer ID] [Next] -> [Upload]. Could you please tell me what I should check, or any other information? I've attached screenshots. Thank you.
1
0
364
Jun ’24
Archive is failing from Xcode command line tools
I've recently upgraded to MAC OS 14.5 and Xcode 15.3. My iOS project which was running properly on earlier Xcode versions started failing when I run archive command from command line tools. Still able to archive properly from Xcode directly. The error is /Users/buildbot/buildslave/ws/scp-macos-builder/build/Release/analysis/Source/narwhal-utils/ProgUtils.cpp(519): exception 60003 Executable failed Please let me know if anyone of you have faced the similar issue.
1
0
232
Jun ’24
Is there a simple way to adding files to iPhone simulator, for use with Xcode?
Correct me if I'm wrong, but with the latest version of Xcode (15.x) you can no longer add files to the iPhone simulator by dragging them into the the Files app. I also tried to share the files from my Mac desktop to the simulator. But after selecting the simulator, absolutely nothing happened. So I had to do it the long way: Add a folder to the simulator with a unique name, in the Files app Get the document path, print(URL.documentsDirectory.path()) Back track into the folder structure till I find that folder cp the files to that folder Please tell me that there is a way that I haven't found on Google, or that I somehow was doing what the Apple dox suggested, but missed a step.
3
0
513
Jun ’24
Archiving my macOS target app fails with BOOL error
I'm building a macOS target for my App (which also has some Obj-C code). Building and running the app is fine but when I archive the app in XCode, the process / build fails with the following error Type 'BOOL' (aka ;Int32') cannot be used as a boolean;test for '!=0' instead It happens in a couple of places, one of the places being private func getRootDirectory(createIfNotExists: Bool = true) throws -> URL { return try FileManager.default.url(for: .documentDirectory, in: .userDomainMask, appropriateFor: nil, create: true) } where it complains that create: true is not acceptable and throws the above error. If I comment out this line, the archive works successfully. When i Cmd + click the definition of Filemanager.default.url , i get this @available(macOS 10.6, *) open func url(for directory: FileManager.SearchPathDirectory, in domain: FileManager.SearchPathDomainMask, appropriateFor url: URL?, create shouldCreate: BOOL) throws -> URL This looks fishy since it it says create shouldCreate: BOOL whereas the documentation says it should be just Bool func url( for directory: FileManager.SearchPathDirectory, in domain: FileManager.SearchPathDomainMask, appropriateFor url: URL?, create shouldCreate: Bool ) throws -> URL My minimum deployment target is macOS 13.0 I'm quite stumped at this error - which happens only while archiving. Does anybody know why?
4
0
406
Jun ’24
CoreDevice framework is unable to route iOS app's stdout
I am trying to automate the installation, launch, and monitoring of iOS apps. Historically we have used ios-deploy, but as of XCode 15 and iOS 17+, using ios-deploy no longer works. See issue The CoreDevice framework and xcrun's devicectl command has many of the features I require, but in contrast to ios-deploy, executing xcrun devicectl process launch --device &lt;uuid&gt; &lt;bundle&gt; does not route the launched app's stdout the the devicectl process. From the help menu, it looks like adding the --console flag will do exactly what I want, which routes the app stdout to the devicectl process and waits for the app to exit. However, if I try running xcrun devicectl process launch --console --device &lt;uuid&gt; &lt;bundle&gt; I receive the following error ERROR: The specified operation is not implemented on this device. (com.apple.dt.CoreDeviceError error 1 (0x01)) -------------------------------------------------------------------------------- ERROR: The operation couldn't be completed. (CoreDevice.ActionError error 2.) NSDebugDescription = This operation cannot be performed on this device. It's rather unclear on what the actual issue is, and I can't find any CoreDevice documentation online to help me deduce what these error codes refer to. Any help would be appreciated!
1
1
410
Jun ’24
Problems with c++ library on iOS arm64e device
Compiler: XCode12/13/14 Tested On: iPhoneXS+iOS15.4 / iPhone11+iOS16.5 I tried to compile following code with arch=arm64e and run, it crashed with EXC_BAD_ACCESS at 'LDRAA', seems occur when trying to access c++ v-table. And this bug will not occur in following conditions. c++ I/O api is easy to trigger the bug. compile with arch=arm64 and run on arm64e device compile with arch=arm64e and run on arm64e device with iOS<=14 #include <fstream> #include <stringstream> int main(int argc, char** argv) { std::ifstream MyReadFile("/System/Library/CoreServices/SystemVersion.plist"); // crash1 std::stringstream stream; stream << std::hex << 0; // crash2 } I also tried c++11/14/17/20, it makes no difference.
1
0
343
Jun ’24
Command CodeSign failed with a nonzero exit code
I am having a peculiar issue with an app I am developing. I am trying to upload it onto App Store Connect but I am getting one error, and a very odd behavior. The error message I am getting is: /Users/user/Documents/GitHub/MyApp/MyApp/DerivedData/MyApp.pub/Build/Intermediates.noindex/ArchiveIntermediates/MyApp.pub/InstallationBuildProductsLocation/Applications/MyApp.pub.app: resource fork, Finder information, or similar detritus not allowed Command CodeSign failed with a nonzero exit code I have cleaned built the directory, I have removed the Derived Data, but this always gets thrown. It was working fine a few months ago, I have only just got back to working on it. The other issue I am havving, when I set to archive the app, I set the target as Any iOS Arm Device (arm64), but when it is archiving it switches to my iPhone as the target. I don't prompt it to do this, it just does it. This is very frustrating. I'm using a MacBook Air M1, with a macOS Sonoma. I updated my Xcode the other day, that's Version 15.4 (15F31d). My App has a minimum target of iOS 15 and a project target of Xcode 13. Any help is appreciated.
4
0
464
1w
Xcode Targeting Non-Apple Platform like Arduino or Bare Metal Embedded System
Looking for anyone that has some experience in getting Xcode to work with external compiler/linkers in what is tantamount to a foreign tool chain to build non-apple platform executables. For example, I want to ultimately use Xcode to edit, build, and push bare metal firmware (read "no operating system at external device"). Think of it as in how to use Xcode to develop the firmware in the processor in the ThunderBolt 4 cable (TPS65994AD) which runs a variant of the ARM Cortex-M machine code. Suppose I don't want to use TI's "Code Composer Studio (CCS)" but instead want to use Xcode which might drive some part of Code Composer Studio. Xcode supports external / foreign tool chains (or did) but the question is "have you done it successfully for any foreign platform?" and if so what was your approach? I'm trying to not waste a bunch of time with horrendous make file scripting only to find out that I did not have to do it or it headed down the wrong directions. I have a hard time believing that someone hasn't done this before for something even more monolithic like Arduino.
1
0
280
Jun ’24
Unable to see sticker pack in simulator
Hello, I am trying to update my 3 sticker packs. I updated them a few years ago with no problem. I have uploaded my new stickers and when I try to test with simulator, they are not showing up. I tried making a new pack with only 3 small stickers (total of 44kb for all 3) using the template and I got the same errors, nothing shows up in simulator. This is what I get: mkdir: path=/var/mobile/tmp/com.apple.messages/ mode= -rwx------: [2: No such file or directory] mkdir: path=/var/mobile/tmp/com.apple.messages/ mode= -rwx------: [2: No such file or directory] setAllowableTypes_block_invoke:1242: *** CGImageSourceSetAllowableTypes - ignoring unknown: 'public.avci' Received Connection Invalid mkdir: path=/var/mobile/tmp/com.apple.messages/ mode= -rwx------: [2: No such file or directory] Synchronous remote object got an error attempting to post setup, reason: Couldn’t communicate with a helper application. [com.apple.MobileSMS:2F148998-0636-4F50-B2E6-834AD4394B69] Error when getting current app configuration for action identifier ConversationListFocusFilterAction, error='Error Domain=DNDErrorDomain Code=1007 "No current action is available. Supply the caller with the default." UserInfo={NSLocalizedDescription=No current action is available. Supply the caller with the default.}' Calling -viewWillAppear: directly on a view controller is not supported, and may result in out-of-order callbacks and other inconsistent behavior. Use the -beginAppearanceTransition:animated: and -endAppearanceTransition APIs on UIViewController to manually drive appearance callbacks instead. Make a symbolic breakpoint at UIViewControllerAlertForAppearanceCallbackMisuse to catch this in the debugger. View controller: <CKSearchViewController: 0x103857600> Invalid absolute dimension, must be > 0.0. NOTE: This will be a hard-assert soon, please update your call site. Invalid absolute dimension, must be > 0.0. NOTE: This will be a hard-assert soon, please update your call site. Invalid absolute dimension, must be > 0.0. NOTE: This will be a hard-assert soon, please update your call site. Invalid absolute dimension, must be > 0.0. NOTE: This will be a hard-assert soon, please update your call site. Synchronous remote object got an error attempting to post setup, reason: Couldn’t communicate with a helper application. UIColor created with component values far outside the expected range. Set a breakpoint on UIColorBreakForOutOfRangeColorComponents to debug. This message will only be logged once. Error registering for delegate callbacks. Error: Error Domain=SKStatusSubscriptionErrorDomain Code=-4000 "System iCloud account does not exist or is not statuskit capable" UserInfo={NSDebugDescription=System iCloud account does not exist or is not statuskit capable} Error retrieving subscription for handle. Error: Error Domain=SKStatusSubscriptionErrorDomain Code=-4000 "System iCloud account does not exist or is not statuskit capable" UserInfo={NSDebugDescription=System iCloud account does not exist or is not statuskit capable} handle: <SKHandle: 0x600000011490; handleString = "+18885551212"> Error fetching subscription service for handle: "+18885551212" Error: Error Domain=SKStatusSubscriptionErrorDomain Code=-4000 "System iCloud account does not exist or is not statuskit capable" UserInfo={NSDebugDescription=System iCloud account does not exist or is not statuskit capable} failed to create XPC connection Unknown invokeXPCSynchronousCallWithBlock error: Error Domain=TransparencyErrorXPC Code=-108 "failed to create XPC connection" UserInfo={NSLocalizedDescription=failed to create XPC connection} XPC error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.coreduetd.knowledge was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.coreduetd.knowledge was invalidated: failed at lookup with error 3 - No such process.} Duet query failed: Couldn’t communicate with a helper application. Checked bag access permission -- allowed? YES {hasMachAccess: YES, hasEntitlements: YES} API MISUSE: Resuming an NSURLSessionTask with nil URL. Task .<1> finished with error [-1002] Error Domain=NSURLErrorDomain Code=-1002 "unsupported URL" UserInfo={NSUnderlyingError=0x600000c62610 {Error Domain=kCFErrorDomainCFNetwork Code=-1002 "(null)"}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask .<1>" ), NSLocalizedDescription=unsupported URL} unhandled process MobileSMS Thank you for any help.
4
2
371
Jun ’24
How do I exclude linking a library for simulator builds
I have a third party library added to my project as ThirdParty.framework, but it only supports real device. I want to make my project still build for simulators but exclude this library and any references of importing it. I tried a few things, for example in the target's build phase "Link Binary With Libraries" set this framework as "Optional", and in the code I have: #if !targetEnvironment(simulator) import ThirdParty class SomeClass: ProtocolFromThirdParty { // ... } #endif Also some view that has reference to this class: import SwiftUI #if targetEnvironment(simulator) struct TestViewSimulator: View { var body: some View { Text("See this view on real device") } } #else struct TestView: View { @StateObject var example = SomeClass() var body: some View { // ... } } #endif But still when I build for simulator, it still gives error for the linking issue: Building for 'iOS-simulator', but linking in object file (/<Path>/ThirdParty.framework/ThirdPartySDK[arm64][2](someobject.o)) built for 'iOS' Building to a real device works as expected. Any suggestions I could make it build on simulators? (I'd like to isolate this screen only for real device and not impacting other parts of the app)
2
0
363
Jun ’24
How can I enable HTTP exceptions in Xcode 15?
Before Xcode 15, when I could access the info.plist file, I was able to add exceptions to the App Transport Security Settings so I could connect with my home server, which has no HTTPS, just HTTP. But in Xcode 15 I have no idea, not can I buy a clue with google, on how to do this. Please help! Thanks p.s. I should probably add that one site mentioned going to the Target section of your project allows easy access to info.plist. Yet for some strange reason, there is no item in Targets, which is odd, as I can debug my. project.
0
0
319
Jun ’24
Problem with setNeedsDisplay:
Hi, with the default values the rotation take place but changing the value not. I bind a button to a slider action: -(IBAction)rotateXAction:(id)sender { NSLog(@"%@ \n",sender); BOOL yn = YES; _rotationX = [_sliderX intValue]; if(yn) printf("rotationX %d \n",_rotationX); // value o.k [self setNeedsDisplay:YES]; } The drawRect: will not be called. What is wrong with my code, please tell me. Uwe
1
0
435
Jun ’24