Our Outlook addin saves and loads custom properties. Our server code may also add a property to the list of the addin's custom properties via EWS and OWA and Windows Outlook see those server added properties just fine but for some reason in Outlook for Mac a server added custom property is not available.
Ideas? Is it a bug or some kind of a restriction?
Seems like a Mac Outlook bug because OWA and Windows versions work just fine.
As of 16.14.1 this is still an issue. When will this be fixed?
This looks like a bug in Mac Outlook. We are working towards fixing it.
Related
We have developed outlook Addins and hosted on Apache Server with SSL certicate installed with it. Some days back it was working absolutely fine on both web as well office outlook client, after windows update and client update it returns Empty blank screen?
Till the Outlook Client version 1808 all looks good in client. After the Update to outlook client 1902 Addin Stopped working on outlook client.
The error message in F12 Debugger is thrown is :
Everything was working fine before update,
Note that this addin is build on Angular version 5 frame work using routes.
Update: I was loading office.js locally from the project not from the CDN, Now when I changes the office.js path in index.html to the cdn link "https://appsforoffice.microsoft.com/lib/1/hosted/office.js" Addins started working back.
But I need something not from CDN because one of our customer has on-primises server and not the office365 .So the problem I found is the office.js loading the outlook-win32.02.js but saying permision denied if loaded from the project and not from the CDN link.
Hope to get some suggestions from the outlook web addin Team....
After lots of reasearch I decided to use CDN link "https://appsforoffice.microsoft.com/lib/1/hosted/Office.js", and every thing started work as like before,
Then I decided compare my office.js inside the library with the CDN link javascript then I came to know that office script library is updated and I m having an old package, after reseach I found the github project updated recently , the below link will directly takes to the updated libraby , one can download with your existing one,
"https://github.com/OfficeDev/office-js/tree/release/dist" .
Hope this works for all having this issue.
We have a Custom Outlook Addin. Which is frequently giving
"Add-in error: This add-in may not load properly, but you can still try to start it."
After couple of retries it started working and it is happening on every first load when I click the add-in.
What could cause this issue ?
Our manifest file is fine and the site is also working fine in browsers.
Make sure add-in's pages reference the office.js library and include an Office.initialize handler.
Take a look at the Understanding the JavaScript API for Office section for more information.
I have a published/certified MS Outlook Add-In on the Microsoft Store:
https://appsource.microsoft.com/en-us/product/office/WA104381281?src=office&tab=Overview
It shows Product Supported: OfficeProductForAndroid and OfficeProductForIOS. However, the Add-In only appears on IOS devices (as well as Desktop, OWA, etc).
How can I get support to know why the Add-in does not appear on Android devices?
PS - it does work by adding our XML staging manifest directly. And other public store Add-Ins are working.
In mobile(iOS and Android) add-in need to be whitelisted to show on Add-in Management Screen if it is not installed manually or not installed at all.
Whitelisting of Add-in is done by our team on request. I think franConnect has been whitelisted. Soon it will start coming on Addin Management Screen.
I developed an add-in with a MessageComposeCommandSurface extension point.
It appears, is activated and works on outlook.office.com but with windows desktop client, Outlook 2016 (version 16.0.8625.2121), the button appears in compose mode but stays gray and it is not clickable.
I tested the command-demo-addin mentioned in Microsoft Docs and published on Github with the same result. Similarly, as shown on screenshot, it is impossible to click and launch the add-in which seems unactivated.
The COMPOSE buttons are disabled in the following instances:
1) The Item is in a public folder.
2) The Item is in Junk, Outbox (not drafts), or Sync Issues.
3) The item is "secure". DRM, or S-MIME encrypted. (older versions of Outlook also do not support S-MIME signed)
4) Outlook is offline.
In the situation where Read Mode add-ins are working, but Compose does NOT it is almost always #3. Usually the user will have on the option to always DRM / S-MIME their outgoing messages.
Update with image of security settings:
If Com Add-ins load a Custom Form this can also affect add-ins:
Checking Com Add-ins:
Note that outlook actually ships with some add-ins and a lot of com-addins work fine with Web Add-ins. It's only when Com Add-ins override the default new mail form (or other forms) that they can interfere with Web Add-ins.
Some COM add-ins will NOT use Custom Form, but will access the parent folder (item.Parent) and there is currently a bug that disable's Web Add-ins when a COM Add-in or VBA script does this.
File->Options->Add-Ins-> "Go" (next to manage add-ins)
If you have an antivirus instaled like avast, try to disable the addin of this and then try to open your compose mail window.
I'm trying to use MS Office Name.dll as a COM object.
I found some help in these links to do something like this in web browsers:
https://msdn.microsoft.com/en-us/library/office/ms455335(v=office.14).aspx
http://mcgivery.com/displaying-a-users-lync-status-using-namectrl/
http://blogs.msdn.com/b/tomholl/archive/2013/03/02/integrate-lync-into-your-intranet-sites-using-the-namectrl-plug-in.aspx
name.dll basically allows me to get presence information from MS Lync and display a contact card.
I was able to successfully create a test Windows Form application that references name.dll. VisualStudio creates an Interop for me and i'm able to use the class NameCtrl.
The project worked fine and my test aplication was able to display the contact card, but only when working with an old version of Office 2010.
When upgrading to Office 2010 SP2, it didnt work anymore. When using Office 2013, it never worked.
I can actually instantiate the object successfully, but the object's property 'PresenceEnable' is always 0, and trying to display the contact card throws an exception "E_ACCESDENIED 0x80070005". In these not-working environments, using the webbrowser (IE/ Firefox) still works fine.
Does anyone know what to do to make it work?
Why did it only work with an old version of Office 2010 and stopped to work with newer releases?
I talked to a Microsoft Office Engineer and he told me this dll was not meant to be used that way: it's only meant to be used inside web browsers.