I work on an add-in for Microsoft Outlook, and recently we’ve received reports from some users that they can no longer click on buttons in the taskpanes of add-ins. Other add-ins, not just ours, have been affected by this issue. Affected users can still open the taskpane without issue. Our taskpane web view loads correctly, but then any clicking inside the taskpane has no effect. We are not seeing console errors when this happens.
To help narrow things down further: we’ve seen this issue occur in Outlook 2019 and Outlook for Microsoft 365 MSO with Office 365 accounts so far. We’ve seen this issue happen when the taskpane is opened from Compose view. One affected user was using Outlook 2019 version 16.0.13127.20266 (32-bit). Affected users have been running Windows 10, version 2004. A team member was able to reproduce the bug by updating to version 2004, but the bug disappeared for them after a subsequent system update on the same version 2004.
Has there been any recent change to add-in taskpane behavior that could be causing this issue?
This issue was fixed, and the fix should be available in Windows build 19043.1266 or later. Note that it is the Windows Build that matters, not the Office build.
We are seeing the same thing since updating to Windows 10 build 2004. For us, the add-in task pane freezes when the user tries to reply to an email (which is also compose view I guess).
Would be good to get an update on this as it is breaking the add-in for our users.
We are using Outlook Version 2009 (Build 13231.20200)
This is Outlook for Microsoft Office 365 MSO (16.0.13231.20146) 64 bit.
Related
We have a custom Outlook VSTO add-in. We publish to a location which installs based on version, and it has worked perfectly for years. For some reason, the new version we pushed today is not running properly. It installs fine, it appears to be running (i.e. shows in the list of Add-Ins, has delays ignored, and shows as active) but the icon that should show up in the ribbon for a meeting is not appearing. It does work on the developer machines. No errors are logged anywhere, including Application Event Viewer. The install package does seem considerably larger, but there are no massive upgrades, and the machines with the issues have .Net 4.8 as do the development machines.
but the icon that should show up in the ribbon for a meeting is not appearing
By default, if a VSTO add-in attempts to manipulate the Microsoft Office user interface (UI) and fails, no error message is displayed. However, you can configure Microsoft Office applications to display messages for errors that relate to the UI. You can use these messages to help determine why a custom ribbon does not appear, or why a ribbon appears but no controls appear. See How to: Show Add-in user interface errors for more information.
Also you need to make sure that images are available on the end user machine.
I have an Add-in I have written for Microsoft Outlook. The Add-in runs in a task pane. I have a button on the html in the page that opens a new window using Office.context.ui.displayDialogAsync. This button works fine in the web client, but when clicked in the full Outlook client, a window appears and disappears in a split second. This Add-in was developed outside VS so not sure how I can debug apart from in web client, which not does have the issue.
The domain is the same, and the domain is in the appDomain of the XML manifest. The URL is also https.
Does anyone have any ideas, have I missed something that says this isn't available in full client and only available in web client?
About Outlook version:
Version 2102 (Build 13801.21004 Click-to-Run)
Microsoft Office for Outlook 365 MSO (16.0.13801.21002) 64-bit
If I clock Office Updates, it tells me Office is up to date.
Update
I have another machine with Outlook installed, and I have discovered the dialog opens fine on the full outlook client. Looking at the version for that version of outlook (logged in to the same Office 365 account), the version shows as:
Version 2110 (Build 14527.20226 Click-to Run)
Microsoft Office for Outlook 365 MSO (Version 2110 Build 16.0.14527.20168) 64-bit
So it looks like maybe the earlier build had an issue in Outlook?
Would you like to share a screen recording in the machine where the API is not working?
Besides, you could also try a test add-in with this: Manifest.
It's an app command so you can click "Show Taskpane" first, and then click "launchDialogSameOrigin" button in the taskpane. You can observe whether the dialog is working correctly in this add-in.
Thanks.
I've submitted my outlook add-in 6 times now and every time the certification failed for a different reason. The last rejection reason I got was that my add-in didn't work on Office 2013 and Office 2016 (which they also refer to as O365 Perpetual).
I develop on a Mac and I have no idea how to go about debugging why my add-in is not working on those older Offices. Can't I just drop support for older Office suites? How could I test these environments?
I'm pretty close to quitting and just not publishing my outlook addin. I have never experienced a worse app review process.
If you want to be published on the Office Store, you need to support all the platforms for the minimum Outlook API Requirement Set in your manifest.
If you do not need to support Outlook 2013 or Outlook 2016, you can set your minimum API requirement set to 1.5, which will drop support for those versions (1.4 was the last version supported by those versions of Outlook). When you submit to the Office Store, please make a note that your minimum API set means that the add-in will not run in those Office clients.
We developed an add-in for Outlook which is published in the store already. It has paid and trial versions. License checking in the add-in works fine if the add-in is used from a browser, Outlook for Mac. But if it is Outlook for Windows or outlook.live.com (versions where "add-in commands" feature is enabled and add-in is opened in a side bar) then no license information is passed.
Example:
This correct URL is navigated from Outlook Web and Outlook Mac:
https://serverurl?et=%3cr+v%3d%221%22%3e%3ct..............
This is how the URL looks like for Outlook for Windows:
https://serverurl?_host_Info=Outlook|Win32|16.01|en-US
So, since Outlook for Windows does not supply license information we have to refuse add-in access for our clients on Outlook for Windows.
I found related questions for Excel and Word, but none of them was answered yet. The problem is that it is Outlook that needs to send the data, so we can do nothing in our code to troubleshoot.
Guys, any ideas where the problem is or what to check in the manifest?
Here is the link to the add-in listing in the Office store (TextMiner) if it may help to answer.
I have written an Outlook add-in (VSTO in C#) and now the problem occurs that on some machines (all Windows 7) with Office 2010 installed the Outlook add-in suddenly becomes inactive after a Windows Update (including at least one Office update).
It can be reactivated without any issues though and everything will be working fine, including the user-settings.
Do you know what could cause this behavior?
Thanks.