Store FileParams properly for inbound Jingle

Stephen Paul Weber created 3 years ago

Change summary

src/main/java/eu/siacs/conversations/xmpp/jingle/JingleFileTransferConnection.java | 5 
1 file changed, 3 insertions(+), 2 deletions(-)

Detailed changes

src/main/java/eu/siacs/conversations/xmpp/jingle/JingleFileTransferConnection.java

@@ -507,7 +507,9 @@ public class JingleFileTransferConnection extends AbstractJingleConnection imple
                     xmppConnectionService.getFileBackend().setupRelativeFilePath(message,message.getUuid() + (extension.main != null ? ("." + extension.main) : ""));
                 }
                 long size = parseLong(fileSize, 0);
-                message.setBody(Long.toString(size));
+                Message.FileParams fp = new Message.FileParams();
+                fp.size = new Long(size);
+                message.setFileParams(fp);
                 conversation.add(message);
                 jingleConnectionManager.updateConversationUi(true);
                 this.file = this.xmppConnectionService.getFileBackend().getFile(message, false);
@@ -522,7 +524,6 @@ public class JingleFileTransferConnection extends AbstractJingleConnection imple
                         Log.d(Config.LOGTAG, "could not process KeyTransportMessage");
                     }
                 }
-                message.resetFileParams();
                 //legacy OMEMO encrypted file transfers reported the file size after encryption
                 //JET reports the plain text size. however lower levels of our receiving code still
                 //expect the cipher text size. so we just + 16 bytes (auth tag size) here