Can this be avoided by disabling iMessage notifications?
> The calling method then calls -[IMBalloonPluginDataSource _replaceHandleWithContactNameInString:] which calls im_handleIdentifiers on the 'NSString' which is really an NSNumber, which throws an exception as the selector does not exist in that class.
Looks like they need to move more of their stuff to Swift to reduce snarfles like this.
Stories like these (this isn't the first time that iOS/macOS could be crashed by chat messages), and the empty root password debacle, or all the GateKeeper bypasses, make me wonder if their engineers take their own WWDC security-related talks seriously.
Still, it's not so bad as the Windows XP-7 epoch, when eldritch nightmares walked the land.
> The calling method then calls -[IMBalloonPluginDataSource _replaceHandleWithContactNameInString:] which calls im_handleIdentifiers on the 'NSString' which is really an NSNumber, which throws an exception as the selector does not exist in that class.
Looks like they need to move more of their stuff to Swift to reduce snarfles like this.
Stories like these (this isn't the first time that iOS/macOS could be crashed by chat messages), and the empty root password debacle, or all the GateKeeper bypasses, make me wonder if their engineers take their own WWDC security-related talks seriously.
Still, it's not so bad as the Windows XP-7 epoch, when eldritch nightmares walked the land.