size of msg file is getting as 0.

[ReddyBhargavi18]

When an msg filed added size of the file is getting as 0 we are unable to get the correct content of the msg file.

Your Environment

• Platform: PC desktop, Mac, iOS, Office on the web
• Host: Outlook
• Browser (if using Office on the web): Edge and chrome

Expected behavior

1.Open new mail
2.Add an msg > get the details of msg file using the getAttachmentsAsync.
3.Need to get the exact size and the content.

Current behavior

1.Open new mail
2.Add an msg > get the details of msg file using the getAttachmentsAsync.
3.The size of file is 0 and the content also corrupted.

Useful logs

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Behavior of getAttachmentsAsync to get msg file is different between OWA and desktop version. #4550
• Attachment name is getting incorrectly from the getAttachmentsAsync function #6362
• Accatment name is getting incorrectly from the getAttachmentsAsync function. #6361

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Looking a little more closely at your code sample, I realize that you are trying to use localstorage in a launch event. In Win32 launch events run in a JS runtime and don't have browser things like localstorage whereas when you are running the add-in in OWA there are browser features available to you. This has nothing to do with the getAttachmentsAsync itself, but rather how you are trying to use it. You should look at the asyncResult object directly in the callback to do anything with the attachments.

see: https://learn.microsoft.com/en-us/javascript/api/outlook/office.appointmentcompose?view=outlook-js-preview&preserve-view=true#outlook-office-appointmentcompose-getattachmentsasync-member(1)

Reference:

• Behavior of getAttachmentsAsync to get msg file is different between OWA and desktop version. #4550 (comment)

Solution 2:

Upon further inspection, it looks like you are using the old 'ItemSend' event and not the new 'launch events'. The older event runs slower but does use the HTML sandbox, so those extra things are available (even if they do complicate the code).

Trying out the API in a simple taskpane scenario reproduces the issues with .msg files specifically in a compose window that hasn't been saved and re-opened (either through sending or saving as draft). We'll look into fixing this, but we cannot comment on a timeline.

internal tracking id: 9217103

Reference:

• Behavior of getAttachmentsAsync to get msg file is different between OWA and desktop version. #4550 (comment)

Powered by issue-sentinel