“xcode github”

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?

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 🤷🏻

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.

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

[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

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

[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

Hi, thank you again. We were unable to reproduce this on our end with Xcode 26.4.1 and Codex 0.129.0-alpha.9, so it may be something specific to your configuration. Could you navigate to Xcode Settings → Components → Other Components → Codex and check the version listed there? It should read 0.129.0-alpha.9. If it shows a different version or indicates an update is available, try deleting it and redownloading the agent executable, then attempt signing in again. Let us know if that resolves the issue or if you're still seeing the login loop afterward, and we can dig deeper from there.

Thank you for your post. Are you encountering the issue with the RC 26.5? I think I have seen that issue with previous version where the tokens getting stuck in your Keychain. Ensure you are actively connected without VPN or proxies. As requires a stable connection to internal services to validate the token. If your network connection dropped briefly during the auth handoff, it will fail silently and leave you in the Not Signed In state. Also can you delete any cache? In your terminal: rm -rf ~/Library/Caches/com.apple.dt.Xcode If the issue persists please let me know and we can file a bug to see the issue in Xcode 25.6 RC. Albert
  Worldwide Developer Relations.

Unmodified code from here https://developer.apple.com/documentation/visionos/playing-spatial-audio-in-visionos I am not mirroring my screen. No sound connected to Xcode and I get the error in the log. No sound if my VisionPro is not connected to Xcode. I have a Gen 1 Vision Pro and using Xcode 26.4.1