UI.displayDialogAsync() does not work in Outlook 2016 / Windows 10

1
votes

We build an Outloook Addin and are testing it across different platforms.

It works on all the browsers (IE 11, Edge, Chrome and Safari), but not in the Outlook 2016 on Windows 10. We root cause it, looks like the problem is Office JS API UI.displayDialogAsync() . It does not open a dialog in Outlook 16 and the addin just hangs in there with the following progress message spinning forever,

[Your Addin] is working onr your [Request]

The closest thing we found on the Internet is this Stackflow post in which the answer says the oldest Outlook build that supports this API is 16.0.6741.0000. We are using 16.0.9226.2114, so we meet the requirement.

Here are versions of OS/Outlook and Office JS we use in the test:

  1. OS: Window 10 Home, Version 10.0.16299, x64
  2. Outlook: 16.0.9226.2114, 32bit (Version 1804)
  3. Office JS: 1.1.5-release-next.1 (We download the exact package from GitHub and host it on our server)

Wonder is there any known issue of this API on Outlook 2016? Need some help here, thanks!

We have also been trying to debug Outlook 2016 using F12 developer tools . But our addin cannot show up in the chooser page, no matter we launch the chooser before or after we click on our addin. We have tried this on several windows 10 machines, but none of them work. Any suggestions that what we could possible miss here?

1
outlook-web-addins
1) Can you add the lines of code you are using for displayDialogAsync? 2) Are you trying to access a web page that is not in the <AppDomains> section of your Manifest 3) Are you getting an error back from displayDialogAsync? (if so what) 4) Hosting the Office.js from your server should work, but you may try going directly to: appsforoffice.microsoft.com/lib/1/hosted/office.debug.js to be safe. 5) Instead of using the F12 tools, you can also attach a debugger (i.e. Visual Studio in script mode to the instance of IE) – Outlook Add-ins Team - MSFT
If it is possible to share the add-in manifest, to see if we can get a local repro that would be good too. It is possible that the add-in just isn't being loaded at all. (though this probably isn't the case if you have already narrowed the issue down to display dialog) Can you load a Taskpane add-in (hosted on the same server) instead of an ExecuteFunction? to make sure IE/Outlook isn't haven't trouble reaching it. – Outlook Add-ins Team - MSFT
We've been looking into the F12 Developer Issue, and we also repro not being able to attach to an ExecuteFunction. We're looking into it. For now though, we are able to attach with VisualStudio to the IE Instance. (you may need to enable script debugging in Internet Explorer Manually though) Tools->Internet Options -> Advanced. We were able to F12 debug on a taskpane. So if you can don't want to use VS, you could run your code in a taskpane app, and F12 debug it there. – Outlook Add-ins Team - MSFT
Thank you for the reply! We see <AppDomains> is the issue. We did not add the domain that the dialog is trying to open (a different domain than the addin itself that we have added). – CodingFanSteve
The window opens now! But clicking on the windows throws us error which is not the case on IE 11. Checking them now. – CodingFanSteve

1 Answers

0
votes

Seems to me that you had a similar issue to mine. For me adding the remote domain in the manifest resolved the case. Find and update the following section:

<AppDomains>
  <AppDomain>https://your.domain.com/</AppDomain>
  <AppDomain>https://auth.com/</AppDomain>
</AppDomains>

Proxy HTML works cause it's loading from your domain and still is viable solution.