Xcode 26.4.1
Fixed crash for MetricKit apps built with Xcode 26.4 due to missing symbols when running on iOS, macOS, and visionOS versions below 26.4.
[…]
Fixed stack-allocation bugs in async functions that caused “freed pointer was not the last allocation” crashes, particularly in
swift_asyncLet_finish. These long-standing issues became more frequent in Swift 6.2 and 6.3 due to optimizer improvements.
I’m currently learning SwiftUI.
26.4 preview windows don’t let you scroll or swipe. Crashes & requires an Xcode restart.
Seems like this kind of stuff is, if not the norm, then at least common enough where the general response is “welcome to iOS development, here’s a cookie”.
Xcode loses my Apple Accounts again and again!! WTF? It also happens on the CI server… SO annoying!
And it doesn’t even has a Passwords.app integration!! 🤬
notarization failing today because of new Paid App terms. i don’t have any paid apps but still have to agree to get notarization working.
took me 90min to sign in. dev ID was “Locked for Security Reasons” — it always is.
unlock fails in Chrome, “The action could not be completed”. in safari the captcha doesn’t show.
but unlock works on my phone.
the it says, “Reset your password?” but it didn’t. it just unlocked the account — the text in the alert was just wrong.
Every month or so, I have to open Xcode, and every time I’m surprised at how it can’t do basic things. Xcode can’t find a call hierarchy for a local function declaration. It just beeps at me.
It’s been 10 years or so since Jump to Definition and Jump to Next Counterpart worked consistently for me. Often, I just get beeps or nothing happens.
Previously:
Update (2026-04-21): Der Teilweise:
Someone at Apple sat at their keyboard and wrote this error message for Xcode.
Maybe replacing devs with an AI tool is a step forward in some cases.
I’m not even starting to talk about the fact that the alert looks like it is disabled/in the background but is not.
And the tiny OK button.
Update (2026-04-29): Christian Beer:
Is anybody else using Xcode to run unit tests? Is it just me or do you also have the following problems:
- test navigator not showing the results
- build errors are not shown in toolbar
- I can’t get from the test results to the code …
Yeah but… have you actually tried using SwiftUI previews? Maybe it’s ok on iOS but for Mac I’ve found it completely non functional.
Update (2026-05-04): Der Teilweise:
“IF THIS IS UNEXPECTED, PLEASE FILE A BUG REPORT.”
If that’s not what a dev screaming for help against management looks like, I don’t know what is.
It would be great if Xcode was decoupled from operating system versions. I'm not convinced a compiler benefits from glassy user interfaces.
(I know the real reasons, but I'm annoyed at those thin reasons).
6 Comments RSS · Twitter · Mastodon
> It’s been 10 years or so since Jump to Definition and Jump to Next Counterpart worked consistently for me. Often, I just get beeps or nothing happens.
Broke with the introduction of Swift, it seems. Still works fairly well in ObjC. More recently I sometimes have to Command+B to force a build to complete to get it to work. Same with the generated Documentation.
It either is gradually getting worse slowly all around or my project has grown to the point where I notice these little issues more. In Swift...Jump to Def almost never worked every time I tried which was frustrating when you are reading someone else's code because of type inference.
I do most of my paid macOS development with Qt using Qt Creator, and I feel very lucky to not have to regularly work with Xcode.
> It’s been 10 years or so since Jump to Definition and Jump to Next Counterpart worked consistently for me
Works ok for me with C and Obj-C, but with C++ and Obj-C++ it works less well, but not abysmally.
„Funny“ thing is that Jump to Definition nearly never works, but Quick Open shows the symbol immediately. Why isn‘t that working the same?!
