Please try 4.1.0-rc3-SNAPSHOT
Will do.
Can you put the right to run the code?I also encountered such a problem, thank you very much!
Try 4.1.0-rc4-SNAPSHOT
Sorry to hijack this thread, but I am facing a similar problem with incoming file transfer. So, posting here.
I am using 4.1.0(also tried 4.1.1).
On attempting an incoming file transfer, getting a ExecutionException. This is the output of exception.getcause()
06-09 16:39:21.342 18322-18338/com.mol.android.chat W/System.errīš org.jivesoftware.smack.XMPPException$XMPPErrorException: Could not establish socket with any provided host
06-09 16:39:21.346 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.bytestreams.socks5.Socks5BytestreamRequest.cancelRequest(Socks5BytestreamRequest.java:286)
06-09 16:39:21.347 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.bytestreams.socks5.Socks5BytestreamRequest.accept(Socks5BytestreamRequest.java:255)
06-09 16:39:21.348 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.Socks5TransferNegotiator.negotiateIncomingStream(Socks5TransferNegotiator.java:104)
06-09 16:39:21.349 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.FaultTolerantNegotiator.createIncomingStream(FaultTolerantNegotiator.java:68)
06-09 16:39:21.350 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$2.call(IncomingFileTransfer.java:187)
06-09 16:39:21.351 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$2.call(IncomingFileTransfer.java:183)
06-09 16:39:21.352 18322-18338/com.mol.android.chat W/System.errīš at java.util.concurrent.FutureTask.run(FutureTask.java:237)
06-09 16:39:21.353 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.negotiateStream(IncomingFileTransfer.java:190)
06-09 16:39:21.353 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer.access$100(IncomingFileTransfer.java:57)
06-09 16:39:21.355 18322-18338/com.mol.android.chat W/System.errīš at org.jivesoftware.smackx.filetransfer.IncomingFileTransfer$1.run(IncomingFileTransfer.java:129)
06-09 16:39:21.355 18322-18338/com.mol.android.chat W/System.errīš at java.lang.Thread.run(Thread.java:841)
Am I using the right library version?
Hello, mates!
Iâm working with smack 4.1.1 for android application
My connection settings looks like
mConnection.setUseStreamManagement(true);
mConnection.addConnectionListener(mXmppConnectionListener);
mConnection.addAsyncStanzaListener(mXmppMessageListener, XmppMessageListener.FILTER);
ServiceDiscoveryManager mDisco = ServiceDiscoveryManager.getInstanceFor(mConnection);
mDisco.addFeature(DeliveryReceipt.NAMESPACE);
mDisco.addFeature(DiscoverInfo.NAMESPACE);
DeliveryReceiptManager mDeliveryReceiptManager = DeliveryReceiptManager.getInstanceFor(mConnection);
mDeliveryReceiptManager.setAutoReceiptMode(DeliveryReceiptManager.AutoReceiptMod e.always);
mDeliveryReceiptManager.autoAddDeliveryReceiptRequests();
PingManager.getInstanceFor(mConnection).setPingInterval(180);
ReconnectionManager.getInstanceFor(mConnection).setReconnectionPolicy(Reconnecti onManager.ReconnectionPolicy.RANDOM_INCREASING_DELAY);
FileTransferNegotiator.getInstanceFor(mConnection);
mFileTransferManager = FileTransferManager.getInstanceFor(mConnection);
mFileTransferManager.addFileTransferListener(mFileTransferListener);
File transfer works perfectly until one of devices change network connectivity (3g | 4g | wi-fi) or reconnect to xmpp server.
Error messages are
SENT (0): OutgoingFileTransferhttp://jabber.org/protocol/bytestreamshttp://jabber.org/protocol/ibb
RECV (0): http://jabber.org/protocol/bytestreamshttp://jabber.org/protocol/ibb
SENT (0):
RECV (0):
SENT (0):
RECV (0):
SENT (0):
RECV (0):
SENT (0):
RECV (0):
SENT (0):
RECV (0):
SENT (0): <query xmlns='http://jabber.org/protocol/bytestreamsâ/>
RECV (0):
SENT (0):
RECV (0):
SENT (0):
RECV (0):
RECV (0):
Can someone point me how to fix this issue?
ok, release 4.1.2 fixes this issue