Codex will no longer be available in Xcode 26.3 starting on Friday, May 8th. Please upgrade to Xcode 26.4 or later to continue using Codex.

For a couple of months now I haven't been able to see new crash reports for my App Store apps in Xcode. I see the list of crash reports in the Organizer, but selecting any of the new ones always shows the same error message: Error Downloading Crash Log Information: An error occurred preventing Xcode from downloading crash log information. "my.email at domain.com" failed with error: There was a failure decoding response: (HTTP 500, 20364 bytes) The data couldn't be read because it isn't in the correct format.. Pushing the Reload button makes the view load for a bit, but then the same error appears again. Since I want to keep fixing crashes in my apps as fast as possible, is Apple aware of the issue and working on a fix? I don't know if this is a Xcode or App Store Connect issue. I would have expected this issue to be fixed with the newest Xcode version 26.5, but it's still happening. I opened FB22589345 on April 23, but got no response so far.

Since a few days ago, I noticed that every time you go to the top of the text in the Agentic Coding chat box, if you keep pressing the up arrow, the current message is replaced by the previous one. It's like someone decided to allow users to use the arrows to navigate to previous conversations in the same context, but this means that you are constantly jumping to previous messages by accident. The "feature" is error prone, confusing, and extremely annoying. If someone knows of an option in setting to disable it, please let me know. I'm constantly making mistakes, wasting tokens, editing the wrong message, and making the conversation confusing by sending the wrong message to the agent.

When working with an Objective-C project in Xcode 26.5, I'm unable to establish outlet and action connections by dragging between XIB files and the corresponding .h header files. This drag-and-drop connection works perfectly after switching to Xcode 26.3.0. In addition, under Xcode 26.5, drag-and-drop linking works normally for projects using Swift files together with XIB files. The issue only occurs with Objective-C .h files and XIB files.

When I submit an https web request I receive both of those funny errors. In particular I do not understand what that “Sectigo Public Server Authentication” message represents, perhaps yet another certification for Apple to access the request, when of course by connecting to that web address on Safari produces no errors. Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 1; } urlstring=https://taxiprofessional.net/***.php process loading tcp_input [C2.1.1.1:3] flags=[R] seq=2572529641, ack=2572529641, win=251 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 tcp_input [C2.1.1.1:3] flags=[R] seq=2572535079, ack=2572535079, win=1981 state=ESTABLISHED rcv_nxt=2572535079, snd_una=3494441675 nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate)] already failing, returning nw_endpoint_flow_failed_with_error [C2.1.1.1 82.223.15.117:443 cancelled channel-flow ((null))] already failing, returning Connection 2: received failure notification Connection 2: received ECONNRESET with incomplete TLS handshake - generating errSSLClosedNoNotify Connection 2: failed to connect 3:-9816, reason -1 Connection 2: encountered error(3:-9816) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> HTTP load failed, 0/0 bytes (error code: -1200 [3:-9816]) Task <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1> finished with error [-1200] Error Domain=NSURLErrorDomain Code=-1200 "Connessione sicura non riuscita a causa di un errore TLS." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrustRef: 0x121bd4240>, NSErrorFailingURLKey=https://taxiprofessional.net/...php, NSErrorFailingURLStringKey=https://taxiprofessional.net/....php, NSErrorClientCertificateStateKey=0, NSErrorPeerCertificateChainKey=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=( "LocalDataTask <7879BCCC-47A3-44C8-A74A-560231AA4AE5>.<1>" ), NSLocalizedDescription=Connessione sicura non riuscita a causa di un errore TLS., _kCFStreamErrorDomainKey=3, NSUnderlyingError=0x121b7b0c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "(null)" UserInfo={_kCFNetworkCFStreamSSLErrorOriginalValue=-9816, kCFStreamPropertySSLPeerCertificates=( "<cert(0x11bfcca00) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x121a27200) s: *.taxiprofessional.net i: Sectigo Public Server Authentication CA DV R36>", "<cert(0x122dac000) s: Sectigo Public Server Authentication CA DV R36 i: Sectigo Public Server Authentication Root R46>" ), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrustRef: 0x121bd4240>, _NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: pdp_ip0[lte], ipv4, dns, expensive, uses cell, LQM: moderate, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=-9816}}, _kCFStreamErrorCodeKey=-9816}

