@sethwillits

Will write code for racing drive.

 Anaheim Hills, CA
sethwillits.com/
Joined July 2008
  • Tweets1.5K
  • Following98
  • Followers190
31Media
Found a bug in NSKeyedUnarchiver secure decoding of an NSAttributedString that causes the whole decode to fail with an absolutely dead-wrong error message. It's preventing me from using secure coding. Anybody know any Foundation engineers? >_>
2
1
680
"Apple repair kits for Mac Studio and the Studio Display can be rented for $49…" Who's going to try to fix the annoying high pitched whine first?
301
Spent 3 hours today trying to debug an NSBox layout constraint problem. It turns out I had "Autoresizes Subviews" turned off which was making AppKit install a fixed-width constraint at runtime which broke all expectations. Super confusing.
1
4
Oh hello there #wwdc 2004
Updated all the errors on osstatus.com to those in the SDKs with Xcode 14.
1
1
1
15
Hey, fellow Mac developers: Don't forget that tooltips exist. Just sayin'.
2
If all of the macOS bugs I've founded had payouts 1/10th of those in the "Apple Security Bounty" program, I'd be making bank without even shipping anything. I'd settle for just having timely responses to my bug reports though.
1
1
Hot take: My theory is that NSMenu is a little too limited in its customization capabilities. I've run into it now and then. Ex: As soon as a menu item has a view, it's no longer a clickable/selectable item like the others. Sometimes want it to be. 1/…
1
1
more replies
I feel grouping & spacing are wanted additions. I've been experimenting with this in my apps. I would have to really take inventory of examples, but I would like to see a more robust API that's more flexible with layout but can still respond to / act with menu behavior. 3/3
1
But all in all, yes… a popover masquerading as a menu is a terrible thing. Crazy that they did it.
2
Audio recording from my Apple Studio Display microphone is still fundamentally broken in every app. Latest OS and display firmware versions.
2
And for what it's worth, I filed this back in May as FB10017937. No response from Apple yet.
1
So far it appears that the recent Studio Display Firmware Update 15.5 (19F80) did fix the audio issues for me. Great! Now, am I the only one who is getting windows resized to 1920x1080 whenever the display sleeps? Can we get a fix for that too?
1
1
EEK! The new "ips" crash reports in macOS do not contain assert() information! (Assertion failed: (myVar != nil), function fooBarTest(), file code.m, line 100) Problematic because symbolication is often finicky, so it takes a LOT more work to find which assert() failed.
1
2
This is true on macOS 12 and macOS 13. I don't know whether it's the "log" that's to blame or that the "___crashreporter_info__" symbol is no longer supported, but even manually writing to it doesn't show up in the log anymore. It's not a problem with assert() itself.
1
1
Anyone else's Apple Studio Display mic not work *at all*? Mac Studio, everything updated, no system plugins… It shows up, but everything fails to capture audio from it. Errors or silence. Even System Prefs doesn't show any audio level.
1
1
Mmmm… even plugging an external mic into this Mac Studio briefly works, then the system stops capturing new audio from it, and it's just looping on its existing audio buffer. Somewhat comically, it's currently looping a clip of me making an audible groan of frustration.
1
Is anyone else with a new Mac Studio + Studio Display seeing windows move and resize to fit a 1080p resolution area when the display goes to sleep? It only happens to *some* windows, *some* of the time, but overall it's happening often. #apple #macstudio
1
My favorite kind of work… figuring out mysterious private error codes and behavior in AVFoundation and MediaToolbox. Currently, -16356. Separately, AVAssetWriter, samples inserted, finishes correctly, no errors, but the file is 0 bytes when done. Sigh.
1
Load more