I'm developing an Outlook Office add-in, and need to allow the user to right click to choose a previously selected option from context menu.
Everything was working until I updated Windows 10 and Outlook. Now it is not working.
Windows Version
Outlook version
OfficeJs Version
host: Outlook,
version: 16.0.12026.20190,
platform: PC,
I wanted to enable right click menu as follows:
[Edit] My desktop outlook add-in is using edge web-view
Related
I'm building an outlook add-in for web and desktop users.
And I'm struggling to find the method that closes the add-in for the desktop version
In my Add-in, I inserted a button that invokes
Office.context && Office.context.ui && Office.context.ui.closeContainer();
onClick to close the add-in.
This works on the web version of the add-in but not on the desktop one,
Is there a problem with my code or is the desktop version not supporting this method ?
Environment setup :
Microsoft Outlook 2016 (16.0.5182.1000)
Exchange 2016 (build version 15.1.2375.7) on-premise
It should work for task panes on the desktop. Here is the description for the closeContainer method:
Called from a task pane: The task pane will close. Any dialog opened by displayDialogAsync will also close. If the task pane supports pinning and was pinned by the user, it will be un-pinned.
But the minimum requirement set is 1.5 where Outlook 2016 is not supported.
Also you may find a similar thread here.
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.
The problem:
I have a feature for a Microsoft Outlook web add-in which works fine in Office 365 Outlook, but when I test the same feature on Outlook for Mac or Outlook for Windows, the same feature doesn't work. The web add-in still installs fine on Outlook for Mac, it's just that there is a discrepancy between the behavior I am seeing on Office 365 Outlook and Outlook for Mac (this is also true when testing on Outlook for Windows, which has the same behavior as the Mac version).
What I've tried (Mac): I've tried running defaults write NSGlobalDomain WebKitDeveloperExtras -bool true as suggested from this answer and defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true as suggested here and have an option to View Source which opens the HTML source in what appears to be a TextEdit window, but I'm still unable to inspect element in order to see any errors.
What I've tried (Windows):
I've tried using the VSCode Debugger Extension for Office Add-Ins to try to attach the debugger to Outlook for Windows, but keep running into this 'Error processing attach' error.
Additional Notes:
On Mac, I'm running Microsoft Outlook for Mac version 16.43 on MacOS Catalina version 10.15.6 and on Windows I'm running Outlook on Windows 10 Pro version 1909 inside a VM.
My understanding is that while debugging web add-ins for Word, Excel, and PowerPoint are all pretty well supported, debugging add-ins for Outlook on Mac or Windows is somewhat limited at the moment. Has anyone had success in debugging Outlook web add-ins running on Outlook for Mac and/or Windows?
For Outlook for Mac, we think this is specific to the Mac App Store build of Office, which currently doesn't support those flags. To workaround this, you will need to get a non App Store build. You can get one by signing up for the developer program and getting a tenant: https://aka.ms/o365devprogram. (similar issue: https://github.com/OfficeDev/office-js/issues/506)
For Outlook for Windows, we suggest attaching a debugger. Instructions for how to attach a debugger can be found here. Note that there is a different debugger for add-ins that run in Edge and IE.
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.
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.