Hello all! Trying to find list of all XCode project parameters or build settings within description. Is there any documentation? Need something that will help me to understand list of project properties when running command in project folder: $ xcodebuild -showBuildSettings Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -showBuildSettings User defaults from command line: IDEPackageSupportUseBuiltinSCM = YES Build settings for action build and target test: ACTION = build AD_HOC_CODE_SIGNING_ALLOWED = NO AGGREGATE_TRACKED_DOMAINS = YES ALLOW_BUILD_REQUEST_OVERRIDES = NO ALLOW_TARGET_PLATFORM_SPECIALIZATION = NO ALTERNATE_GROUP = staff ALTERNATE_MODE = u+w,go-w,a+rX ALTERNATE_OWNER = alexandr ALTERNATIVE_DISTRIBUTION_WEB = NO ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = NO ALWAYS_SEARCH_USER_PATHS = NO ALWAYS_USE_SEPARATE_HEADERMAPS = NO and may other parameters Need to know meaning of this kind of parameters.
Search results for
xcode github
91,958 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
According to the ARM documentation for the CPU models available in Apple Silicon, the CoreSight implementation includes an Embedded Trace Macrocell which can perform a complete Instruction Trace (https://developer.arm.com/documentation/102119/0200/What-is-trace-). Although other operating systems such as Linux make this easy, we have not been able to find any tools or even a system-level API for accessing this feature of the ETM. In the Instruments window of Xcode 16+, there is a Processor Trace instrument, but this performs sampling and is totally unrelated to the Instruction Trace we need for debugging and analysis purposes. Because it produces a complete, contiguous sequence of branch instructions, the Instruction Trace is essential for identifying precise execution behaviors that are otherwise invisible to the developer. On other platforms, an alternative is debugger scripting, but we have found far too many bugs and reliability issues with the macOS implementation of lldb. Any suggestions would
Topic:
Developer Tools & Services
SubTopic:
Instruments
I've been playing with the new GameSave API and cannot get it to work. I followed the 3-step instructions from the Developer video. Step 2, Next, login to your Apple developer account and include this entitlement in the provisioning profile for your game. seems to be unnecessary, as Xcode set this for you when you do step 1 First add the iCloud entitlement to your game. Running the app on my device and tapping Load starts the sync, then fails with the error Couldn’t communicate with a helper application. I have no idea how to troubleshoot this. Every other time I've used CloudKit it has Just Worked™. Halp‽ Here is my example app: import Foundation import SwiftUI import GameSave @main struct GameSaveTestApp: App { var body: some Scene { WindowGroup { GameView() } } } struct GameView: View { @State private var loader = GameLoader() var body: some View { List { Button(Load) { loader.load() } Button(Finish sync) { Task { try? await loader.finish() } } } } } @Observable class GameLoader { var directory: G
Topic:
Graphics & Games
SubTopic:
General
GKAccessPoint triggerAccessPointWithState handler not invoked on iOS 26.0 and iOS 15.8.4 Incorrect/Unexpected Behaviour: When calling [GKAccessPoint.shared triggerAccessPointWithState:GKGameCenterViewControllerStateAchievements handler:^{}] on a real device running iOS 26 beta (iOS 26), the overlay appears as expected, but the handler block is never called. This behavior also not working correctly on previous iOS versions(tested on iOS 15.8.4) Steps to Reproduce: Authenticate GKLocalPlayer Call triggerAccessPointWithState:handler: with a block that logs or performs logic Observe that overlay appears, but block is not executed Behavior: UI appears correctly Handler is not invoked at all Expected Result: The handler should fire immediately after the dashboard is shown. Actual Result: The handler is never called. Usecase: As GKGameCenterViewController is deprecated we are moving to GKAccesspoint but due to above functionality issue we are unable to. Environment: Device: iPhone 16, iPhone 7 iOS: 26.0 and iOS 15.8
Environment iOS Version: iOS 26 Beta 8 Xcode Version: iOS 26 Beta 6 StoreKit: StoreKit 2 Description When calling AppStore.showManageSubscriptions(in:) on iOS 26 beta, I'm experiencing an unusual presentation behavior that wasn't present in earlier versions. An empty/blank view appears first Then the actual StoreKit manage subscriptions sheet appears on top When dismissing the StoreKit sheet, it closes properly But then I have to dismiss the empty view underneath as well This creates a poor user experience showing double sheets. Code Sample @MainActor func showManageSubscriptions() { guard let scene = UIApplication.shared.connectedScenes .first(where: { $0 is UIWindowScene }) as? UIWindowScene else { return } Task { do { try await AppStore.showManageSubscriptions(in: scene) } catch { // Handle error } } } Expected Behavior The StoreKit manage subscriptions sheet should present directly without any intermediate empty view, as it did in previous iOS versions. Actual Behavior An empty view layer appears
I am also seeing this issue where successfully uploaded builds do not show in TestFlight / App Store Connect. We are using Xcode 26 Beta 7 and altool with an app specific password.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
I also try to be a good app, and provide asynchronous support. I think that's your problem. It's too difficult to keep up with that. Your asynchronous code is already deprecated and disavowed. First of all, make sure you try using the ClipboardViewer tool. I think it's in Xcode's AdditionalTools as a separate download. I know you're dealing with Drag and Drop, which is not quite the same, but it may be enlightening as most people implement Copy and Paste with the same data. I've never tried dragging from Safari, but I certainly never seen any TIFF conversions. I even support data types that the system doesn't, so there's no way it ever could convert it. Again, I think you're trying too hard. Instead of itemProvider.loadInPlaceFileRepresentation, try just loadItem. That should give you the actual URL. You might run into concurrency problems. I seem to have encountered that myself with these APIs. Unfortunately, there's no easy solution. You definitely don't want to try those old dispatch queues, at le
Topic:
UI Frameworks
SubTopic:
AppKit
Tags:
I've built an app that supports live activities, but when trying to build and deploy I'm getting the error: Provisioning profile iOS Team Provisioning Profile doesn't include the com.apple.developer.live-activity entitlement. Looking in Xcode - under signing and provisions, there is no Live Activity option to select. Looking in the developer portal, similarly under Certificates, Identifiers & Profiles, there is no Live Activity option. I've added com.apple.developer.live-activity to my entitlements file for both my widget and my main app target, and added NSSupportsLiveActivities to my info.plist files. I'm building on Xcode Version 16.0 Any ideas on how to fix this? Super confused! Thanks in advance!
Hi. Yes, the Developer ID identity. Thanks for promoting the use of proper terminology 😁 I've read through a number of your other posts on this forum and found them informative and helpful. And yes, I'm referring to Xcode Cloud. My ci_post_xcodebuild.sh script includes: codesign ... --sign $CODESIGN_IDENTITY diskimage.dmg Where CODESIGN_IDENTITY is the SHA-1 of my Developer ID Application: My Company (MYTEAMID). It unsurprisingly fails with: error: The specified item could not be found in the keychain. I can also see there are no identities in the keychain with: security find-identity -v -p codesigning I'm hoping Xcode Cloud provides me a better way to access the identity than uploading the .p12 to the host... Thanks!
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
I’d like to clarify your issue here. You wrote: [quote='799215021, rvalance, /thread/799215, /profile/rvalance'] The issue is my Developer ID Application certificate is not accessible to the build host. [/quote] I’m presuming you mean “Developer ID Application signing identity” here, because you can’t sign anything with just a certificate. For more about that common terminological mixup, see TN3161 Inside Code Signing: Certificates. However, that’s not my actual question. Rather, I’d like to focus on the “is not accessible to the build host” bit. You put this thread in the Xcode Cloud subtopic, which suggests that by “build host” you mean the Xcode Cloud builder. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Tags:
I ran the same test in the environment below, and the ClientHello packet still does not include early_data in this case either. Xcode 26.0 Beta 7 iPhone SE (2nd generation) running iOS 26.0 (23A55336a)
Topic:
App & System Services
SubTopic:
Networking
Tags:
Development environment Xcode 26.0 Beta 6 iOS 26 Simulator macOS 15.6.1 To verify TLS 1.3 session resumption behavior in URLSession, I configured URLSessionConfiguration as follows and sent an HTTP GET request: let config = URLSessionConfiguration.ephemeral config.tlsMinimumSupportedProtocolVersion = .TLSv13 config.tlsMaximumSupportedProtocolVersion = .TLSv13 config.httpMaximumConnectionsPerHost = 1 config.httpAdditionalHeaders = [Connection: close] config.enablesEarlyData = true let session = URLSession(configuration: config, delegate: nil, delegateQueue: nil) let url = URL(string: https://www.google.com)! var request = URLRequest(url: url) request.assumesHTTP3Capable = true request.httpMethod = GET let task = session.dataTask(with: request) { data, response, error in if let error = error { print(Error during URLSession data task: (error)) return } if let data = data, let responseString = String(data: data, encoding: .utf8) { print(Received data via URLSession: (responseString)) } else { print(No da
Hello! The minimize behavior was working correctly while I was using Xcode 26 beta 4 with iOS 26 beta 4 simulator — when scrolling down, the Tab Bar would minimize as expected. However, after upgrading both Xcode and iOS simulator to beta 5, the tabBarMinimizeBehavior setting no longer has any visible effect — the Tab Bar stays fixed in place. Code snippet: if #available(iOS 26.0, *) { self.tabBarMinimizeBehavior = .onScrollDown } Steps to reproduce: 1. Create a UITabBarController with at least one tab containing a scrollable view (e.g., UITableView). 2. In viewDidLoad, set tabBarMinimizeBehavior to .onScrollDown. 3. Run on iOS 26 beta 5 simulator. Expected behavior (beta 4): Scrolling down hides/minimizes the Tab Bar with animation. Actual behavior (beta 5): Tab Bar remains fixed; no minimize animation is triggered. Environment: • Xcode 26 beta 5 (Build: 17A5295f) • iOS 26 beta 5 simulator (Build: 1055) – iPhone 16 Pro • Also tested on iPhone 13 mini – iOS 26 (Build: 23A5308g)
You do have to add com.apple.security.files.bookmarks.document-scope to your entitlement file yourself, Already done. The object you're using as the bookmark anchor needs to be a file, not a directory, and must be a file you already have full read/write access to. Already done. The object you're targeting needs to be a file as well. That's an important plot point. My current app looks at folders exclusively. So that's all I tested. Document scoped bookmarks are designed to be used to track groups of user files (for example, like an Xcode project), so a small number of directories have been blocked. It sounds like a large number of directories have been blocked - i.e. all of them. Or are these blocked target file prefixes rather than directories? Ah well, such is life. I'm working an an iOS/macOS GUI version of a command-line GIS tool. I had wanted to allow the user to specify a directory to be used as a library. Power users could then use my sandboxed and Metal-powered version of the command line app
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Encountering this stern warning in Xcode simulator and occasional app ending errors which I believe are due to this problem. App ran fine on earlier (pre iOS 17) versions of iOS for over 10 years. Any leads on where this issue is addressed in Apple documentation?
Topic:
UI Frameworks
SubTopic:
UIKit
Tags: