According to this, I know that pinnable task panes are only available for Windows and Outlook Online. Is there any kind of workaround for pinnable task panes on OS X? If I modify the manifest to include pinning, Outlook for Mac sporadically crashes with bug messages like:
Exception: EXC_BAD_ACCESS
Exception Code: KERN_NAME_EXISTS (0x00007f86cd511698)
I assume this is because some objects are zombies when a pinned email message is changed. Is there any hope besides waiting for Microsoft to support pinning on OS X add-ins?
Now the documentation is updated and Outlook for Mac supports pinnable task pane starting from 16.13.503 version.
Pinnable task panes are currently available to Office 365 subscribers on Outlook 2016 or later for Windows (build 7668.2000 or later for users in the Current or Office Insider Channels, build 7900.xxxx or later for users in Deferred channels), Outlook 2016 or later for Mac (version 16.13.503 or later), and Outlook Online.
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.
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.
We have an add-in that works fine on Outlook for mac but not on windows for IMAP (Gmail) accounts.
Is the setup different to how the IMAP is configured on MAC and Windows?
Mac Version - 16.41 (20091302)
Win Version - 16.0.13127.20402
This is an issue because a lot of our users are unable to use the add-in when they have multiple accounts in Outlook on windows (of which most are IMAP - Gmail)
I would have thought it would be other way around where Add-ins would be available on Windows and not on Mac since a lot other things are not supported on Mac within outlook.
Are there settings that can be changed to make them available on windows or of anyone knows about this being available in the future?
----------------- UPDATE --------------------
Mac Version - 16.42 (20101102)
So, this morning 19th Oct, 2020. I got an Outlook Update for mac and as per the screenshot below, you can clearly see that I am using a Google Account (IMAP) and the add-ins are availanle.
Outlook Web Add-Ins are only supported on Outlook accounts connected to an Exchange server. Further documentation here : https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/add-in-requirements
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.
I'm trying to develop addins for Outlook 2016 for Mac, doesn't seem like it's possible to add command buttons to the ribbon. I am able to create only custom panes in the Read/Update windows for Message and Appointment.
Anybody knows why ? The Windows version works as advertised.
Assuming you mean these kinds of add-in command buttons, Mac Outlook doesn't support them yet.