Behavior of getAttachmentsAsync to get msg file is different between OWA and desktop version. about office-js

[akagarwa-msft]

Please confirm if it is old Oulook or new Outlook in windows? You can check through this toggle present in Outlook desktop on right hand side top corner:

Also, please share the repro video as we are not able to repro the issue at our end.

[mailchecktool-admin]

I am using the “old Outlook”.
I took a video in my local environment, check it out.
レコーディング-20240607_154855.webm

[mailchecktool-admin]

@akagarwa-msft
I have attached a reproduction video, have you checked it?
I look forward to hearing back from you as soon as possible.

[mailchecktool-admin]

@akagarwa-msft @exextoc
Have you had a chance to review the information I shared previously? If you're unable to replicate the issue, we can gather the necessary data and provide it to you. Please let us know the results of your investigation.

[millerds]

Sorry for the large delay in responding. Can you clarify what you are doing on the classic outlook rich client to view the issue? The repro says "Open the Developer Tools" . . . but since this isn't a browser the devtools aren't just a menu away.

[millerds]

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)

[mailchecktool-admin]

@millerds
The reason for using local storage this time is that the console could not display the getAttachmentsAsync value when sharing information with the Outlook client.
This add-in does not originally use local storage, so I don't think it is relevant.
I am sorry, but could you please tell us how exactly to implement this so that we can see the getAttachmentsAsync values that you want?

[millerds]

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