How did you disable Socks5BytestreamManager? Try SmackConfiguration.addDisabledSmackClass(“org.jivesoftware.smackx.bytestreams.s ock5”) in a static block before performing any XMPP operations.
I used disableService(). But also with
static
{
SmackConfiguration.addDisabledSmackClass(“org.jivesoftware.smackx.bytestreams.sock5”);
}
or
SmackConfiguration.addDisabledSmackClass(Socks5BytestreamManager.class);
presence is still sent:
D/SMACK﹕ SENT (0): cff14d05677693aba11e280e27ebd5e9af6aaea0</ph oto>
But I also still get the manager returned…
Socks5BytestreamManager s5bm = Socks5BytestreamManager.getBytestreamManager(m_connection);
But I also still get the manager returned…
addDisabledsmackClass just prevents the class from getting initialized by Smack when Smack is initialized. It does not forbid to later retrieve the manager.