After performing an action using a Ribbon command one may want to display a message using the dialogAPI.
I noticed that, if the dialogAPI window is not closed by the end-user, when navigating to another email and clicking again the ribbon button Outlook crashes. This happens randomly, you may need to visit several emails and clicking the ribbon.
This is annoying, one of the great aspect of the new office add-in model is its stability.
Is this a bug? Is there a workaround or am I doing something wrong?
My config
Outlook: Outlook 2016 32 bits version 1611 (Build 7571.2072)
Windows 10 Pro 64: Version 1607 OSBuild 14393.447
Full add-in code for reproduction:
https://github.com/bpatra/dialogapisample
This was fixed in Outlook build 16.0.7729.1000. Thanks for reporting!
Related
At one point I was able to see our Outlook add-in app in the target options in f12 devtools for troubleshooting, but sometime last month it stopped showing up there. My colleagues are stumped, and I can't find much online in the way of troubleshooting.
I tried checking my Windows version and Outlook version against others who can see it in their devtools, but we're all on Windows 10 enterprise v1803, Outlook v1910, and IE 11. I've tried many things over the month since this happened like rebooting my PC, making sure I have the latest updates from IT, refreshing the options, running some commands I found online for targeting the right browser for devtools, etc. No change.
Another peculiar thing is that I'm seeing some completely different things in the Add-in than they are, like button alignments and div widths and such. I had our dev environment looking perfect on my end, but when a few people on the team screenshared with me there were a number of styling issues I can't reproduce. Even weirder, nobody experiences these issues in O365, it's just the desktop Outlook app on our Windows machines.
Any ideas on how to troubleshoot this would be very greatly appreciated.
Steps I take to produce the issue:
Click on manifest icon for our app in Outlook ribbon. App loads in the sidebar.
Open F12 devtools (both 32 and 64 bit for good measure from the System32 and SysWOW64 directories).
App is not in the target list. Click refresh, still not in the list.
FYI, any IE 11 windows I have open show up there, just not my app.
Starting in Windows 10 version 1903, the latest version of Office will use Edge WebView instead of IE to render add-ins. Edge WebView requires a different debugger (not the F12 debugger) called Microsoft Edge DevTools. You can find out more about it here.
We are developing an office powerpoint content app. During the slide show (presentation mode) the user needs to be able to click buttons. Until last week this worked perfectly fine, but now I am not able to click buttons during presentations on my Laptop (Lenovo Thinkpad E540). The presentation will just jump to the next slide, thus the app is not focused. But this still works on my colleague's laptop (Asus Vivobook S400C). We use the same versions of Powerpoint (2016) and Windows (10). Rolling back to older versions of our code did not work as well.
Is there any setting in Powerpoint that could be responsible for this issue or is there any way to make this possible using the office.js API?
Edit:
Lenovo Laptop PowerPoint Version: 16.0.7726.1042 (64 Bit)
Asus Laptop Powerpoint Version: 16.0.8201.2102 (32 Bit)
Do you believe I shoud just wait until I am able to update to a higher version?
Thanks in advance
I cannot add a comment for this question. I have exactly the same problem and it also on Lenovo laptop, powerpoint 2016. When going to slide show, powerpoint just show an static image (the snapshot at the time entering presentation mode), so clicking on it just make it move the next slide instead of focusing on the addin.
This was caused by a bug that has since been fixed. For more details, see powerpoint-content-add-in-on-windows-just-show-an-image-in-slide-show-mode
Background
We have an Office Addin running in production and we've stumbled across a case with a customer where I suspect that his Mac computer won't run Javascript in Outlook. I haven't been able to confirm it but the symptoms point to that. For example, event handlers for buttons won't fire.
Questions
What browser is running the add-ins inside Office for Mac?
How can I confirm or deny that Javascript is running in Office?
You can run the command
defaults write NSGlobalDomain WebKitDeveloperExtras -bool true
from the terminal and relaunch outlook. When you launch Addin, you can invoke debugger tool using menu item Inspect Element (do right click).
It might help you to debug your Addin issues.
I'm not sure what is going on here but if the add-in properly launches then we can rule out JavaScript itself not running. Were this the case the Office.initialize event would fire and Outlook wouldn't report an error.
As to what is actually happening, I would need a bit more information. They primary questions I have would be:
Are they able to run other add-ins properly?
Are they using Outlook 2016 against a modern Exchange Server or O365?
Have the updated Outlook to ensure they have the latest bits installed?
I'm working on an Outlook addin using the new Office-JS apis, and in building out the authentication flow, I've found that in the Outlook 2016 for Mac case, the dialog system seems to not work properly.
To be clear, we're using the Office Insider Fast Track build as it has much improved support for the Office-JS API.
I've been through several iterations of this particular piece (most of which worked fine both in the Windows client and the web client on Mac and Win), and have had no luck. The scenario is:
List item
Open up the task pane in outlook.
Hit the sign in button
A new window opens, pointed at our authentication portal
User signs in.
On auth completion, the window redirects to a page in the office add-in scope, and calls back to the parent frame with the auth token, where it can be further processed.
Steps 1 through 5 work fine on all platforms. Step 6 refuses to work on Outlook for Mac. Initially, this flow was built using the native js window.open and window.postMessage apis. As mentioned above, this worked everywhere but Outlook Mac, where, the API seemed to ignore the window options and just open the url in a new tab in whatever browser was open and never setting the child window reference (result of window.open being null).
Failing this, I followed the advice found here on SO to use the Office functionality, displayDialogAsync and messageParent. After some initial hurdles, this too was setup and working on every platform save Outlook Mac.
As there is no dev tools or JS console support in Mac Outlook, I followed the advice found here Howto: Outlook 2016 for Mac - Debugging/View Console Logs in Outlook Add-in and setup Vorlon to attempt to get some context, adding numerous logging points to try and get some context. Unfortunately, while Vorlon does pick up my auth landing page as a client, and sees the Office interfaces, none of my console outputs are presented, making it seem as though the JS isn't running at all.
At this point I'm not sure what to try next. Has anyone run into this issue, or gotten this to work on the Outlook 2016 for Mac client?
Clarifying context:
All auth pages are listed in the AppDomains section of the Manifest.
While initial versions pointed directly at our auth service (this worked on not Mac), the current version first opens up an in scope pre-auth page that redirects to the auth service.
The Office-JS api's block alerts, preventing their use in displaying useful information.
Authentication through all versions of this app have worked on both Outlook 2016 on Windows and OWA on both Win and Mac.
Thank you.
This issue in Outlook Mac has been fixed a few months ago. If anyone still encounters this issue with a recent Outlook Mac build, please reply with the build number.
The Office.context.ui is undefined in v16.17 (180909) build of Outlook for Mac 2016 using the following OfficeJS dist:
https://appsforoffice.microsoft.com/lib/1/hosted/office.js
I have MS Outlook 2007, the MS CRM 2011 Outlook client and MS CRM 2011 on-premise.
After you install the MS CRM 2011 Outlook client you have a new toolbar within Outlook 2007. On that Toolbar is a button for 'New Record.' If you click that button a dropdown appears with different options, which for me includes 'Account' and 'Contact.'
The first time I click on 'Account' a small popup opens with a message like 'waiting for web page to load' No form ever appears. clicking on the button subsequent times produces the same result, minus the 'waiting' popup. I cannot seem to get the CRM form to appear.
The interesting part is that when the 'New Record' > 'Contact' option is clicked the Contact form appears and works without issue.
A work around for this is to use the actual website. That works without issue. However, I have a lot of users who use Outlook. So getting this to work proper would be ideal.
I did notice that an iisreset solved the issue once, but that doesn't solve the issue permanently or consistently.
Any help would be appreciated.
The fact that it works with Account and not with Contact is interesting as it means that the connector is talking successcully to CRM. Security roles should be fine if you can do it through the web interface also.
And that the issue was solved through an IIS reset temporarily points more towards connection issues, or possibly something on the Account form which is causing it to not load through the outlook client correctly.
Also check that you have Outlook 2007 with service pack 2 installed. Thats the minimum requirement for using the 2011 Offfice Outlook client.