OfficeDev / office-js

A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
685 stars 95 forks source link

Outlook desktop (new Mac OS X UI): addFileAttachmentFromBase64Async throws code: 5001, message: "An internal error has occurred." in pinned add-in #2890

Closed guzman-rc closed 7 months ago

guzman-rc commented 2 years ago

Message from office-js bot: We’re closing this issue because it has been inactive for a long time. We’re doing this to keep the issues list manageable and useful for everyone. If this issue is still relevant for you, please create a new issue. Thank you for your understanding and continued feedback.

Provide required information needed to triage your issue

In an Outlook add-in (new Mac UI preview) for compose mode, we are using the addFileAttachmentFromBase64Async method to add attachments. In Outlook desktop "new Mac UI preview", the "Internal Error" occurs if the add-in's pane is pinned.

In Mac Outlook desktop "Classic UI" this method work correctly.

Your Environment

Expected behavior

Current behavior

Steps to reproduce

  1. Install MetaClean for Outlook from Microsoft App Source (https://appsource.microsoft.com/en-us/product/office/WA200003633)
  2. Start Outlook and select new Mac UI for Outlook.
  3. Create a new email in Outlook desktop.
  4. Click "MetaClean for Metadata" button.
  5. Click on the add-in’s pane and select a file to attach.
  6. The code that causes the error is (See Screenshots from Web Inspector):

Link to live example(s)




Provide additional details

  1. In Mac Outlook desktop "Classic UI" this AddIn work correctly.

Context

This bug is causing complaints from our customers.

Useful logs

Error returned by addFileAttachmentFromBase64Async method: 150651429-3a6fcd03-ed4c-44ef-abc0-ef92606a2184

exextoc commented 2 years ago

We have a repro of this issue and are working on it. We unfortunately have no timelines to share at this point