Since we(Jitsi) upgraded to Smack 4.4 we got multiple reports from the community that destroying a room is broken and one of our serverside components does not detect it.
We tracked it down to https://github.com/igniterealtime/Smack/commit/0f7b7df1f0cd6a3d2f75a983143d02fda8990111
Even though the XEP does not mention anything about the status in the x element for the destroy presence, we think that handling of the presence unavailable should be tolerant process those messages if there is a status or not.
The incoming message is:
<presence xmlns='jabber:client' xml:lang='en' email@example.com/focus' firstname.lastname@example.org/focus' type='unavailable'> <x xmlns='http://jabber.org/protocol/muc#user'> <item affiliation='owner' email@example.com/focus' role='none'></item> <status code='110'/> <destroy></destroy> </x> </presence>
and Smack ignores it, which was not the case running with Smack 4.2.