While testing Flutter applications on macOS 26 beta with Xcode 26 beta, iOS builds consistently fail during Flutter.framework codesigning with: "resource fork, Finder information, or similar detritus not allowed" Investigation suggests newer Xcode beta versions now reject additional extended attributes beyond com.apple.FinderInfo during codesigning. Flutter tooling currently removes only: xattr -r -d com.apple.FinderInfo Replacing it with: xattr -cr successfully resolves the issue. Environment: macOS 26.4.1 beta Xcode 26.4.1 beta Apple Silicon (ARM64) Flutter 3.41.9 Flutter issue: https://github.com/flutter/flutter/issues/186372 Apple Feedback Assistant report: FB22756923 Interested to know whether other developers on Xcode 26 beta are seeing similar stricter codesigning validation behavior.

In Xcode (26.4.1), when using Coding Assistant, in new project, one can reference files by @fileName, but it does not work for projects that have been created e.g. 8 months ago. How can I make the @fileName feature work for previous projects as well? Project it fails with (@ does not show any files from the Project Navigator, and when e.g. manually referencing the @fileName and then clicking on the file in the Coding Assistant chat, macOS shows): Project it works with (FriendsFavoriteMovies project from this tutorial: Navigate sample data | Apple Developer Documentation) I'd be very happy to know a solution to my question: How can I make the @fileName feature work for previous projects as well? Thank you very much, Tim :)

I tried every possible but it just won't work on my device. The program runs well on the simulator by the way

Xcode iig hangs. In the best case, the project will be in error - and Xcode cannot recover. To recover restarting Xcode may not help (force quit Xcode) - most of the time a restart of the Mac is required. Its speaks to software quality when "Clean build folder" is your best friend. Xcode iig hangs, and while its only using two of my MacStudio's 10 cores - the whole mac hangs (Activity monitor confirms, if it opens at all). If you are not quick enough to reboot the Mac will hang and require power down using power button. Don't use Finder to reboot because Finder hangs too and will not reboot - use terminal (sudo shutdown -r now). see screen dump below: super useful! After restart, Xode may refuse to launch. This is something I notice with my Java apps (jar launcher): If the app ends with an exit code (1, not 0 like normally) - it will not launch until I restart the Mac, in the meantime must launch the app from Eclipse. After restart, the crash reporter comes up - asking me to type a reason. When I type "iig" the auto-correct will change that to "big". This is so totally useful! MacOS 26.4.1 Xcode 26.3 apologies - its a lousy day when your Mac hangs and requires a restart - repeatedly; until I got my iig fixed up and Xcode fully aware with the actual content. iig error reporting is lousy; which makes fixing so extra hard.

I’m trying to build and run a brand-new Xcode project created from the Audio Unit Extension App template for local macOS development on a brand-new Mac, and I’m blocked by a signing/keychain issue. Environment: macOS on a brand-new Mac Xcode 26.4.1 Build version 17E202 Personal Team Targeting My Mac Project type: Audio Unit Extension App Main symptom: During build/run, Xcode repeatedly shows this prompt: codesign wants to access key "Apple Development: Sam Magnant (...)" in your keychain It asks for the login keychain password. Important detail My current Mac password successfully unlocks the login keychain manually in Keychain Access every time. So the issue seems specific to Xcode / codesign using the Apple Development private key, not a general inability to unlock the keychain. What I’ve already tried Reset the default keychain Logged out and back in after reset Changed my Mac account password to a new password Confirmed the login keychain unlocks manually with the current Mac password Deleted and recreated local Apple Development certificate/private key where possible Removed and re-added my Apple account in Xcode Checked the private key in Keychain Access Confirmed the private key exists under the Apple Development certificate Confirmed Allow all applications to access this item is already checked on the private key Removed App Groups and other extra capabilities to simplify the project Tried security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k '' ~/Library/Keychains/login.keychain-db Tried switching the project to simpler signing configurations, then switched back to standard Apple Development signing What’s confusing Xcode appears to know about an Apple Development certificate/private key Keychain Access shows the identity under login > My Certificates The login keychain unlocks fine manually But codesign still prompts, and the machine reports 0 valid identities found Questions What would cause Keychain Access to show the Apple Development identity, but security find-identity -v -p codesigning to report 0 valid identities found? Is this most likely a broken certificate/private key pairing, trust chain issue, or something specific to Personal Team signing? Is there a recommended way to fully repair the local Apple Development signing identity on the current macOS user account without creating a new macOS user? Are there known issues with the Audio Unit Extension App template and Personal Team local development on macOS?

