Hi, I'm using XCode 16 to connect my iPhone. Recently I'm getting an error as below while connecting to Xcode to install the app Timeout while connecting to remote device. Domain: com.apple.mobiledevice Code: -402652910 User Info: { DVTErrorCreationDateKey = "2025-04-02 15:03:29 +0000"; FunctionName = "_AMDeviceCreateWithRemoteDeviceWithError"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; LineNumber = 334; } System Information macOS Version 15.3.2 (Build 24D81) Xcode 16.2 (23507) (Build 16C5032a) Is there any way we can connect iOS 18 devices through USB only?

问题描述: 环境: Xcode 版本: 16.3 *macOS 版本: 15.4 项目类型: SwiftUI App with SwiftData 问题摘要: 当在 Xcode 项目的 "Signing & Capabilities" 中为启用了 iCloud 能力的应用关联一个具体的 iCloud Container 时，即使代码中并未显式启用 CloudKit 同步（例如，未在 ModelConfiguration 中设置 cloudKitDatabase），SwiftData 的 ModelContainer 在应用启动初始化时也会立即失败并导致崩溃。如果仅启用 iCloud 能力但不选择任何 Container，应用可以正常启动。此问题在使用空的 Schema([]) 进行测试时依然稳定复现。 复现步骤 (使用最小复现项目 - MRE): 使用 Xcode 16.3 创建一个新的 SwiftUI App 项目 (例如，命名为 CloudKitCrashTest)。 在创建时不要勾选 "Host in CloudKit"，或者，如果勾选了，先确保后续步骤覆盖相关设置。Storage 选择 None 或 SwiftData 均可复现。 修改 CloudKitCrashTestApp.swift 文件，添加 SwiftData 导入和基本的 ModelContainer 初始化逻辑。关键代码如下： import SwiftUI import SwiftData @main struct CloudKitCrashTestApp: App { let sharedModelContainer: ModelContainer init() { // 使用空 Schema 进行诊断 let schema = Schema([]) // *不* 指定 cloudKitDatabase let modelConfiguration = ModelConfiguration(schema: schema, isStoredInMemoryOnly: false) do { sharedModelContainer = try ModelContainer(for: schema, configurations: [modelConfiguration]) print("ModelContainer created successfully.") } catch { // 在关联 Container 后，会在此处崩溃 fatalError("Could not create ModelContainer: \(error)") } } var body: some Scene { WindowGroup { ContentView() .modelContainer(sharedModelContainer) } } } // ... ContentView 定义 ... 进入项目的 Signing & Capabilities 标签页。 点击 + Capability 添加 iCloud。 在 iCloud 服务中，勾选 CloudKit。 此时，不要在 Containers 部分选择任何容器。 运行应用: 应用应该能够成功启动，并在控制台打印 "ModelContainer created successfully."。 停止应用。 回到 Signing & Capabilities -> iCloud -> Containers。 点击 + 添加一个新的自定义容器，或选择 Xcode 默认建议的容器。确保一个容器 ID 被明确选中。 再次运行应用: 应用现在会在启动时立即崩溃，fatalError 被触发。 预期结果: 即使在 Signing & Capabilities 中关联了 iCloud Container，应用也应该能够成功初始化 ModelContainer（尤其是当代码中未使用 cloudKitDatabase 或使用空 Schema 时），不应崩溃。 实际结果: 应用在 ModelContainer 初始化时崩溃，抛出 fatalError，错误信息为： Could not create ModelContainer: SwiftDataError(_error: SwiftData.SwiftDataError._Error.loadIssueModelContainer, _explanation: nil) 补充说明: 此问题在 iPhone 模拟器上稳定复现。 尝试清理构建文件夹 (Clean Build Folder)、删除派生数据 (Derived Data) 未能解决问题。 使用 Xcode 模板创建项目（勾选 "Host in CloudKit"）并在之后手动取消选择 Container 可以运行，但一旦重新选择 Container 就会崩溃，现象一致。 这表明问题与 ModelContainer 初始化过程在检测到项目关联了具体 iCloud Container 标识符（可能涉及读取 .entitlements 文件或准备相关环境）时发生的内部错误有关，而不是由于实际的 CloudKit 同步代码或模型定义。 影响: 此 Bug 阻止了在当前的 Xcode 和 macOS 环境下开发和测试任何需要关联 iCloud Container 的 SwiftData 应用。

Hey iOS Dev's, I’m currently working on a Swift Package Manager (SPM) for WireGuard, originally developed by a previous team member. It was working fine in Xcode 15.2, but after upgrading to Xcode 16 and Swift 6, I need to update the SPM to ensure compatibility with my base projects and other projects relying on it. With Apple making Xcode 16 mandatory for app submissions starting April 24, this has become an urgent issue. I’ve searched extensively but haven’t found a working solution yet. Has anyone faced similar challenges with Swift 6 migration and SPM updates? Any insights, best practices, or debugging tips would be greatly appreciated! Let’s connect and collaborate—I’d love to discuss possible solutions! 😊 #iOSDevelopment #Swift6 #Xcode16 #SPM #WireGuard #iOS #Swift #SoftwareEngineering #AppStore

It seems like, by default, the preview pane tries to align to 50% of the editor pane's width. I prefer to shrink the preview pane to around ~30% of the screen so I have more space for code. This used to work fine—at least until I restarted Xcode. I never understood why the setting wouldn’t persist across sessions, but fine, that was a tradeoff I was willing to live with. However, with Xcode 16.3, it seems like Xcode forgets the manually adjusted preview pane width as soon as I switch to a different file. This has definitely impacted my productivity, as I now find myself readjusting the pane size dozens of times in a single session. Am I holding it wrong? Is anyone else experiencing this? And while we’re at it—why not make this a persistent setting so everyone can tweak the width to their liking?

Hi, upgraded to Xcode Version 16.3 (16E140) today and now Playground can't execute JSON decoding. The code below is taken from Apple's own JSONDecoder example: struct GroceryProduct: Codable { var name: String var points: Int var description: String? } let json = """ { "name": "Durian", "points": 600, "description": "A fruit with a distinctive scent." } """.data(using: .utf8)! let decoder = JSONDecoder() let product = try decoder.decode(GroceryProduct.self, from: json) print(product.name) // Prints "Durian" This use to work in the previous Xcode version. Now I get this error: The LLDB RPC server has crashed. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. This file doesn't exist in the location. I've restarted Xcode and the Mac, same error. Any thoughts?

Hi All, I'll start by saying i am complete beginner when it comes to coding/ developing. So please be easy on me, im also using AI tools to help and learn so apologies if what im saying doesnt make sense. The error im getting is /Services/SupabaseManager.swift:47:29 Cannot find 'GlobalOptions' in scope From AI tells me 'GlobalOptions' is defined a types.swift file in the supabase package public struct GlobalOptions: Sendable { /// Optional headers for initializing the client, it will be passed down to all sub-clients. public let headers: [String: String] /// A session to use for making requests, defaults to `URLSession.shared`. public let session: URLSession /// The logger to use across all Supabase sub-packages. public let logger: (any SupabaseLogger)? public init( headers: [String: String] = [:], session: URLSession = .shared, logger: (any SupabaseLogger)? = nil ) { self.headers = headers self.session = session self.logger = logger } } From what i can see i have added the supabase package successfully, following this guide - https://developer.apple.com/documentation/xcode/adding-package-dependencies-to-your-app Here are some screenshots of my xcode to show the added package.

Within Xcode's settings location section is a drop down menu to switch between setting the derived data location to be default, relative or custom. However its a global setting. I work on more than one project simultaneously, and for one of them I want the location set to relative, but default for all the others. Is there any way of achieving that?

Im a Quality Engineer and using Appium to automate in Physical devices so installed appium server and xcuitest. We need to build the webdriveragent project from xcode , when doing that getting the following error "Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/" I have a apple account licensed but still unable to resolve this, any immediate help is highly appreciated

Hi, I am able to build my iOS app successfully, developed in objective-C with iOS 17.5 SDK and Xcode 15. Due to requirement of Appstore we are trying to build with iOS 18 SDK and Xcode 16. When building getting error in LAEnvironmentState.h file: a) "Property requires field to be named" b) "Expected member name or ';' after declaration specifiers" Same app when opening with Xcode 15 gets build without any issue. Any help/suggestion would be appreciated.

