adium/adium

#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.
adium-1.5.3
2012-07-25, Thijs Alkemade
d8b4d0dcc831
Parents c9f0ada1220d
Children 1e2b55610208
#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 files changed, 6 insertions(+), 0 deletions(-)
  • +6 -0
    Plugins/Send Message Contact Alert/ESSendMessageContactAlertPlugin.m
    • --- a/Plugins/Send Message Contact Alert/ESSendMessageContactAlertPlugin.m Wed Jul 25 01:08:29 2012 +0200
    +++ b/Plugins/Send Message Contact Alert/ESSendMessageContactAlertPlugin.m Wed Jul 25 01:21:46 2012 +0200
    @@ -128,6 +128,12 @@
    UID:contact.UID];
    }
    + /* I'm also not sure how this can occur. Apparently the contact corresponding to the destUniqueID was a
    + * meta-contact, and it had no subcontacts on account.service. Probably a broken (empty?) meta-contact
    + * or an inconsistent offline message. (#15787)
    + */
    + if (!contact) return FALSE;
    +
    //If the desired account is not available for sending, ask Adium for the best available account
    if (![account availableForSendingContentType:CONTENT_MESSAGE_TYPE
    toContact:contact]) {