Hello,
I have started using your application for a project I'm working on, however i noticed that when saving docx files that they do not open correctly. docx seems to be the only file type affected but the issue runs deeper.
Upon investigation i discovered that when you read the base64 encoded string from the source, there are blank characters on the end of the string, which are then decoded which produce a file which is not entirely what was sent. In my case, the docx file had 2 extra NULL characters on the end of the binary file.
To fix this, you need to simply call .Trim() on the string, in the appropriate place, which i think may be around line 307-310 in MessageContent.cs when the message is downloaded. However i might be incorrect.
I hope this has helped you and thank you very much for making this application in the first place, and also, apologies if this has already been flagged
Thanks
Jamie
I have started using your application for a project I'm working on, however i noticed that when saving docx files that they do not open correctly. docx seems to be the only file type affected but the issue runs deeper.
Upon investigation i discovered that when you read the base64 encoded string from the source, there are blank characters on the end of the string, which are then decoded which produce a file which is not entirely what was sent. In my case, the docx file had 2 extra NULL characters on the end of the binary file.
To fix this, you need to simply call .Trim() on the string, in the appropriate place, which i think may be around line 307-310 in MessageContent.cs when the message is downloaded. However i might be incorrect.
I hope this has helped you and thank you very much for making this application in the first place, and also, apologies if this has already been flagged
Thanks
Jamie