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

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Created

Goland cannot debug under the latest XCode
version: Goland 2025.1.4 Go 1.24 Xcode last release When I debug from a breakpoint, Goland will skip the breakpoint and run all programs directly, just like running directly. There are also people online who have the same problem. Their solution is to downgrade the Xcode version to 16.2, but the Apple official website does not have version 16.2, only version 16.3. So I downloaded version 16.3 but couldn't install it because it showed incompatibility with the MacOS version. I almost completely reinstalled it but it had no effect. I request your assistance, thank you!
1
0
57
Aug ’25
UIKit-***.pcm' does not exist
Setting breakpoints in Xcode and debugging the program will output the following information in the console. The first breakpoint debugging is triggered every time you compile and run the program. Furthermore, loading variables during breakpoint debugging takes a very long time. Why is this information outputted? And why does it take so long warning: (arm64) /Users/***/Library/Developer/Xcode/DerivedData/MYApp-edwwubwxxruxpddmfzegvkdqhppk/Build/Products/Debug-iphoneos/XCFrameworkIntermediates/FBKVOController/FBKVOController.framework/FBKVOController(FBKVOController.o) '/var/folders/45/h0vrkd951jjbc538flwxctqc0000gn/C/clang/ModuleCache/2OX0YH8X0GZ6V/UIKit-HKJAGZJT5Z2N.pcm' does not existwarning: (arm64) Environment Xcode Version 16.4 (16F6) + any iPhone device
0
0
34
Aug ’25
Playground Macro Raises Error when compiled with Swift 6
In my Xcode app, I was attempting to use the #Playground macro to play around with some of the Foundation Model features to see if they would work for my iOS app. However, every time I used a #Playground macro, even if it was empty, it would receive the following error: /var/folders/q2/x5b9x0y161bb2l_0yj1_j6wm0000gn/T/swift-generated-sources/@__swiftmacro_20PlaygroundMacroIssue0022ContentViewswift_tiAIefMX26_0_33_B691877350F20F2DFC040B9E585F4D10Ll0A0fMf_.swift:51:5 Main actor-isolated let '$s20PlaygroundMacroIssue0022ContentViewswift_tiAIefMX26_0_33_B691877350F20F2DFC040B9E585F4D10Ll0A0fMf_23PlaygroundContentRecordfMu_' can not be referenced from a nonisolated context Here are my Xcode and system versions: Mac is running the first public beta of Tahoe. iOS Simulator is running 26.0 dev beta 4. Xcode is Xcode 26 beta 4. So, I went to try to reproduce the error in a blank iOS app project (the error above is the one that I reproduced in that project). Here are the steps that I took. I created a new iOS project in Xcode 26. I went into the ContentView.swift that was created for me and imported the Playgrounds module and created a blank #Playground at the bottom of the file. I then compiled the project and it ran just fine. To try to find out what the issue was, I looked at the concurrency settings. In my real app, Strict Concurrency Checking was set to Complete but was Minimal in my test project. So I went and changed that setting in my real app and it didn't fix anything. Next, I looked at the Swift Version, which turned out to be the culprit. My test app was running Swift 5 whereas the real app was running Swift 6. It seems to have crashed while running Swift 6, not 5. I have trouble understanding what the error is saying. I have tried using the Code Intelligence feature to fix the bug but it hasn't helped. Has anyone here experienced a similar bug? Is there something I can do to fix it or is this an error in Xcode that should be reported? I have attached an iCloud link to my test project if anybody wants to see if they can reproduce the issue: here Thanks!
2
0
96
Jul ’25
Sandbox restriction Error 159: Tap to Pay integration in iOS app
Hi all, I am hope someone could assist me with the below error if you ever ran into this during Tap-to-Pay functionality integration on iOS/iPadOS devices. Pre-condition: I have received required entitlements for the Tap-to-Pay integration and created Sandbox test account to validate my development work. Used updated development profile with the new capabilities required for the Integration. When i try to test my flow, i keep receiving this error, with multiple sandbox accounts in developer portal. Error (refreshContext): proxy error handler [ Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.merchantd.transaction was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.merchantd.transaction was invalidated: failed at lookup with error 159 - Sandbox restriction.} ] I greatly appreciate if anyone faced this issue or any knowledge on how to address this error. Thanks in advance. Best regards, Govardhan.
0
0
122
Jul ’25
linking error file cannot be open()ed, errno=2
I have been learning from the Apple Developer tutorials and I got stuck on the ScoreKeeper chapter with Testing. Since my Macbook Pro 2017 can only use Xcode 15.2 as the highest level, I am having issues with it. I saw a forum post that a certain level of Swift and the tool chain would fix this. I attempted to install Swift 5.10.1 to then realize I only had Xcode 15.2 not 15.3, so I had to attempt to install Swift 5.9. Since neither option worked, I uninstalled Xcode and removed any extra files along with swift packages, minus my projects, to redownload and reinstall Xcode 15.2. Now I am having issues with building the scheme, and I get link error,s and they pertain to Swift 5.10.1, which I had not installed any Swift packages after the Xcode reinstallation. I have tried another previous project even a new one same error. This was 7/30/25, as of today 7/31 I tried to install Swift 5.9 thinking it would overwrite or "downgrade" the package, no such luck. The file path in the error stops at the /.../...RELEASE.pkg file and does not continue, which seems to be the issue of the error. How to I fix this issue, I had a working product 3 dyas ago
2
0
91
Jul ’25
XCode 26 beta 4 Playground macro issue
Using the #Playground macro in beta 3 worked fine, but the Playgrounds package appears to be missing in beta 4. import Playgrounds #Playground { print("🚀 Playground is active") } Canvas error message: Cannot find playgrounds Check whether the playground is compiled for the current scheme and OS of the selected device. There could be compile time checks filtering playgrounds out. Check for dead code stripping or other settings that could exclude playgrounds from the final binary.
1
0
99
Jul ’25
Xcode organizer not properly showing termination charts
Two month back we published 28.11.0 version a app. for both foreground and background terminations are not properly showing by Xcode matrix Foreground Termination: I was able to see the termination bar chart for one release, but after that, the chart stopped showing real-time crash progress. However, crashes are still being reported directly by users. Why is Xcode Organizer unable to capture these events? Please help us track them effectively. Background Termination: The termination bar chart has not appeared in Xcode Organizer for the last two releases, which span nearly two months. As a result, we are unable to monitor app terminations for background scenarios.
0
0
51
Jul ’25
How to Prevent Xcode from Automatically Generating Unnecessary "inputPaths" and "outputPaths" in project.pbxproj?
I’ve noticed that Xcode keeps automatically adding unnecessary inputPaths and outputPaths entries to my project.pbxproj file. These outputPaths don’t seem to serve any real purpose in my project and clutter the project file, sometimes causing unnecessary merge conflicts in version control. I’ve already checked I didn't change my project.pbxproj file, but Xcode still occasionally generates these outputPaths. I’m not using any custom build tools or plugins that should be modifying this. One thing I’ve observed is that this issue only occurs when Xcode is open. If I close Xcode, the problem does not happen. This makes me think it might be related to how Xcode manages or updates the project file in the background. My questions: Is there a way to completely disable Xcode from generating these outputPaths automatically? Are there any hidden settings, project configurations, or best practices to prevent this behavior? Has anyone else experienced this issue, and how did you resolve it? Any advice or insight would be greatly appreciated. Thank you!
0
1
48
Jul ’25
XCode 26 debug build run time crash on iOS Device with iOS < 26.0


