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?
Xcode
RSS for tagBuild, test, and submit your app using Xcode, Apple's integrated development environment.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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!
Topic:
Developer Tools & Services
SubTopic:
Xcode
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
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.
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!
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
Topic:
Developer Tools & Services
SubTopic:
Xcode
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
Topic:
Developer Tools & Services
SubTopic:
Xcode
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
Topic:
Developer Tools & Services
SubTopic:
Xcode
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
)
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;
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.
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!
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Xcode
Signing Certificates
Developer Program
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!
Hi everyone, have any of you tried running an app from Xcode 16.x (during development, running on device) on one of the iPhone 17 models? I'd like to know whether it still works or if someone would need to update to Xcode 26 for that to work.
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!
Topic:
Developer Tools & Services
SubTopic:
Xcode
My app start up has became horrid. It takes 1 minute to open SQLlite database for my rust core. Impossible to work...
I have Address Sanitizer, Thread Perf Checker and Thread Sanitizer disabled...
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.
Hey there
Just updated to Xcode 26 on mac OS Sequoia (MBP M1 Max 32GB, 2021, so you know, still pretty decent and capable).
Xcode is super slow on building, but also on editing. There is a lag between what I type and what is displayed. Am I the only one experiencing this?
Is there something I should look into?
Topic:
Developer Tools & Services
SubTopic:
Xcode
I am using the latest version of Xcode 16, and I have created a GPX file in my project. However, I am unable to see or select the file to simulate the GPS location. I have attempted to uninstall and reinstall Xcode completely, but the issue persists. Has anyone encountered a similar problem? How can I resolve this? Thank you.
My app hangs and I get this error when using an inspector view on macos tahoe. Changing to a different type of view resolves the issue.
The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window.
<SwiftUI.AppKitWindow: 0x8897e0000> 0xb4d8 (46296) {{1004, 182}, {1254, 948}} en Future marking as needing Update Constraints in Window might be ignored.
FAULT: NSGenericException: The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window.
<SwiftUI.AppKitWindow: 0x8897e0000> 0xb4d8 (46296) {{1004, 182}, {1254, 948}} en; (user info absent)