I've been researching #98 a bit and found that we have these null checks everywhere we trying to get message.getBody. Smack seems to be sometimes using these "messages" to signal about various non-message events, so we need to filter that shit.
I wasn't able to reproduce the bug (because it's triggered by some specific XMPP messages we're still not aware about), but I am pretty confident that's the core reason. Just filter these nasty nulls on the outer side of our API.
I've been researching #98 a bit and found that we have these
null
checks everywhere we trying to getmessage.getBody
. Smack seems to be sometimes using these "messages" to signal about various non-message events, so we need to filter that shit.I wasn't able to reproduce the bug (because it's triggered by some specific XMPP messages we're still not aware about), but I am pretty confident that's the core reason. Just filter these nasty
null
s on the outer side of our API.Closes #98.