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

Xcode Documentation

Post

Replies

Boosts

Views

Activity

Xcode will not build function
I am self-learning basic C programming and have installed Xcode v. 14.2 on MacOS Monterey v. 12.7.5. I cannot get any programs I write under a new project I created to build and run on Xcode. Here is an example of what I am trying to build and run: #include <stdio.h> int main() { char test_string[] = "new string text"; printf("This process will %s\n",test_string); return(0); } Any guidance or feedback would be appreciated.
2
0
113
2w
Xcode not generating code coverage.
No coverage is generated for private xxxx.framework, but tests are running under this framework. This was perfectly working before and started giving this error after updating to Xcode 16. Failed to generate coverage for target xxxx.framework at paths ( "/Users/xxxxxx/Desktop/xcode/Debug-iphonesimulator/Common/xxxxxx.framework/xxxx" ): No object file for requested architecture The operation couldn’t be completed. (XCTHCoverageReportGenerationErrorDomain error 2.). (Underlying Error: No object file for requested architecture)
1
0
251
Oct ’24
Debugging a macOS IPS dump
I have a macOS application built via command line (xcodebuild) using Xcode 16.1. Developed on ARM but end user is on Intel (same macOS 15.1). App crashed and they sent me a .IPS dump. From what MacGPT tells me: Reading an IPS (Incident Processing System) file from a macOS crash report in Xcode isn’t as straightforward as with iOS device logs. I can open the dump using Console. I see the IPS dump is partially symbolicated. Line in the dump says: Meteorologist 0x103e0348f 0x103d88000 + 504975 Referencing this article: Adding identifiable symbol names to a crash report | Apple Developer Documentation I run this command and see the same UUID for x86_64 as in the dump. dwarfdump --uuid /Users/ed/meteorologist/trunk/Build/Meteorologist.xcarchive/dSYMs/Meteorologist.app.dSYM/Contents/Resources/DWARF/Meteorologist I run this command: atos -arch x86_64 -o /Users/ed/meteorologist/trunk/Build/Meteorologist.xcarchive/dSYMs/Meteorologist.app.dSYM/Contents/Resources/DWARF/Meteorologist -l 0x103d88000 0x103e0348f And it says: fg: no current job Suggestions for what I’m missing?
1
0
130
2w
xcrun xcresulttool Failed to create a new result bundle reader
I need to read results of a test in Xcode post-action of Test. So the script that runs after tests contains SUMMARY=$(xcrun xcresulttool get test-results summary --path $RESULT_FILE 2>> "$LOGS") If I run my script from terminal, everything is ok but if I launch tests and the post-action is executed, I got Warning: unknown environment variable SWIFT_DEBUG_INFORMATION_FORMAT Warning: unknown environment variable SWIFT_DEBUG_INFORMATION_VERSION Warning: unknown environment variable SWIFT_DEBUG_INFORMATION_FORMAT Warning: unknown environment variable SWIFT_DEBUG_INFORMATION_VERSION Error: Failed to create a new result bundle reader, underlying error: failed to read metadata with underlying error (type: FileSystemError: 3 - [:] - The operation couldn’t be completed. (MinimalTSCBasic.FileSystemError error 3.) Usage: xcresulttool <subcommand> See 'xcresulttool --help' for more information. It might be that the environment set by Xcode is missing something but I cannot figure out what, any idea?
2
1
214
Oct ’24
Top Shelf and App Icon not appearing on tvOS 18.
I am a developer working on tvOS apps for Enterprise. I would like to report an issue occurring in tvOS 18.1. Workflow : Exporting tvOS build from Xcode (Enterprise). We have developed another Mac App to white label the tvOS App. We are changing its Assets and bundle identifier of the app while white labeling process. Resigning app again. Distributing through JAMF. Problem: We have been facing a problem for a while. The top shelf is not working in our white -labeled app and app icon is not appearing. BTW App is opening and doing well. I'm just getting following lines in console (Apple TV Device Console). MDMProvisoningProfileTrust could not find record of managed app 'com.company.connecttv.events' with error: Error Domain=NSOSStatusErrorDomain Code=-10814 "(null)" UserInfo={_LSLine=1734, _LSFunction=runEvaluator} Unable to create LSApplicationRecord for application: com.company.connecttv.events. error=Error Domain=NSOSStatusErrorDomain Code=-10814 UserInfo={_LSLine=1734, _LSFunction=<private>} Top shelf content doesn't conform to TVTopShelfContentPrivate. It will not be ignored [xpcservice<com.company.connecttv.events.Top-Shelf([app<com.apple.HeadBoard(E4023AC5-8955-4943-8AAF-9C8246A9F003)>:156])>{vt hash: 0}:328] Memorystatus failed with unexpected error: Invalid argument (22) <0x302e2eee0-com.company.connecttv.events>: Error returned on remoteObjectProxy for loadTopShelfContentAndDelegateFlags message. error=Error Domain=NSCocoaErrorDomain Code=4097 UserInfo={NSDebugDescription=<private>} Process state is unknown AppStateTracker, pid 328, uuid 809A68F1-76D2-396E-9CE0-5C16058FE354 display identifier com.company.connecttv.events.Top-Shelf foreground 0 Systen Information: Machine : MacBook Pro / M1 Pro / 16 GB / 16-inch / 2021 Mac OS : Version 15.0 (15.0) Xcode : Version 16.1 (16B40) Apple TV Information: tvOS : 18.1 (22J580) Model : Apple TV 4K (3rd generation) Capacity : 128 GB
1
0
134
2w
Can't compile asset catalog when including iMessage App Icon asset
I'm trying to add an iMessage extension to my app, and upon adding the iMessage App Icon set, I ran into an issue with one specific icon size: 1024x768px, aka 1x 1024x768pt. When I remove this one icon from the icon set, it compiles and runs fine, however I can't push it to the App Store as I get the error: "Asset validation failed. Missing Image Asset. Your app is missing the Large App Icon asset 'AppIcon' in 'Payload/Runner.app/PlugIns/MessagesExtension.appex'." I'm assuming this refers to 1024x768px, as this size placeholder appears upon adding a New Messages Extension Icon to my assets folder, and 1024x1024 is already included and compiles fine with it. However, when I add the 1024x768 icon, and try to run the app, I get the error: "Command CompileAssetCatalog failed with a nonzero exit code" The app icon's filename is correct, it is exactly 1024x768 px, and my contents.json correctly includes : { "filename" : "AppIcon_1024x768.png", "idiom" : "ios-marketing", "platform" : "ios", "scale" : "1x", "size" : "1024x768" } as is the same format for all of my other icons that work. Why am I running into this issue upon inclusion of this one required size? How do I fix it?
1
0
168
2w
Augmented Reality app unable to load the image from the camera
I have an app on the App Store for many years enabling users to post text into clouds in augmented reality. Yet last week abruptly upon installing the app on the iPhone the screen started going totally dark and a list of little comprehensible logs came up of the kind: ARSCNCompositor <0x300ad0e00>: ARSCNCompositor (0, 0) initialization failed. Matting is not set up properly. many times, then RWorldTrackingTechnique <0x106235180>: Unable to update pose [PredictorFailure] for timestamp 870.392108 ARWorldTrackingTechnique <0x106235180>: Unable to predict pose [1] for timestamp 870.392108 again several times and then: ARWorldTrackingTechnique <0x106235180>: SLAM error callback: Error Domain=Slam Error Code=7 "Non fatal error occurred due to significant drop in a IMU data" UserInfo={NSDescription=Non fatal error occurred due to significant drop in a IMU data, NSLocalizedFailureReason=SlamEngineNodeGroup Failure: IMU issue: gyro data stream verification failed [Significant data drop]. Failed on timestamp: 870.413247, Last known timestamp: 865.350198, Delta: 5.063049, System timestamp: 870.415781, Delta between system and frame: 0.002534. } and then again the pose issues several times. I hoped the new beta version would have solved the issue, but it was not the case. Unfortunately I do not know if that depends on the beta version or some other issue, given the app may be not installed on the Mac simulator.
11
1
863
Jul ’24
Xcode 16.2 Beta fails to build visionOS app RealityContent assets
I've just updated to macOS 15.2 Beta and Xcode 16.2 Beta and just noticed I can't build my visionOS app as before. I have a separate /Volumes/Development APFS volume for Xcode projects, plus utilising a Relative setting for DerivedData so that these are located in the projects' directories – in this case, subfolder on this volume mentioned. I just found that when attempting to build the app in either Xcode 16.1 or 16.2 Beta with visionOS 2.1 SDK, I'm getting a following error: Finished processSwiftFiles() with a failure 'You don’t have permission to save the file “CustomComponentUSDInitializers.usda” in the folder “RealityAssetsGenerated”.' Sandbox: realitytool(6216) deny(1) file-write-create /Volumes/Development/travel-visionos/DerivedData/Tripomatic/Build/Intermediates.noindex/RealityKitContent.build/Debug-xrsimulator/RealityKitContent_RealityKitContent.build/DerivedSources/RealityAssetsGenerated/CustomComponentUSDInitializers.usda.sb-02874eb3-PS4qfZ Failure creating schema - 'You don’t have permission to save the file “CustomComponentUSDInitializers.usda” in the folder “RealityAssetsGenerated”.' This for sure worked previously with 15.0/16.0 or 15.1/16.1 as I've even published the app to the App Store. It seems to be some shenanigans related to sandboxing &amp; permissions for Xcode tools which I can hardly work around. I have Xcode added to Developer Tools and Full disk access sections in Privacy &amp; Security, yet that doesn't really change anything in relation to this issue. When I move the project to a subfolder in my home directory, the build succeeds. The same applies to switching DerivedData setting to the default value to that DD are generated in ~/Library/Developer folder for all projects opened in Xcode. Thus, either macOS or Xcode now has an issue with running realitytool to generate files on my dedicated volume. Should I consider this Xcode or macOS Beta issue? Report it via Feedback Assistant maybe?
0
0
166
3w
Xcode 16.1 can't load the Account information in VM
I have a MacMini M2 machine running Sequoia 15.1 OS. On this machine, I am running a Virtual Machine, utilizing the Virtualization.Framework, with the same OS version, 15.1. Logging into my account in the System Settings is successful. Next, I need to add my account in Xcode 16.1. While the initial login is successful, Xcode immediately displays the following error: Decoding Error. There was a failure decoding response: (HTTP 401, 60 bytes) The data couldn’t be read because it isn’t in the correct format. As a result, I cannot see any account information, teams, etc. A very similar bug has been reported at this issue - https://developer.apple.com/forums/thread/759877, but there has been no progress or updates there. Is there any chance to fix this and get it working?
6
6
406
3w
Xcode 16 beta 3 can't load Teams in VM
I'm currently setting up a new build environment. Our old build server was a small M1 Mac Mini set up to build our, up-to-now, only app. Since we now have a second app (and probably more to come) and have some issues building all on the same mac (gem versions, flutter versions, etc.) I now set up a virtualized build environment. I'm currently running a MacOS 15 beta 3 VM on a M2 Mac Mini also on MacOS 15 beta 3. The VM has all basic tools inside, including Xcode 16 beta 3 and is logged in with our AppleID for our build server. The VM is spun up with a non-persistent storage before the build, installs the gem's/flutter in the correct version, checks out the code and builds it. Now I'm getting an error on the build, that I have to select a development team, but he team is already selected and the build is working fine on the old M1 Mac Mini. It is suggested to login to Xcode, so I logged in to Xcode in the VM, which itself was successful, but when loading the teams I'm getting the following error: Decoding Error There was a failure decoding response: (HTTP 401, 60 bytes) The data couldn't be read because it isn't in the correct format.. The account info is correct, it's the same account that is logged in to MacOS and it's the same account from the old build system. I guess this somehow has to do with the MacOS VM (before MacOS 15 it was not possible to signin to an apple id, this is also the reason why I use the beta). Is there any chance to fix this and get it working? We are not able to use Xcode cloud builds (or any other cloud services) due to corporate policies. We are also not able to buy a dedicated Mac Mini for every app (too expensive and too much time needed for maintenance).
5
2
1.4k
Jul ’24
Xcode 16.1 (23503) keeps crashing on launch DVTPlugInManager
After upgrading to Xcode 16.1 the IDE does crash on launching, using Xcode 16.1 is not possible. When 1st launching Xcode 16.1 it asks to activate the plug-ins, after agreeing it crashes. All subsequent launches do crash with this report. This is the same issue when Xcode 15 was release, subsequent releases fixed this. See here https://forums.developer.apple.com/forums/thread/738097 Translated Report (Full Report Below) Process: Xcode [14193] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 16.1 (23503) Build Info: IDEApplication-23503000000000000~2 (16B40) App Item ID: 497799835 App External ID: 869932297 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-11-02 17:46:02.4767 +0100 OS Version: macOS 15.1 (24B83) Report Version: 12 Anonymous UUID: 794C407F-4930-BAA9-C41E-64C157CC3277 Sleep/Wake UUID: 0CF56A77-6F81-448D-9093-9461EE187F08 Time Awake Since Boot: 51000 seconds Time Since Wake: 7243 seconds System Integrity Protection: enabled 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: Xcode [14193] Application Specific Information: abort() called Application Specific Signatures: 0 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x194f76600 __pthread_kill + 8 1 libsystem_pthread.dylib 0x194faef70 pthread_kill + 288 2 libsystem_c.dylib 0x194ebb908 abort + 128 3 IDEKit 0x10610cdb8 +[IDEAssertionHandler _handleAssertionWithLogString:assertionSignature:assertionReason:extraBacktrace:] + 964 4 IDEKit 0x10610d248 -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] + 876 5 DVTFoundation 0x1022cc040 _DVTAssertionHandler + 424 6 DVTFoundation 0x1022cc1c0 _DVTAssertionFailureHandler + 196 7 DVTFoundation 0x10241b454 -[DVTPlugInManager _registerPlugInsFromScanRecords:] + 2412 8 DVTFoundation 0x1024192fc -[DVTPlugInManager _createPlugInObjectsFromScanRecords:] + 228 9 DVTFoundation 0x102417664 __52-[DVTPlugInManager _recordNonApplePlugInDescriptor:]_block_invoke + 92 10 DVTFoundation 0x102417c2c -[DVTPlugInManager _allowNonApplePlugInsFromDescriptors:error:] + 304 11 DVTFoundation 0x102417e14 -[DVTPlugInManager _checkNonApplePlugIns] + 204 12 DVTFoundation 0x102417ef0 -[DVTPlugInManager initializePlugIns:] + 20 13 IDEFoundation 0x10a7a8cac IDEInitialize + 6632 14 IDEKit 0x1060e45dc -[IDEApplicationController applicationWillFinishLaunching:] + 364 15 CoreFoundation 0x19508a800 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 148 16 CoreFoundation 0x19511b66c ___CFXRegistrationPost_block_invoke + 88 17 CoreFoundation 0x19511b5b4 _CFXRegistrationPost + 436 18 CoreFoundation 0x19505943c _CFXNotificationPost + 732 19 Foundation 0x196201b14 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 20 AppKit 0x198bb2d30 -[NSApplication finishLaunching] + 248 21 AppKit 0x198bb29fc -[NSApplication run] + 252 22 IDEKit 0x1060dc798 -[IDEApplication run] + 60 23 AppKit 0x198b89364 NSApplicationMain + 888 24 dyld 0x194c2c274 start + 2840 Thread 1:: Dispatch queue: ConcurrentQueue: -[DVTPlugInManager _savePlugInCacheWithScanRecords:error:]block_invoke 0 libsystem_kernel.dylib 0x194f71d6c __unlink + 8 1 libsystem_kernel.dylib 0x194f71d48 unlink + 16 2 libremovefile.dylib 0x1a2a5b75c __removefile_tree_walker + 392 3 libremovefile.dylib 0x1a2a5b548 removefile + 340 4 Foundation 0x1964995f8 specialized static FileOperations.removeFile(::with:) + 224 5 Foundation 0x196762570 specialized String.withFileSystemRepresentation(:) + 308 6 Foundation 0x19635f0f8 @objc _NSFileManagerBridge.removeItem(atPath:) + 136 7 DVTFoundation 0x10241c5b4 DVTPlugInManager_removePlugInCacheAtPath + 40 8 DVTFoundation 0x10241cb68 __58-[DVTPlugInManager _savePlugInCacheWithScanRecords:error:]_block_invoke_2 + 224 9 DVTFoundation 0x1023de414 DVT_CALLING_CLIENT_BLOCK + 16 10 DVTFoundation 0x1023dee3c __DVTDispatchAsync_block_invoke + 152 11 libdispatch.dylib 0x194dfa8f8 _dispatch_call_block_and_release + 32 12 libdispatch.dylib 0x194dfc658 _dispatch_client_callout + 20 13 libdispatch.dylib 0x194dffb08 _dispatch_continuation_pop + 596 14 libdispatch.dylib 0x194dff138 _dispatch_async_redirect_invoke + 580 15 libdispatch.dylib 0x194e0e314 _dispatch_root_queue_drain + 392 16 libdispatch.dylib 0x194e0eb20 _dispatch_worker_thread2 + 156 17 libsystem_pthread.dylib 0x194fab39c _pthread_wqthread + 228 18 libsystem_pthread.dylib 0x194faa0f0 start_wqthread + 8 Thread 2: 0 libsystem_pthread.dylib 0x194faa0e8 start_wqthread + 0 Thread 3: 0 libsystem_pthread.dylib 0x194faa0e8 start_wqthread + 0
0
0
198
3w
"Fonts needed by this application are missing." alert upon opening SF Symbols.
When I was on the 15.1 developer beta, I downloaded the beta version of the SF Symbols app. It worked perfectly throughout the beta, but when 15.1 was released, I downloaded the stable version of SF Symbols as well and removed the beta version. However, now when it launches I am greeted by an alert titled "Fonts need by this application are missing." It goes on to say that fonts may not display properly... etc, but I haven't noticed any issues viewing any symbols I have looked up, and they seem to show up properly when I define them in Xcode. I tried uninstalling and reinstalling the application, as well as following the advice in the alert by downloading "the latest fonts from the Apple Developer website." but the alert still shows up everytime I launch SF Symbols. Any one else experiencing this issue or know of a way to solve it? It's not that big of an issue, it's just one extra click after all, but in case it might be in the future, I just thought I'd check with others. Thanks!
3
2
115
3w