So I believe my machine JUST updated to Xcode 16.3 (16E140). But it definitely just installed the latest iOS simulator 18.4. However, now my preview will sometimes give me the error Failed to launch app ”Picker.app” in reasonable time. If I add a space in my code, or hit refresh on the Preview, then it will run on the second or third attempt. Sometimes in between the refreshes, the preview will crash, and then it will work again. Anyone else experiencing this? Any ideas? Thanks

I've updated to Sequoia 15.4 and Xcode 16.3 on my Intel iMac 2019 and now everything Xcode does results in a spinning rainbow. Open a window? Spin. Look up documentation? Spin. Compile the app? Well that doesn't spin, but simple things like compiling a storyboard now takes over 5 minutes. Every compile needs to redo compiling Clang modules over and over again. And compiling the project at times just stalls out. It's been bad for a while but now with these versions it's gotten even worse. Is Apple just saying give up on Intel and get an M-series Mac just to develop with? On my Intel Mac the project takes over 19 minutes to compile. The main storyboard takes almost 7 minutes alone! It didn't take this long with Xcode 16.2. The other storyboards are showing times of over 4 minutes as well, a vast increase. A swift file with two functions, neither of which is over 10 lines, takes 87 seconds? It seems like everything involving swift code is now taking much much longer to compile. And don't even get me started on debugging. 90% of the time I can't find symbols, and clicking on a variable leads to spinning. Entering anything into the debugger window results in a warning about not being able to show the value and now I have to figure out how to cast the return value to what it should be? Why? All of this used to work, and now it doesn't. Or does, but not reliably. So after all this, I went and configured an M3 Mac mini I had dedicated for other purposes for Xcode. Took a while as the mini is very limited on space, and Xcode was too big. After getting it set up, certificates transferred, account set up etc, I copied the app's files and hit build. It took 47 seconds.

