David Smith

Ran into a weird data consistency bug today, where certain step count badges weren't updating correctly when the user changed their step goal. Took me about 10 minutes of poking around, breakpointing and on device testing to find that it was a bad `Equatable` implementation which was tripping up the updater.

Reverted my fix and asked Codex in Xcode 26.3 to give it a try. About 1 minute later it came up with the same fix.

Wild stuff.

Feb 5 at 8:43pmIvory for Mac
Show threadTormodFeb 5

@_Davidsmith

”Honey, those darn step count badgers are at it again.”

🦡🦡🦡🦡🦡

Show threadDennis BirchFeb 6
@_Davidsmith I’ve been burned by this a few times. Unfortunately it has been months apart each time, so I forgot in each instance that my == functions need to be updated anytime I add a property to a type.
Show threadartjulianFeb 6
@_Davidsmith especially for edge case bugs like this, it’s incredible. If it doesn’t find the solution, having to explain it just makes all the difference