I'm getting a static analysis warning on the following code. I don't think it could be my error, but I guess it's more likely a static analysis false positive than a C++ standard library bug. The warning says "Method called on moved-from object of type 'std::basic_string'". Tested in Xcode 26.5 RC. Reported as FB22735405. #include <algorithm> #include <string> #include <vector> #include <CoreFoundation/CoreFoundation.h> template < class traits = std::char_traits<char>, class Allocator = std::allocator<char> > struct UTF8StringLess { bool operator()( const std::basic_string<char, traits, Allocator>& inFirst, const std::basic_string<char, traits, Allocator>& inSecond ) const; }; template<class traits, class Allocator> inline bool UTF8StringLess<traits, Allocator>::operator()( const std::basic_string<char, traits, Allocator>& inFirst, const std::basic_string<char, traits, Allocator>& inSecond ) const { CFStringRef theFirst = ::CFStringCreateWithCString( nullptr, inFirst.c_str(), kCFStringEncodingUTF8 ); CFStringRef theSecond = ::CFStringCreateWithCString( nullptr, inSecond.c_str(), kCFStringEncodingUTF8 ); CFComparisonResult compResult = ::CFStringCompare( theFirst, theSecond, kCFCompareCaseInsensitive ); bool isLess = (compResult == kCFCompareLessThan); ::CFRelease( theFirst ); ::CFRelease( theSecond ); return isLess; } int main(int argc, const char * argv[]) { std::vector<std::string> names{ "obey", "Zorro", "can" }; std::sort( names.begin(), names.end(), UTF8StringLess() ); return EXIT_SUCCESS; }

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.

Hello, I’m encountering an issue retrieving crash reports from the AppStore Connect using Xcode 26.4.1 (17E202). I’m signed in with multiple Apple IDs, including the one required to fetch crashes. When I select the destination application and attempt to download crashes in Organizer, a small warning icon appears in the top right corner. Clicking on it displays the following error: "{AppleID email}" failed with error: There was a failure decoding response: (HTTP 500, 20364 bytes) The data couldn’t be read because it isn’t in the correct format.. I already tried to remove my account and sign in again multiple times and also restarted Xcode but nothing seems to work. I wonder whether this is some new bug introduced in the latest Xcode version or rather local issue on my machine. Any help appreciated.

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

It annoys me that Xcode keeps downloading Simulators automatically, even though I haven't asked for them. Under Settings > Components > Other Installed Platforms I see iOS Simulator iOS 18.0 uptil 18.5. These are eating space in /Library/Developer/CoreSimulator/Caches/dyld/25E253. Is there a way to prevent these automatic downloads?

I inherit from a protocol that implements in its extension those functions, that should not be required by the adopting class and instead I get those errors. Could someone explain why those errors appear and how to fix it.

Is there any solid documentation to get the controllers to work in my experience? I am having the hardest time figuring out how to get the controllers to work properly. I get them to work in the system, but within my project, they work, but inconsistent and some buttons will not register taps, grabs, grips, etc

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

I just noticed this but am curious: Why does Xcode use list.bullet SF Symbol to toggle the "navigators" (sidebar) instead of sidebar.left? For the inspectors Xcode uses "sidebar.right" but I don't understand why the left sidebar uses a different icon from the right sidebar? Shouldn't the left sidebar icon match the right sidebar (just flipped)? Am using the wrong SF Symbol in my app to toggle the sidebar? Is the list.bullet the recommended symbol for this now? Every other app seems to use sidebar.left.

We came across reports on Medium and Apple Developer Forums suggesting that ApplicationToken and ActivityCategoryToken values issued by the FamilyControls framework are not guaranteed to be stable, that iOS may silently re-issue new tokens for the same apps after OS or app updates, making any previously stored tokens invalid. We are storing FamilyActivitySelection tokens encoded via JSONEncoder to a backend for long-term use, and relying on them inside a DeviceActivityMonitorExtension to restore and apply shields when a schedule fires. What we're trying to understand is: is this token instability still an active problem in iOS 16/17/18/26, and when a token does become invalid, does JSONDecoder actually throw a DecodingError giving us a clear signal, or does it decode successfully and ManagedSettingsStore just silently ignore the stale tokens with no error at all? On Medium, We Found That The Token Mutation Problem One of the more painful bugs in real production apps: application tokens are not guaranteed to be stable forever. iOS can silently issue new, different tokens for the same app. If your store contains the old token and the Shield delegate receives a new one, the delegate has no way to match them — it doesn’t know which store is responsible for the shield, or which blocking “profile” caused it. This has been reported by multiple developers of real Screen Time apps and confirmed across several Apple Developer Forum threads. There is no official fix yet. The workaround is defensive: when the ShieldConfigurationDataSource or ShieldActionDelegate receives a token you don't recognise, fall back to a generic shield UI rather than crashing or returning empty data. And never rely on token identity as a long-term stable key in your persistence layer — always re-derive from a fresh FamilyActivityPicker selection when the user re-activates a profile.