After upgrading to Xcode 16.3, whenever I open the Documentation window, Xcode started CPU hungry mode, forever. Does anyone else have the same experience as me? Is there any known remedy so far?

We have a script that builds several Swift Packages using xcodebuild. Since Xcode 16.3, xcodebuild crashes when invoked on a Swift Package, with the following error xcodebuild -list Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -list Resolve Package Graph ** INTERNAL ERROR: Unable to load workspace '/Users/glaurent/Developer/livesight-universalsdk/SDKs/Modules/CommonObjC' ** Uncaught Exception: -[Swift.__SwiftDeferredNSArray intersectsSet:]: unrecognized selector sent to instance 0x600002593e00 Stack: 0 __exceptionPreprocess (in CoreFoundation) 1 objc_exception_throw (in libobjc.A.dylib) 2 -[NSObject(NSObject) __retain_OA] (in CoreFoundation) 3 ___forwarding___ (in CoreFoundation) 4 _CF_forwarding_prep_0 (in CoreFoundation) 5 -[DVTCoreDevice(DVTCoreDeviceIDE) deviceSupportsBuildable:buildParameters:error:] (in IDEFoundation) 6 -[DVTCoreDevice(DVTCoreDeviceIDE) supportedArchitecturesForBuildableContext:buildParameters:error:] (in IDEFoundation) 7 _IDERunDestinationsForBuildableUsingDeviceWithBuildParameters (in IDEFoundation) 8 -[IDERunDestinationManager runDestinationsForScheme:schemeCommands:executionEnvironment:eligibleOnly:genericOnly:architectureVisibility:] (in IDEFoundation) 9 IDESchemeDetermineAvailableRunDestinations (in IDEFoundation) 10 -[IDEScheme _actuallyInvalidateAvailableRunDestinations] (in IDEFoundation) 11 addSchemeAndMakeActiveIfNecessary #1 (result:error:) in IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 12 IDESwiftPackage.generateScheme(with:buildable:additionalBuildables:unsetRunnable:makeActive:orderHint:) (in IDESwiftPackageCore) 13 IDESwiftPackage.generateSchemes(_:isRootPackage:) (in IDESwiftPackageCore) 14 IDESwiftPackage.update(from:graphHasErrors:delegate:) (in IDESwiftPackageCore) 15 specialized IDESPMWorkspaceDelegate.rootPackagesDidUpdate(packages:graphHasErrors:modelGraphSynchronizerToken:) (in IDESwiftPackageCore) 16 closure #1 in IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 17 partial apply for closure #1 in IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 18 <deduplicated_symbol> (in DVTFoundation) 19 <deduplicated_symbol> (in DVTFoundation) 20 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 21 __58-[DVTModelObjectGraph performBlockCoalescingModelChanges:]_block_invoke (in DVTFoundation) 22 -[DVTModelGraphTransactionScope performTransaction:] (in DVTFoundation) 23 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 24 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 25 IDESPMWorkspaceDelegate.disableWorkspaceContentSynchronization(during:) (in IDESwiftPackageCore) 26 IDESPMWorkspaceDelegate.packageGraphDidFinishAction(_:duration:result:) (in IDESwiftPackageCore) 27 <deduplicated_symbol> (in IDESwiftPackageCore) 28 SPMWorkspace.packageGraphActionFinished(_:) (in SwiftPM) 29 closure #2 in closure #3 in SPMWorkspace.processPackageGraphActionsInBackgroundIfNeeded(canProcessPackageGraphActions:) (in SwiftPM) 30 partial apply for closure #1 in SPMSDKPackageContainer.loadManifest() (in SwiftPM) 31 specialized thunk for @escaping @isolated(any) @callee_guaranteed @async () -> (@out A) (in SwiftPM) 32 partial apply for closure #1 in SPMSDKPackageContainer.loadManifest() (in SwiftPM) 33 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) (in libswift_Concurrency.dylib) This error happens regardless of the command passed to xcodebuild.