1.App build using xCode 26 beta 4 crashing on run time on iOS device with iOS < 26.0 but works fine on iOS 26 beta devices. 2. Works fine if build using xCode 16.2 Runtime Crash Dump 
dyld[67519]: Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture Symbol not found: _NSUserActivityTypeBrowsingWeb Referenced from: /private/var/containers/Bundle/Application/2D4B24D6-CEA5-4682-B549-9CCB6A56BAB9/Foreground Camera.app/Foreground Camera.debug.dylib Expected in: <050203DD-7488-307D-A999-E587314B041A> /System/Library/Frameworks/CoreServices.framework/CoreServices dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture
2
0
104
Jul ’25
Push notifications on the iPhone simulator
I've been aware for some time that Push notifications work on the iOS simulator now -- I see them pop up while I'm working. However, it would seem that SILENT push notifications do not work. I came to this conclusion only after several frustrating hours of debugging my app, thinking either the app was broken or the server wasn't sending the notification. Finally I tested it on a device and found that it actually works fine. Why does such a limitation exist? If I can't depend on the simulator to handle ALL of the notifications, I'd rather it didn't work at all. Having it work part of the time on some notifications is really confusing.
1
0
106
Jul ’25
Xcode 26 Beta 4 Build Failures
We are trying to track down some build failures that started happening only in our Jenkins CI environment. error: Failed to decode version info for '/Applications/Xcode.app/Contents/Developer/usr/bin/actool': The data couldn’t be read because it is missing. (stdout: '<?xml version="1.0" encoding="UTF-8"?> [2025-07-30T19:21:18.479Z] <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> [2025-07-30T19:21:18.479Z] <plist version="1.0"> [2025-07-30T19:21:18.479Z] <dict> [2025-07-30T19:21:18.479Z] <key>com.apple.ibtool.version</key> [2025-07-30T19:21:18.479Z] <dict> [2025-07-30T19:21:18.479Z] <key>bundle-version</key> [2025-07-30T19:21:18.479Z] <string>24112</string> [2025-07-30T19:21:18.479Z] <key>short-bundle-version</key> [2025-07-30T19:21:18.479Z] <string>26.0</string> [2025-07-30T19:21:18.479Z] </dict> [2025-07-30T19:21:18.479Z] </dict> [2025-07-30T19:21:18.479Z] </plist> [2025-07-30T19:21:18.479Z] ', stderr: '' Key facts we've noted: Locally I cannot reproduce the problem We did not see this problem with previous Xcode 26 betas If I remote into the machine and run build commands from the command line I cannot reproduce the problem The very first build succeeds, every build after that on this machine fails from jenkins actool --version is spitting out the version information for ibtool, but only in the context of running from a jenkins agent. If I run this locally or if I remote into the CI machine and run this from the terminal I cannot reproduce this behavior. Command line tools appear to be installed, xcode-select --install fails if I try to do it from the command line. We've tried to recreate the build agents for this jenkins environment exactly as they were for all previous betas and xcode versions, and still get this behavior.
13
4
467
Jul ’25
Xcode 26 b4 stopped recognizing connected iPhone (MacOS 26)
Hello. I am a complete novice. I have a MacOS26 partition as well as a 15.5 one. I use 26 for dev. Today, after booting into 26, Xcode (both version 26 and 16.4) are failing to recognize the iPhone which i've been using as a test device. I have made no changes to the install, i've simply been using 15.5 for a couple days, and when i booted back into 26, it just wouldn't work. Both Xcode 26 and 16.4 see the device when in MacOS 15.5. I have tried the following: restarting all devices switching wireless network no VPN on either phone or computer reinstalling xCode starting a new project manually adding device (no connected devices found) turning off and on developer mode on phone restarting usbmuxd different cables and ports I don't know what else to try at this point. I'd rather not reinstall macos on the other partition if possible. Thanks very much.
2
0
97
Jul ’25
Xcode can't find prepareCustomLanguageModel
I have Xcode 16 and am setting everything to a minimum target deployment to 17.5, and am using import Speech Never the less, Xcode doesn't can't find it. At ChatGPT's urging I tried going back to Xcode 15.3, but that won't work with Sequoia Am I misunderstanding something? Here's how I am trying to use it: if templateItems.isEmpty { templateItems = dbControl?.getAllItems(templateName: templateName) ?? [] items = templateItems.compactMap { $0.itemName?.components(separatedBy: " ") }.flatMap { $0 } let phrases = extractContextualWords(from: templateItems) Task { do { // 1. Get your items and extract words templateItems = dbControl?.getAllItems(templateName: templateName) ?? [] let phrases = extractContextualWords(from: templateItems) // 2. Build the custom model and export it let modelURL = try await buildCustomLanguageModel(from: phrases) // 3. Prepare the model (STATIC method) try await SFSpeechRecognizer.prepareCustomLanguageModel(at: modelURL) // ✅ Ready to use in recognition request print("✅ Model prepared at: \(modelURL)") // Save modelURL to use in Step 5 (speech recognition) // e.g., self.savedModelURL = modelURL } catch { print("❌ Error preparing model: \(error)") } } }
1
0
93
Jul ’25
Potential Issue with SKStoreReviewController.requestReview API - Significant Drop in App Store Ratings
We are experiencing a significant issue with the SKStoreReviewController.requestReview(in: scene) API that may be affecting our app's rating collection on the App Store. Issue Details: Development Environment Behavior: The rating popup displays consistently in development builds (as expected per documentation) API calls are functioning correctly in our test environment Production Environment Issue: We have observed a major drop in App Store ratings received between January and July 2025 The same codebase that works in development is deployed to production Analytics Confirmation: Before calling SKStoreReviewController.requestReview() in production, we fire analytics tags to track API invocations Our analytics show no drop in the number of times this API is being called This confirms the API is being invoked correctly in production Discrepancy: Despite consistent API calls (confirmed by analytics), we see a major drop in actual ratings received on the App Store This suggests the rating popup may not be displaying to users in production, even though the API call is successful Questions: Are there any known issues with SKStoreReviewController.requestReview() API between January-July 2025? Are there any iOS version-specific issues that might prevent the popup from appearing in live app? What debugging steps do you recommend to identify why the API calls aren't resulting in visible rating prompts?
0
0
67
Jul ’25
Is it possible to apply a fix and compile, release using the older 17.2 and XCode 15 codesets?
Our mobile application was originally designed and built approximately 2015. It has been incrementally iOS upgrade up to SDK version 17.2 compiled using XCode 15. Issue: Due to a recently degraded Customer Journey, we are blocked from making further changes to the application via the App store due to the fixed Apple protocol message (since April 2025): “iOS requirements have changed. • Minimum SDK Requirement: The minimum SDK version for iOS and iPadOS apps submitted to the App Store after the specified date is iOS 18. • Xcode Requirement: Xcode 16 or later is required to build apps with the iOS 18 SDK. • Existing Apps: If your app was last released using an older SDK, you will not be affected by this update until you submit a new release.” Thus, based on an ask to remediate the poor CJ without fully rewriting the app to be iOS 18 / Xcode 16: Is it possible to apply a fix and compile, release using the older 17.2 and XCode 15 codesets? We are currently blocked from doing so. Any steer on how to apply a fix and release on the older code sets would be appreciated. Thank you
1
0
70
Jul ’25
Unable to View Crash Logs in Xcode Organizer
Hi everyone, I’m currently unable to view crash logs in Xcode Organizer for any of the apps in my account. When I try to access crash reports, I receive the following error: "An error occurred preventing Xcode from downloading version information from App Store Connect. An unexpected error occurred: [<__NSDictionaryM> valueForUndefinedKey:]: this class is not key value coding-compliant for the key [App Name] [Version] (iOS App)." The error message references an app name and version that were previously used. Notably, the original app name included an @ symbol (e.g., @ExampleApp). We suspected this might be contributing to the issue, so we updated the app name to remove the symbol. However, the error persists and still references the old name. Has anyone experienced something similar or found a workaround? Any guidance would be greatly appreciated! Thanks in advance.
1
0
117
Jul ’25