Outlook addin not working on Office 2013 or Office 2016

0
votes

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.

1
outlookoffice-jsoutlook-web-addins
Clarify, this in an add-in in Access or an add-in in Outlook? - June7
@June7 It's an Outlook Add-in - Anthony Silva
Still want to make sure I understand. I should open Access and with Add-in Manager add this Outlook Add-in? Where can I find the add-in? - June7
You can install virtual machines with Office 2013 and 2016 where you can debug the add-in. Office add-ins are supported by Office applications starting from 2013. - Eugene Astafiev
Please be aware that the validation team will not be able to discuss individual submission results on Stack Overflow. As per our documentation, we cannot and do not provide customer support for individual submissions on StackOverflow. You can raise a Customer Support ticket here: aka.ms/marketplacepublishersupport 1. Browse topics Category: Commercial Marketplace 2. Topic: Certification issue 3. Next step: Review solution - Office Store Developer Comms

1 Answers

0
votes

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.