Since Xcode 16.3, the DerivedData folder has doubled in size, growing from 20.65GB to 47.66GB. This is unacceptable for us because my team frequently builds large apps, and our hard drives will soon run out of space. Otherwise, we would need to clean the DerivedData folder much more often, which also negatively impacts our build times. When I tried to investigate the source of this increase, I found that the CompilationCache.noindex folder was responsible. However, I didn’t notice any significant difference in incremental or clean build times, to be honest. Are there any ways to opt out of the feature?

Hi there, When using devicectl to manage files: It's unclear for which domains the username should be provided It's unclear how to determine the username Listing files USAGE: devicectl device info files [<options>] --device <uuid|ecid|serial_number|udid|name|dns_name> --domain-type <domain-type> FILE OPTIONS: --username <username> The username of the user we should target. Only relevant for certain domains. --domain-type <domain-type> The file service domain. Valid values are: temporary, appDataContainer, appGroupDataContainer, systemCrashLogs. You must specify a valid domain and identifier pair. Certain domains must be accompanied by an identifier that provides additional context. For example, if the domain is an app data container, the identifier is the bundle ID of the app. For temporary directories, the identifier is a unique client-provided string which is used to get your own space, separate from those of other clients. --domain-identifier <domain-identifier> A unique string used to provide additional context to the domain. --username The username of the user we should target. Only relevant for certain domains. In the domains, the username requirements are not mentioned. Copying files USAGE: devicectl device copy to --device <uuid|ecid|serial_number|udid|name|dns_name> --source <source> [--destination <destination>] [--user <user>] --domain-type <domain-type> [--domain-identifier <domain-identifier>] [--remove-existing-content <remove-existing-content>] [--verbose] [--quiet] [--timeout <seconds>] [--json-output <path>] [--log-output <path>] DEVICE OPTIONS: -d, --device <uuid|ecid|serial_number|udid|name|dns_name> The identifier, ECID, serial number, UDID, user-provided name, or DNS name of the device. FILE OPTIONS: --source <source> The item which should be copied. --destination <destination> The location to which the item should be copied. -u, --user <user> The name of the user we should target. Only relevant for certain domains. --domain-type <domain-type> The file service domain. Valid values are: temporary, appDataContainer, appGroupDataContainer, systemCrashLogs. You must specify a valid domain and identifier pair. Certain domains must be accompanied by an identifier that provides additional context. For example, if the domain is an app data container, the identifier is the bundle ID of the app. For temporary directories, the identifier is a unique client-provided string which is used to get your own space, separate from those of other clients. --domain-identifier <domain-identifier> A unique string used to provide additional context to the -u, --user The name of the user we should target. Only relevant for certain domains. The "certain domains" are not specified. user vs username The list files command takes: --username <username> The username of the user we should target. Only relevant for certain domains The copy command takes: -u, --user <user> The name of the user we should target. Only relevant for certain domains. Is there a difference between username and user? How do we figure out the user or username? From https://developer.apple.com/forums/thread/749649 I learned that about the "mobile" value, but why, and how? It would help if these arguments could be explained in more detail.

