This blog post is a follow-up to How to fix the disastrous new Xcode 15 console, which was itself a follow-up to Xcode 15 logs nil as an empty string, not (null). I mentioned in the previous blog post that I filed three bugs with Apple, one of which was FB13289059 "Xcode 15 console logs truncated". Since then I've had some back and forth with Apple on that bug in Feedback Assistant. I'm going to screenshot the entire exchange below. For context, if you're not familiar with Apple's bug reporting system, they constantly ask developers to "Please verify this issue" with the latest betas, despite having done nothing to fix the issue in the latest betas, in the hope that the issue (or maybe the developer) will magically go away. In my many years of filing bugs with Apple, the issue almost never magically goes away in the latest betas.
The ultimate outcome of this case was that Apple blatantly lied to me—"As you’ve indicated, this issue is resolved"—and then Apple refused to hear any contradiction to their lie—"this Feedback will no longer be monitored, and incoming messages will not be reviewed." This kind of response reinforces what I said earlier in the exchange: "It makes me not want to file feedbacks at all. It feels like you don't care." The coup de grâce was "We appreciate your feedback." No, Apple absolutely does not appreciate our feedback.
Anyway, apparently this particular issue is fixed in macOS Sonoma, which doesn't help me at all, since I'm still using Ventura. And the reason I'm avoiding Sonoma is that it's buggy. I've also filed some Sonoma bugs with Apple, for example, FB13215060 "Sonoma wants me to Verify Your Recovery Key". Ever since the first macOS 14 and iOS 17 betas, I've seen a number of Apple ID related bugs (crashes, hangs, etc.), which scare me away from installing Sonoma on my MacBook Pro, my main development machine (as opposed to my Mac mini, which I use solely for testing various macOS versions).