Craig Hockenberry
Apple needs to go back to the drawing board with these alerts in Sonoma. They are scary, frequent, and not actionable.
It's like an engine check light going on, taking the car to the mechanic, and having them say “I have no fucking idea what's wrong”.
What's worse, is that they only appear once with no apparent way to reset. That makes it impossible for a developer to verify that they fixed the deprecated API usage.
It's also not a good look that these are happening in System frameworks.
Craig Hockenberry
(replying to Craig Hockenberry)
If you're as confused as I am about the new deprecation alerts in Sonoma, read this (it's a lot worse than you think).
And make sure to dupe the FB (see NOTE at the bottom of the blog post). We have to let Apple know they're screwing up in a big way.
shac ron ₪
(replying to Craig Hockenberry)
@chockenberry This feels like something for betas that’s not intended for release. It’s a way to make developers who are testing their apps without recompiling aware that some API they are depending on has become deprecated since it was built.
shac ron ₪
(replying to Saagar Jha)
@saagar @chockenberry I’m guessing it’s a simple patch of the dynamic linking tables to call this, which is why it doesn’t know what the offending function is. Could definitely be done better.