I don't know Xcode very well, and had been using it sporadically to test a project exported from Unity. I recently added a StoreKit Configuration to the project, and since then it gives me ≈10s after launching before the beach ball appears, and it never leaves. Xcode says it is "Indexing" but I don't know if that's an obvious culprit. I can still build my project via the fastlane tool, on the command line, and the newly-added StoreKit configuration works just fine. But I cannot use Xcode interactively any more, unless I re-export the project from Unity. The only difference between it working and hanging is the Store Kit configuration. How do I understand what's going on, and (ideally) fix it? The Activity Monitor gives a bunch of backtraces that don't have an obvious network or I/O culprit in them.

I have a framework project that uses third-party packages integrated via Swift Package Manager. The framework is then bundled as an XCFramework to support both simulator and device builds. However, when this XCFramework is consumed in a different version of Xcode than the one it was originally built with, it results in Swift compiler errors. For example, compiling the framework in Xcode 15.4 and then using it in a consumer app built with Xcode 16.2 results in Swift compiler errors(and vice-versa) Swift should work across different Xcode versions due to ABI stability. It appears the issue is originating from the referenced library, CryptoSwift. I’ve attached two projects: the [framework] project and the consumer app. https://bit.ly/4iWgi9i I’d really appreciate any help in identifying a solution to this problem.

Hello, For one of my recent release (2 versions ago), I used to be able to check its p50 of Hang Rate, but now it disappear and not showing up in XCode Organizer Metrics anymore. The p90 of Hang Rate of this version is still there. It's so unpredictable. Is there something we can do to get this data to populate? If not, may I understand usually why this issue will happen, is it something frond-end bug or is it because there is some thing abnormal going on in the back-end data?

Hi! I'm having problems installing the iOS 18.4 SDK for Xcode. The installation fails from within Xcode or from the command line with the following error message: $ xcodebuild -downloadPlatform iOS Downloading iOS 18.4 Simulator (22E238): Preparing to download...2025-04-05 10:16:50.451 xcodebuild[7138:103696] DVTDownloadable: Observed finish. Cancelling download asset. { assetId = 6fb1e5fe25ee1c372f7116516e615c556906bd4e; assetIdHash = 9d684dee0a7bae81ba9c4f79475976f41789eaf3; assetType = "com.apple.MobileAsset.iOSSimulatorRuntime"; attributesHash = 99e0653b3c175e32d4a045cb9be856573b2938c1; contentHash = d4aad730490a4476d8179d4cdb7c1fcae8dd388a; nonIdHash = be7dd5950580ff7c8e1f822b24bd76d58c08b8aa; pallasDynamicAssetIdHash = d7904ac1d93cc3702244074c49aafad923a6e2b4; policyHash = d3700ca0e5058eb1d7b21fd74b1c225a66f5e74e; urlHash = fc93246f74e44ae2b94a727bfd9bac228f69f961; }, error: (null) Downloading iOS 18.4 Simulator (22E238): Error: Error Domain=SimDiskImageErrorDomain Code=5 "(-67061 invalid signature (code or signature have been modified)" UserInfo={NSLocalizedDescription=(-67061 invalid signature (code or signature have been modified), unusableErrorDetail=} When trying to install in Xcode I get the following error message: Any idea on how to get this fixed is appreciated!

This question is related to this post (of mine). It seems default build settings do not include dSYM files needed when uploading embedding app package. But now Xcode issues new warnings about this. Now the question - how do I tell Xcode to create dSYM files for me, say when I build My.Framework? I asked AI chatbot which tells me that for release build I need to : set "Debug Information Format" to DWARF set "Strip Debug Symbols During Copy" to off I have item 1 turned on (which I believe is the default). But item 2 is on, maybe that's the reason I do not have dSYM files in final built My.Framework. Should I turn "Strip Debug Symbols During Copy" off?