#15787 seems to still occur. Trying to avoid the only way I see this function can still fail and throw and exception, though I don't really know how Adium can come into this inconsistent state.
Refs #15787
1.1 --- a/Plugins/Send Message Contact Alert/ESSendMessageContactAlertPlugin.m Wed Jul 25 01:08:29 2012 +0200
1.2 +++ b/Plugins/Send Message Contact Alert/ESSendMessageContactAlertPlugin.m Wed Jul 25 01:21:46 2012 +0200
1.3 @@ -128,6 +128,12 @@
1.4 UID:contact.UID];
1.5 }
1.6
1.7 + /* I'm also not sure how this can occur. Apparently the contact corresponding to the destUniqueID was a
1.8 + * meta-contact, and it had no subcontacts on account.service. Probably a broken (empty?) meta-contact
1.9 + * or an inconsistent offline message. (#15787)
1.10 + */
1.11 + if (!contact) return FALSE;
1.12 +
1.13 //If the desired account is not available for sending, ask Adium for the best available account
1.14 if (![account availableForSendingContentType:CONTENT_MESSAGE_TYPE
1.15 toContact:contact]) {