Search results for

“xcode github”

95,422 results found

Post

Replies

Boosts

Views

Activity

Reply to Is it possible to download or copy the iOS SDK for Xcode 26.1 using command-line tools? If so, how?
The SDKs for all of Apple's platforms are included in the main Xcode XIP image. By SDK here, I mean the textual files for the API interfaces, like header files and other supporting content. You can see them all if you peak inside the Xcode bundle under Xcode.app/Contents/Developer/Platforms/.platform/Developer/SDKs. What you need to download isn't the SDK, it's the platform support components, which includes the simulator. While you always have the textual SDKs, you can't run a build without installing the platform support components, as they are used during the build process. So while you aren't downloading installing the textual part of the SDK content, the large extra component download enables builds using that SDK. You found the right documentation article, and you want a command like this: xcodebuild -downloadPlatform iOS -exportPath ~/Downloads That will give you a DMG file, which you can then also install through the command line over night in your data center with: xcodebuild -impor
2w
Xcode 26 Kills Productivity by Making Global the State of Inspectors Pane
Here's the text of FB22001359 I've just submitted: Xcode 26 changed the behavior of the Inspectors pane (which hopefully is a bug and not an intended behavior). Now, if I close (or open) the Inspectors pane in a window tab, it closes (or opens) the Inspectors pane in ALL tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years. By way of example: In a window tab that contains a .xib, I always want the Inspectors pane to be open. While in the window tabs that contain code files, I want the Inspectors pane to be closed. (Sometimes I do open it in certain window tabs, when needed). Before Xcode 26, the Inspectors pane was open or closed in each individual tab as the user desired. Now, if I close the Inspectors pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to open the Inspectors pane AGAIN. But then when I go back to a code window tab, I have to CLOSE the Ins
1
0
100
2w
Reply to Xcode 26 Butchers Productivity by Making Global the State of Navigators Pane
@DTS Engineer: Thanks for chiming in, Ed. I've just received a notification that this issue has been addressed in Xcode 26.3, which introduced a setting to enable individual width for navigators/inspectors in window tabs. It's great that the Xcode team listens to our feedback. P.S. My next rant that I'm about to post will be regarding the bug FB19249805 to highlight another productivity downgrade in Xcode 26: the inability to open files in new window tabs, which destroys workflows that have been established for many years.
2w
Xcode 26 Butchers Productivity by Making Global the State of Navigators Pane
Here's the text of FB22008758 I've just submitted: Xcode 26 changed the behavior of the Navigators pane (which hopefully is a bug and not an intended behavior). in Xcode 26, if I close (or open) the Navigators pane in a window tab, it closes (or opens) the Navigators pane in ALL window tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years (I've been using Xcode since 2006). By way of example: In a window tab that contains a .xib, I prefer the Navigators pane to be closed. While in all other window tabs (that contain code files and other items), I want the Navigators pane to be always displayed. Before Xcode 26, the Navigators pane was open or closed in each individual window tab as the user desired. But in Xcode 26, if I close the Navigators pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to close the Navigators pane AGAIN. But
2
0
96
2w
iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
Hi, I’m facing a consistent simulator boot issue that appears to start after iOS 18.2 simulator runtimes and persists in 18.6, 26.1, and 26.2. Observed behavior iOS 18.2 simulator works fine iOS 18.6 simulator does NOT boot iOS 26.1 / 26.2 simulators do NOT boot Tried everything reinstall/clear cache and all and event formatted the system Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding macOS: Sequoia Xcode: 26.1, 26.2 Machine: Apple Silicon Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = 2025-12-26 02:19:27 +0000; IDERunOperationFailingWorker = _IDEInstalliP.honeSimulatorWorker, Session = com apple CoreSimulator.SimDevice CCDECA56-4A59-491B-A830-0F3928FCD957; } Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit resp
7
0
870
2w
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK
Topic: App & System Services SubTopic: Drivers Tags:
2w
Foundation models not detectable in Xcode simulator
I'm building an app which runs around the Foundation model framework. My expected output is generated when testing on a real device or in preview in Xcode but it throws Foundation Model error when I try running it on the simulator. I'm using a Macbook M1 air and have apple intelligence turned on and my simulator run destination is also an iPad Pro M5 (26.0). Any solution for this as this is my submission for the SSC so I need to make it work on the simulator iPad. Thank you👾
6
0
392
2w
Reply to Foundation models not detectable in Xcode simulator
I'm seeing a similar issue as well. Seems like the Foundation model is just not available for iPhone and iPad simulators anymore. To test it out I created a simple playground (similar to https://developer.apple.com/events/resources/code-along-205/) and just used basic code: import FoundationModels import Playgrounds #Playground { // Create a new session with the language model. let session = LanguageModelSession() // Asynchronously generate a response from a text prompt. let response = try await session.respond(to: Generate a 3-day itinerary to Paris.) } For macOS simulator it works, but for iPhone and iPad simulators it gives either error: Apple Intelligence is not enabled. The operation couldn’t be completed. (FoundationModels.LanguageModelSession.GenerationError error -1.) I've tried Xcode 26.2. 26.3, 26.4 beta 1 & 2 versions. iPhone Simulators 26.2, 26.3 and 26.4 beta and none of them works. This is on a M4 Macbook pro I also have an old M1 Macbook pro I haven't used since December and just t
2w
How does AccessoryNotifications forward notifications to BLE accessories? What Service/Characteristic should the accessory implement?
Environment: iOS 26.4 beta Xcode 26.4 beta Framework: AccessoryNotifications, AccessorySetupKit, AccessoryTransportExtension Description: I'm implementing notification forwarding to a custom BLE accessory using the new AccessoryNotifications framework in iOS 26.4. I've set up an AccessoryDataProvider extension following the documentation, but I'm unclear about how the data is actually transmitted to the BLE accessory. Current Implementation: Main App - Uses AccessorySetupKit to discover and pair accessories: let descriptor = ASDiscoveryDescriptor() descriptor.bluetoothServiceUUID = CBUUID(string: FEE0) let displayItem = ASPickerDisplayItem( name: Notification Accessory, productImage: UIImage(systemName: applewatch)!, descriptor: descriptor ) accessorySession.showPicker(for: [displayItem]) { error in // Handle error } AccessoryDataProvider Extension - Implements NotificationsForwarding.AccessoryNotificationsHandler: @main struct AccessoryDataProvider: AccessoryTransportExtension.AccessoryDataProvider
1
0
110
2w
Apple wants me to change the Bundle ID (Non XCODE)
Hello! I have a web extension I've written to Google Chrome and Mozilla Firefox. It's made up of simple files. The extension (content.js) A manifest (manifest.json) file which explains the extension The icon (icon.png) Apple has developed App Store Connect / Xcode Cloud specifically for this. I upload those three files as a zip. I move it over to TestFlight for testing and then select Distribution to put it through Apple Review. This is my entire process. I have been doing this for 4+ months and Apple reviewed my application and put it up. I have then gone through 13 subsequent reviews (ALL POSITIVE) and have gone through version upgrades for months, no issue. On the 15th review, they want me to change the name of my application. I have done that in the content.js, the manifest.json, and anywhere that allows me to change it in App Store Connect. There is apparently one more place they want it changed. This is on the App Information / General Information tab, specifically the BundleID. The tip on that
4
0
356
2w
Swift Student Challenge environment selection question (iOS 26)
Hello, I recently submitted my Swift Student Challenge app playground and realized after submission that I accidentally selected Swift Playgrounds as the software to run it, instead of Xcode 26 or later. My project builds and runs successfully in Xcode 26 using the iOS 26 SDK and simulator. However, when opening the same .swiftpm project in the Swift Playgrounds app on iPad, it does not compile because Swift Playgrounds currently only supports up to iOS 18 SDK and does not support iOS 26 APIs. The submission itself is complete, builds correctly in Xcode, and was submitted before the deadline. The incorrect selection of Swift Playgrounds was an honest mistake during the submission process. I wanted to ask whether reviewers are able to run the submission using Xcode 26 in cases like this, or if there is anything I should do. Thank you very much for your time.
3
0
378
2w
Your request couldn't be completed
Steps to reproduce: Open Xcode 26.3 → Settings → Intelligence → Claude sign-in Click the sign-in button — spinner begins, never completes An email the arrives with a magic link. The magic link opened a browser page which displayed a 6-digit verification code with instructions reading enter this verification code where you first tried to sign in — i.e. back in Xcode. However, Xcode was showing only an endless spinner with no code entry field anywhere in the UI. This is the core bug. I did since manage to complete authentication sign-in through a second browser verification field that eventually appeared after about 10 minutes and did get signed in, but the Claude Intelligence agent still returns Your request could not be completed even after successful sign-in and a full Xcode restart. Prior to this bug starting at 10 am on February 19 I had been using the intelligence agent successfully for about a week. Anthropic did have some sort of event on their system around February
3
0
210
2w
Reply to Is it possible to download or copy the iOS SDK for Xcode 26.1 using command-line tools? If so, how?
The SDKs for all of Apple's platforms are included in the main Xcode XIP image. By SDK here, I mean the textual files for the API interfaces, like header files and other supporting content. You can see them all if you peak inside the Xcode bundle under Xcode.app/Contents/Developer/Platforms/.platform/Developer/SDKs. What you need to download isn't the SDK, it's the platform support components, which includes the simulator. While you always have the textual SDKs, you can't run a build without installing the platform support components, as they are used during the build process. So while you aren't downloading installing the textual part of the SDK content, the large extra component download enables builds using that SDK. You found the right documentation article, and you want a command like this: xcodebuild -downloadPlatform iOS -exportPath ~/Downloads That will give you a DMG file, which you can then also install through the command line over night in your data center with: xcodebuild -impor
Replies
Boosts
Views
Activity
2w
Reply to Xcode 26 Kills Productivity by Making Global the State of Inspectors Pane
I've just received a notification that this issue has been addressed in Xcode 26.3, which introduced a setting to enable individual width for navigators/inspectors in window tabs. It's great that the Xcode team listens to our feedback.
Replies
Boosts
Views
Activity
2w
Xcode 26 Kills Productivity by Making Global the State of Inspectors Pane
Here's the text of FB22001359 I've just submitted: Xcode 26 changed the behavior of the Inspectors pane (which hopefully is a bug and not an intended behavior). Now, if I close (or open) the Inspectors pane in a window tab, it closes (or opens) the Inspectors pane in ALL tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years. By way of example: In a window tab that contains a .xib, I always want the Inspectors pane to be open. While in the window tabs that contain code files, I want the Inspectors pane to be closed. (Sometimes I do open it in certain window tabs, when needed). Before Xcode 26, the Inspectors pane was open or closed in each individual tab as the user desired. Now, if I close the Inspectors pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to open the Inspectors pane AGAIN. But then when I go back to a code window tab, I have to CLOSE the Ins
Replies
1
Boosts
0
Views
100
Activity
2w
Reply to Xcode 26 Butchers Productivity by Making Global the State of Navigators Pane
@DTS Engineer: Thanks for chiming in, Ed. I've just received a notification that this issue has been addressed in Xcode 26.3, which introduced a setting to enable individual width for navigators/inspectors in window tabs. It's great that the Xcode team listens to our feedback. P.S. My next rant that I'm about to post will be regarding the bug FB19249805 to highlight another productivity downgrade in Xcode 26: the inability to open files in new window tabs, which destroys workflows that have been established for many years.
Replies
Boosts
Views
Activity
2w
Xcode 26 Butchers Productivity by Making Global the State of Navigators Pane
Here's the text of FB22008758 I've just submitted: Xcode 26 changed the behavior of the Navigators pane (which hopefully is a bug and not an intended behavior). in Xcode 26, if I close (or open) the Navigators pane in a window tab, it closes (or opens) the Navigators pane in ALL window tabs. This is insanely horrible, unproductive, time-wasting behavior that breaks workflows that has been established for many years (I've been using Xcode since 2006). By way of example: In a window tab that contains a .xib, I prefer the Navigators pane to be closed. While in all other window tabs (that contain code files and other items), I want the Navigators pane to be always displayed. Before Xcode 26, the Navigators pane was open or closed in each individual window tab as the user desired. But in Xcode 26, if I close the Navigators pane in one window tab, the pane closes EVERYWHERE. Thus when, for example, I go to a .xib window tab, I have to close the Navigators pane AGAIN. But
Replies
2
Boosts
0
Views
96
Activity
2w
iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
Hi, I’m facing a consistent simulator boot issue that appears to start after iOS 18.2 simulator runtimes and persists in 18.6, 26.1, and 26.2. Observed behavior iOS 18.2 simulator works fine iOS 18.6 simulator does NOT boot iOS 26.1 / 26.2 simulators do NOT boot Tried everything reinstall/clear cache and all and event formatted the system Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding macOS: Sequoia Xcode: 26.1, 26.2 Machine: Apple Silicon Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = 2025-12-26 02:19:27 +0000; IDERunOperationFailingWorker = _IDEInstalliP.honeSimulatorWorker, Session = com apple CoreSimulator.SimDevice CCDECA56-4A59-491B-A830-0F3928FCD957; } Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit resp
Replies
7
Boosts
0
Views
870
Activity
2w
Reply to iOS Simulator fails to boot (18.6 / 26.1 / 26.2) – launchd_sim could not bind to session
This keeps happening in Xcode cloud watchOS simulator 26.2 (Apple Watch Series 10 (46mm) (watchOS 26.2) simulator) and I cannot finish my test CI/CD pipelines. How can I solve?
Replies
Boosts
Views
Activity
2w
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
How do I go about troubleshooting this? So, the place to start is actually with this log message: eventually ends with provider entitlements check failed The log message is the final, generic, error message printed by IOUserService when the entitlement check process fails. A few things to understand about what this tells you about what HASN'T gone wrong: Basic entitlement validation happens outside the kernel well before this point. So getting to this point means that your DEXT is at least somewhat coherently signed, even if it doesn't actually work. IOKit passive matching happens at the same time as entitlement checking (just before actually), so this message means that either your passive match failed or your entitlement configuration was wrong. So, the next step here is to actually take a closer look at this logging: In the logs I see the matching log entry for my driver, and it goes through some setup that mentions my driver and some entries that do not. Focusing on the entitlement checking side, each IOK
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
2w
Foundation models not detectable in Xcode simulator
I'm building an app which runs around the Foundation model framework. My expected output is generated when testing on a real device or in preview in Xcode but it throws Foundation Model error when I try running it on the simulator. I'm using a Macbook M1 air and have apple intelligence turned on and my simulator run destination is also an iPad Pro M5 (26.0). Any solution for this as this is my submission for the SSC so I need to make it work on the simulator iPad. Thank you👾
Replies
6
Boosts
0
Views
392
Activity
2w
Reply to Foundation models not detectable in Xcode simulator
I'm seeing a similar issue as well. Seems like the Foundation model is just not available for iPhone and iPad simulators anymore. To test it out I created a simple playground (similar to https://developer.apple.com/events/resources/code-along-205/) and just used basic code: import FoundationModels import Playgrounds #Playground { // Create a new session with the language model. let session = LanguageModelSession() // Asynchronously generate a response from a text prompt. let response = try await session.respond(to: Generate a 3-day itinerary to Paris.) } For macOS simulator it works, but for iPhone and iPad simulators it gives either error: Apple Intelligence is not enabled. The operation couldn’t be completed. (FoundationModels.LanguageModelSession.GenerationError error -1.) I've tried Xcode 26.2. 26.3, 26.4 beta 1 & 2 versions. iPhone Simulators 26.2, 26.3 and 26.4 beta and none of them works. This is on a M4 Macbook pro I also have an old M1 Macbook pro I haven't used since December and just t
Replies
Boosts
Views
Activity
2w
How does AccessoryNotifications forward notifications to BLE accessories? What Service/Characteristic should the accessory implement?
Environment: iOS 26.4 beta Xcode 26.4 beta Framework: AccessoryNotifications, AccessorySetupKit, AccessoryTransportExtension Description: I'm implementing notification forwarding to a custom BLE accessory using the new AccessoryNotifications framework in iOS 26.4. I've set up an AccessoryDataProvider extension following the documentation, but I'm unclear about how the data is actually transmitted to the BLE accessory. Current Implementation: Main App - Uses AccessorySetupKit to discover and pair accessories: let descriptor = ASDiscoveryDescriptor() descriptor.bluetoothServiceUUID = CBUUID(string: FEE0) let displayItem = ASPickerDisplayItem( name: Notification Accessory, productImage: UIImage(systemName: applewatch)!, descriptor: descriptor ) accessorySession.showPicker(for: [displayItem]) { error in // Handle error } AccessoryDataProvider Extension - Implements NotificationsForwarding.AccessoryNotificationsHandler: @main struct AccessoryDataProvider: AccessoryTransportExtension.AccessoryDataProvider
Replies
1
Boosts
0
Views
110
Activity
2w
Apple wants me to change the Bundle ID (Non XCODE)
Hello! I have a web extension I've written to Google Chrome and Mozilla Firefox. It's made up of simple files. The extension (content.js) A manifest (manifest.json) file which explains the extension The icon (icon.png) Apple has developed App Store Connect / Xcode Cloud specifically for this. I upload those three files as a zip. I move it over to TestFlight for testing and then select Distribution to put it through Apple Review. This is my entire process. I have been doing this for 4+ months and Apple reviewed my application and put it up. I have then gone through 13 subsequent reviews (ALL POSITIVE) and have gone through version upgrades for months, no issue. On the 15th review, they want me to change the name of my application. I have done that in the content.js, the manifest.json, and anywhere that allows me to change it in App Store Connect. There is apparently one more place they want it changed. This is on the App Information / General Information tab, specifically the BundleID. The tip on that
Replies
4
Boosts
0
Views
356
Activity
2w
Swift Student Challenge environment selection question (iOS 26)
Hello, I recently submitted my Swift Student Challenge app playground and realized after submission that I accidentally selected Swift Playgrounds as the software to run it, instead of Xcode 26 or later. My project builds and runs successfully in Xcode 26 using the iOS 26 SDK and simulator. However, when opening the same .swiftpm project in the Swift Playgrounds app on iPad, it does not compile because Swift Playgrounds currently only supports up to iOS 18 SDK and does not support iOS 26 APIs. The submission itself is complete, builds correctly in Xcode, and was submitted before the deadline. The incorrect selection of Swift Playgrounds was an honest mistake during the submission process. I wanted to ask whether reviewers are able to run the submission using Xcode 26 in cases like this, or if there is anything I should do. Thank you very much for your time.
Replies
3
Boosts
0
Views
378
Activity
2w
Reply to Your request couldn't be completed
i have the same issue, i have a claude account paid, with xcode 26.3 but im having infinite loading after finishing the SSO. The infinite loop appears in xcode
Replies
Boosts
Views
Activity
2w
Your request couldn't be completed
Steps to reproduce: Open Xcode 26.3 → Settings → Intelligence → Claude sign-in Click the sign-in button — spinner begins, never completes An email the arrives with a magic link. The magic link opened a browser page which displayed a 6-digit verification code with instructions reading enter this verification code where you first tried to sign in — i.e. back in Xcode. However, Xcode was showing only an endless spinner with no code entry field anywhere in the UI. This is the core bug. I did since manage to complete authentication sign-in through a second browser verification field that eventually appeared after about 10 minutes and did get signed in, but the Claude Intelligence agent still returns Your request could not be completed even after successful sign-in and a full Xcode restart. Prior to this bug starting at 10 am on February 19 I had been using the intelligence agent successfully for about a week. Anthropic did have some sort of event on their system around February
Replies
3
Boosts
0
Views
210
Activity
2w