Smack v4.2.1 Release Notes

Release Date: 2017-08-14 // over 6 years ago
  • ๐Ÿ› Bug

    • SMACK-749 - SCRAM-SHA-1 and SCRAM-SHA-1-PLUS SASL mechanisms have the same priority, causing SASL authentication failures
    • SMACK-755 - DIGEST-MD5 sometimes causes malformed request server response
    • SMACK-756 - IoTIsFriendResponse has invalid name and produces invalid XML
    • SMACK-759 - PubSubManager.getLeafNode() throws PubSubAssertionError.DiscoInfoNodeAssertionError if node exists but its not a PubSub Node
    • SMACK-764 - NPE in hashCode() in Occupant when jid is null
    • SMACK-766 - Smack possibly includes \'ask\' attribute in roster items when sending requests
    • SMACK-768 - Smack throws NoResponse timeout when waiting for IQ although there was a response
    • SMACK-771 - XMPPTCPConnection should use KeyManagerFactory.getDefaultAlgorithm() instead of KeyManagerFactory.getInstance(\"sunX509\");
    • SMACK-772 - HostAddress must deal with \'fqdn\' being null.
    • SMACK-773 - Allow roster pushes from our full JID for backwards compatibility
    • SMACK-774 - HTTP File Upload\'s SlotRequest metadata should be attributes not child elements

    ๐Ÿ†• New Feature

    • SMACK-746 - Add support for XEP-0380: Explicit Message Encryption
    • SMACK-758 - Add support for XEP-0334: Message Processing Hints
    • SMACK-760 - Smack does not allow custom extension elements in SM\'s <failed/>

    ๐Ÿ‘Œ Improvement

    • SMACK-752 - XEP-0357 Push Notification enable IQ uses wrong form type: Should be \'submit\' instead of \'form\'
    • SMACK-754 - Allow MUC room subject changes from the MUCs bare JID
    • SMACK-777 - MamManager should use the user\'s bare JID to check if MAM is supported