Search results for

“xcode github”

96,025 results found

Post

Replies

Boosts

Views

Activity

Reply to Sometimes my apps crash on launch at _libsecinit_appsandbox.cold.6
Thanks, I'll do that, although I'm not very hopeful that I'll get the crash again soon (while I've been observing the crash reports downloaded by Xcode for many months). Just to be clear, should I then extract the sysdiagnose and look in the system_logs.logarchive file? In the sysdiagnose I uploaded to Feedback Assistant I can only see the last 5 minutes, is that correct?
Topic: App & System Services SubTopic: Core OS Tags:
1h
Sometimes my apps crash on launch at _libsecinit_appsandbox.cold.6
I first started observing this behaviour through the crash logs of one of my App Store apps which are downloaded by Xcode. Then 3 days ago the same crash happened when launching one of my other apps on my own Mac. On the next try, the app launched correctly. The crash logs don't show any of my app's symbols, only a single thread that does something with libsecinit. I have no idea what the problem is, and since these crashes are also downloaded by Xcode, one would get the impression it’s a fault in my programming… but without any hint as to what I’m doing wrong, I have no chance to fix it, and so I get the feeling that it’s actually a macOS bug. I created FB22712334. crash
Topic: App & System Services SubTopic: Core OS Tags:
6
0
100
1h
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to codex-cli 0.129.0 via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
5
0
102
3h
Reply to Xcode won't sign into ChatGPT Codex account anymore
You're lucky I've got 0.129.0-alpha.9 on my MMM4Pro in Xcode RC 26.5 but I can't get it on my MBPM1P in Xcode RC 26.5, but 0.120.0 is fine and signs in. on the MBPM1P in Xcode 26.4.1, I can't sign-in with that tho... So in summary on the: MacMini M4 Pro signed in to 0.129.0-alpha.9 and Codex 5.5 picked (Xcode RC 26.5) MacBook Pro M1 Pro signed in to 0.120.0 and Codex 5.4 picked, (i.e. can't get alpha.9 so can't get 5.5! even tho Xcode RC 26.5!) My problem I think is I didn't upgrade the Codex on the MBP before doing the macOS RC 26.5 + Xcode RC 26.5 (Like I did on the MacMini). And since I didn't upgrade in Xcode 26.4.1, when I did the full RC cycle, when I launched Xcode RC 26.5, it upgrade the Codex Plug-in but stopped at 0.120.0! On the MBP+Xcode RC 26.5 UGH 🤷🏻
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3h
Localization doesn't work in watchOS widget configuration intent
Hi, I have a problem with watchOS widget configuration intents. It turns out that watchOS is unable to load text for localization keys. This is how I set configuration parameter in WidgetConfigurationIntent: @Parameter( title: LocalizedStringResource( watchWidgetConfig.showSymbols, defaultValue: Symbole, table: WidgetLocalizable, bundle: widgetBundle ), default: true ) var showSymbols: Bool Unfortunately, on a device always the defaultValue is used. I tried everything and nothing works. What's weird, it correctly works on watchOS simulator and if you configure widgets in iOS Watch app. On real Apple Watch, the defaultValue is displayed. I'm not sure if it's important but both: the Swift file with WidgetConfigurationIntent and WidgetLocalizable.xcstring are included in two targets: Watch Widget Extension and Watch App. I tried so far: All variants of LocalizableStringResource init. With/without table, with/without bundle. Previously I had texts in Localizable.strings, I migrated it to WidgetLocalizable.xcstrin
Topic: App & System Services SubTopic: Widgets & Live Activities Tags:
6
0
305
4h
After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
After enabling Enhanced Security for an existing iOS project (mixed Objective-C / Swift) I get the linker error: Library 'c++polyfills' not found This happens when compiling for a simulator as run destination. Device builds (debug) or archiving a release build works. However I need to be able to test on a simulator... Xcode version is 26.4.1, Simulator uses iOS 26.4.1
Topic: Developer Tools & Services SubTopic: Xcode Tags:
3
0
121
7h
Reply to After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
Thanks for those extra titbits. Using that, I was able to reproduce the problem: Using Xcode 26.4, I created a new project from the iOS > App template, choosing Swift as the language. I set the deployment target to iOS 17.7. And chose Any iOS Simulator as the run target. I added the Enhanced Security capability and checked Enable Hardware Memory Tagging. At this point things were still building just fine. I added a new Objective-C class to the project. And lo! that triggers the problem. I then raised the deployment target up to iOS 18.6 and the problem went away. So, it seems like the combination of a simulator build for iOS 17 with MTE enabled. Interesting. That’s clearly a supported configuration, so you should definitely file a bug about this. Once you’re done, reply here with your bug number so that I can add my own internal comments to it. How much testing do you do in the iOS 17 simulator? If the answer is “None at all.” you could work around this by temporary raising the deployment target f
Topic: Developer Tools & Services SubTopic: Xcode Tags:
7h
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
[quote='887212022, fbartolom, /thread/825703?answerId=887212022#887212022, /profile/fbartolom'] Unfortunately using your code … produces … Sending 'completionHandler' risks causing data races [/quote] Hmmm, it didn’t when I tested it. Lemme try that again: Using Xcode 26.4, I created a new project from the iOS > App template template. As part of that, I selected Storyboard from the Interface popup. I changed the Swift Language Version build setting to Swift 6. I added GeoreferenceQueue.swift and copied my GeoreferenceQueue to it. I added my application(_:handleEventsForBackgroundURLSession:completionHandler:) method to the AppDelegate class. It built without error. But keep in mind that my example was meant to be an expedient option. I agree with Etresoft’s comments [1] that you should step back and consider whether you want to change your overall approach. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, the comments he
Topic: Programming Languages SubTopic: Swift Tags:
7h
Reply to Agents in Xcode: Codex Sign In not working
Hey Albert, thanks for your competent reply. Yes, Xcode release candidate 26.5 (17F42). I have deleted the cache. I have also deleted codex* and chatgpt* (empty) from the system keychain. No VPN connection. The problem persists. I have now switched Xcode over to use Authenticate with configuration file. It does that, but I am unsure whether the configuration file works, and I don't really know how to check. The codex* entries in keychain are back since I logged in on the Codex app. Kind regards
Topic: Developer Tools & Services SubTopic: Xcode
7h
CloudKit container in a broken state
I'm a first time developer, relying heavily on Claude Agent. In my app, I'm using CloudKit to sync data between devices, but after a migration something got corrupted and syncing is no longer working. I'm using SwiftData with NSPersistentCloudKitContainer. I'm using Xcode 26.4.1 on a Mac mini. I'm testing my app on the same Mac mini, running Tahoe 26.4.1 as well as an iPad 12.9 running iPadOS 26.3.1 and an iPhone running iOS 18.7.8. Sync stopped after a cachedTotal property was added to a SwiftData model, which triggered a backfill migration that wrote to all records simultaneously across multiple devices. This was followed by an iCloud sign-out/sign-in on the Mac. Here’s a summary of everything I’ve tried already: Reset All Data on all devices multiple times Deleted and reinstalled the app on all devices Deleted the CloudKit zone twice Force-deleted local SQLite store files to clear change tokens Zone and subscription both appear correct in the dashboard Change token updates when data is written (co
Topic: App & System Services SubTopic: iCloud & Data Tags:
2
0
109
8h
Reply to Sending 'geoRegion' risks causing data races
[quote='887247022, Etresoft, /thread/825634?answerId=887247022#887247022, /profile/Etresoft'] Most Apple APIs, with very few exceptions … should only be called on the main thread. [/quote] I don’t agree with that summary. Ignoring Swift concurrency, I generally group Apple’s Cocoa APIs into four categories: Main thread — These are limited to the main thread, with occasional exceptions. The canonical example of this is AppKit. Thread safe — These have internal locking and can be used from any thread. A good example is NSOperationQueue. Thread or queue confined — These must be used from a specific thread (or queue) that’s not necessarily the main thread (or queue). NSRunLoop is a good example of this. Serialisation required — These have no internal locking but can be used from arbitrary threads as long as you serialise that access. A good example is NSMutableDictionary. Your summary doesn’t include the last two categories, and IME that’s the biggest group of traditional Cocoa APIs. Unfortunately it’s hard to di
Topic: Programming Languages SubTopic: Swift Tags:
8h
notarytool submissions stuck "In Progress" indefinitely — account-specific issue?
Hello, I've been trying to notarize my macOS app using xcrun notarytool, but all submissions get stuck in In Progress status indefinitely (30+ minutes, never resolve). Environment: Tool: xcrun notarytool (Xcode 16) Bundle ID: io.pix-cull.app Team ID: C473MUK7G2 App type: PyInstaller-built .app, wrapped in a signed .dmg Stuck submission IDs: 00e953da (first attempt) f7ab027e 3e35fc3f 293541bc-ba61-4ccb-a273-a8f34cda2422 (most recent) Steps I've already taken: Disabled UPX compression in PyInstaller spec Signed all binaries inside-out (deepest first, .app last) Used --timestamp flag during codesign Verified Apple system status — all services show green Waited 24+ hours on the oldest submission — still In Progress What I observe: Running xcrun notarytool info returns status: In Progress every time, no matter how long I wait. The submission never transitions to Accepted or Invalid. Other developers report notarization completing in 2–15 minutes. I also submitted a ticket to Apple Developer Support (DTS)
Topic: Code Signing SubTopic: Notarization
1
0
68
10h
com.apple.developer.automatic-assessment-configuration entitlement missing from manually downloaded Distribution/InHouse Provisioning Profile
We are implementing an exam mode feature for an educational app used in schools, which restricts device usage during assessments. We requested the Automatic Assessment Configuration capability, received approval from Apple, and confirmed that the capability is listed as Assigned under our App ID in the Apple Developer portal. What works: When using a Development Provisioning Profile (downloaded from the portal), the entitlement key com.apple.developer.automatic-assessment-configuration is included in the profile, and our exam lock feature works correctly in development testing. The problem: When we manually download a Distribution (InHouse/Enterprise) Provisioning Profile from the portal — even after creating a new one — the entitlement key com.apple.developer.automatic-assessment-configuration is not present in the profile. verified this by running: security cms -D -i YourProfile.mobileprovision The key appears in the Development PP but is absent in the manually downloaded Distribution PP, despite the App ID
Topic: Code Signing SubTopic: Entitlements Tags:
1
0
82
10h
Reply to Sometimes my apps crash on launch at _libsecinit_appsandbox.cold.6
Thanks, I'll do that, although I'm not very hopeful that I'll get the crash again soon (while I've been observing the crash reports downloaded by Xcode for many months). Just to be clear, should I then extract the sysdiagnose and look in the system_logs.logarchive file? In the sysdiagnose I uploaded to Feedback Assistant I can only see the last 5 minutes, is that correct?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1h
Sometimes my apps crash on launch at _libsecinit_appsandbox.cold.6
I first started observing this behaviour through the crash logs of one of my App Store apps which are downloaded by Xcode. Then 3 days ago the same crash happened when launching one of my other apps on my own Mac. On the next try, the app launched correctly. The crash logs don't show any of my app's symbols, only a single thread that does something with libsecinit. I have no idea what the problem is, and since these crashes are also downloaded by Xcode, one would get the impression it’s a fault in my programming… but without any hint as to what I’m doing wrong, I have no chance to fix it, and so I get the feeling that it’s actually a macOS bug. I created FB22712334. crash
Topic: App & System Services SubTopic: Core OS Tags:
Replies
6
Boosts
0
Views
100
Activity
1h
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to codex-cli 0.129.0 via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
5
Boosts
0
Views
102
Activity
3h
Reply to Xcode won't sign into ChatGPT Codex account anymore
You're lucky I've got 0.129.0-alpha.9 on my MMM4Pro in Xcode RC 26.5 but I can't get it on my MBPM1P in Xcode RC 26.5, but 0.120.0 is fine and signs in. on the MBPM1P in Xcode 26.4.1, I can't sign-in with that tho... So in summary on the: MacMini M4 Pro signed in to 0.129.0-alpha.9 and Codex 5.5 picked (Xcode RC 26.5) MacBook Pro M1 Pro signed in to 0.120.0 and Codex 5.4 picked, (i.e. can't get alpha.9 so can't get 5.5! even tho Xcode RC 26.5!) My problem I think is I didn't upgrade the Codex on the MBP before doing the macOS RC 26.5 + Xcode RC 26.5 (Like I did on the MacMini). And since I didn't upgrade in Xcode 26.4.1, when I did the full RC cycle, when I launched Xcode RC 26.5, it upgrade the Codex Plug-in but stopped at 0.120.0! On the MBP+Xcode RC 26.5 UGH 🤷🏻
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
3h
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
Also I have no Swift 6.4 version in my Swift options. As you may see in the picture, both in the official Xcode version as the beta one.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
3h
Localization doesn't work in watchOS widget configuration intent
Hi, I have a problem with watchOS widget configuration intents. It turns out that watchOS is unable to load text for localization keys. This is how I set configuration parameter in WidgetConfigurationIntent: @Parameter( title: LocalizedStringResource( watchWidgetConfig.showSymbols, defaultValue: Symbole, table: WidgetLocalizable, bundle: widgetBundle ), default: true ) var showSymbols: Bool Unfortunately, on a device always the defaultValue is used. I tried everything and nothing works. What's weird, it correctly works on watchOS simulator and if you configure widgets in iOS Watch app. On real Apple Watch, the defaultValue is displayed. I'm not sure if it's important but both: the Swift file with WidgetConfigurationIntent and WidgetLocalizable.xcstring are included in two targets: Watch Widget Extension and Watch App. I tried so far: All variants of LocalizableStringResource init. With/without table, with/without bundle. Previously I had texts in Localizable.strings, I migrated it to WidgetLocalizable.xcstrin
Topic: App & System Services SubTopic: Widgets & Live Activities Tags:
Replies
6
Boosts
0
Views
305
Activity
4h
After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
After enabling Enhanced Security for an existing iOS project (mixed Objective-C / Swift) I get the linker error: Library 'c++polyfills' not found This happens when compiling for a simulator as run destination. Device builds (debug) or archiving a release build works. However I need to be able to test on a simulator... Xcode version is 26.4.1, Simulator uses iOS 26.4.1
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
3
Boosts
0
Views
121
Activity
7h
Reply to After enabling Enhaced Security the linker error Library 'c++polyfills' not found occurs (Simulator only)
Thanks for those extra titbits. Using that, I was able to reproduce the problem: Using Xcode 26.4, I created a new project from the iOS > App template, choosing Swift as the language. I set the deployment target to iOS 17.7. And chose Any iOS Simulator as the run target. I added the Enhanced Security capability and checked Enable Hardware Memory Tagging. At this point things were still building just fine. I added a new Objective-C class to the project. And lo! that triggers the problem. I then raised the deployment target up to iOS 18.6 and the problem went away. So, it seems like the combination of a simulator build for iOS 17 with MTE enabled. Interesting. That’s clearly a supported configuration, so you should definitely file a bug about this. Once you’re done, reply here with your bug number so that I can add my own internal comments to it. How much testing do you do in the iOS 17 simulator? If the answer is “None at all.” you could work around this by temporary raising the deployment target f
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
7h
Reply to Passing closure as a 'sending' parameter risks causing data races between code in the current task and concurrent execution
[quote='887212022, fbartolom, /thread/825703?answerId=887212022#887212022, /profile/fbartolom'] Unfortunately using your code … produces … Sending 'completionHandler' risks causing data races [/quote] Hmmm, it didn’t when I tested it. Lemme try that again: Using Xcode 26.4, I created a new project from the iOS > App template template. As part of that, I selected Storyboard from the Interface popup. I changed the Swift Language Version build setting to Swift 6. I added GeoreferenceQueue.swift and copied my GeoreferenceQueue to it. I added my application(_:handleEventsForBackgroundURLSession:completionHandler:) method to the AppDelegate class. It built without error. But keep in mind that my example was meant to be an expedient option. I agree with Etresoft’s comments [1] that you should step back and consider whether you want to change your overall approach. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, the comments he
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
7h
Agents in Xcode: Codex Sign In not working
Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says Not Signed In. I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574
Topic: Developer Tools & Services SubTopic: Xcode
Replies
4
Boosts
0
Views
92
Activity
7h
Reply to Agents in Xcode: Codex Sign In not working
Hey Albert, thanks for your competent reply. Yes, Xcode release candidate 26.5 (17F42). I have deleted the cache. I have also deleted codex* and chatgpt* (empty) from the system keychain. No VPN connection. The problem persists. I have now switched Xcode over to use Authenticate with configuration file. It does that, but I am unsure whether the configuration file works, and I don't really know how to check. The codex* entries in keychain are back since I logged in on the Codex app. Kind regards
Topic: Developer Tools & Services SubTopic: Xcode
Replies
Boosts
Views
Activity
7h
CloudKit container in a broken state
I'm a first time developer, relying heavily on Claude Agent. In my app, I'm using CloudKit to sync data between devices, but after a migration something got corrupted and syncing is no longer working. I'm using SwiftData with NSPersistentCloudKitContainer. I'm using Xcode 26.4.1 on a Mac mini. I'm testing my app on the same Mac mini, running Tahoe 26.4.1 as well as an iPad 12.9 running iPadOS 26.3.1 and an iPhone running iOS 18.7.8. Sync stopped after a cachedTotal property was added to a SwiftData model, which triggered a backfill migration that wrote to all records simultaneously across multiple devices. This was followed by an iCloud sign-out/sign-in on the Mac. Here’s a summary of everything I’ve tried already: Reset All Data on all devices multiple times Deleted and reinstalled the app on all devices Deleted the CloudKit zone twice Force-deleted local SQLite store files to clear change tokens Zone and subscription both appear correct in the dashboard Change token updates when data is written (co
Topic: App & System Services SubTopic: iCloud & Data Tags:
Replies
2
Boosts
0
Views
109
Activity
8h
Reply to Sending 'geoRegion' risks causing data races
[quote='887247022, Etresoft, /thread/825634?answerId=887247022#887247022, /profile/Etresoft'] Most Apple APIs, with very few exceptions … should only be called on the main thread. [/quote] I don’t agree with that summary. Ignoring Swift concurrency, I generally group Apple’s Cocoa APIs into four categories: Main thread — These are limited to the main thread, with occasional exceptions. The canonical example of this is AppKit. Thread safe — These have internal locking and can be used from any thread. A good example is NSOperationQueue. Thread or queue confined — These must be used from a specific thread (or queue) that’s not necessarily the main thread (or queue). NSRunLoop is a good example of this. Serialisation required — These have no internal locking but can be used from arbitrary threads as long as you serialise that access. A good example is NSMutableDictionary. Your summary doesn’t include the last two categories, and IME that’s the biggest group of traditional Cocoa APIs. Unfortunately it’s hard to di
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
8h
notarytool submissions stuck "In Progress" indefinitely — account-specific issue?
Hello, I've been trying to notarize my macOS app using xcrun notarytool, but all submissions get stuck in In Progress status indefinitely (30+ minutes, never resolve). Environment: Tool: xcrun notarytool (Xcode 16) Bundle ID: io.pix-cull.app Team ID: C473MUK7G2 App type: PyInstaller-built .app, wrapped in a signed .dmg Stuck submission IDs: 00e953da (first attempt) f7ab027e 3e35fc3f 293541bc-ba61-4ccb-a273-a8f34cda2422 (most recent) Steps I've already taken: Disabled UPX compression in PyInstaller spec Signed all binaries inside-out (deepest first, .app last) Used --timestamp flag during codesign Verified Apple system status — all services show green Waited 24+ hours on the oldest submission — still In Progress What I observe: Running xcrun notarytool info returns status: In Progress every time, no matter how long I wait. The submission never transitions to Accepted or Invalid. Other developers report notarization completing in 2–15 minutes. I also submitted a ticket to Apple Developer Support (DTS)
Topic: Code Signing SubTopic: Notarization
Replies
1
Boosts
0
Views
68
Activity
10h
com.apple.developer.automatic-assessment-configuration entitlement missing from manually downloaded Distribution/InHouse Provisioning Profile
We are implementing an exam mode feature for an educational app used in schools, which restricts device usage during assessments. We requested the Automatic Assessment Configuration capability, received approval from Apple, and confirmed that the capability is listed as Assigned under our App ID in the Apple Developer portal. What works: When using a Development Provisioning Profile (downloaded from the portal), the entitlement key com.apple.developer.automatic-assessment-configuration is included in the profile, and our exam lock feature works correctly in development testing. The problem: When we manually download a Distribution (InHouse/Enterprise) Provisioning Profile from the portal — even after creating a new one — the entitlement key com.apple.developer.automatic-assessment-configuration is not present in the profile. verified this by running: security cms -D -i YourProfile.mobileprovision The key appears in the Development PP but is absent in the manually downloaded Distribution PP, despite the App ID
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
1
Boosts
0
Views
82
Activity
10h