Reputation: 16563
I've got a Word add-in on AppSource. Under "products supported", the AppSource page lists:
However, for some versions of Word 2016, people are not able to install it. Here are some examples:
Here is an example error message:
which isn't helpful since the store says it works in Word 2016!
How can I know which versions of Word are actually supported by my add-in?
Is it possible that the add-in can be installed on business non-subscription Word, but that it isn't being installed correctly?
=== UPDATE ===
In case it matters, these are the requirements in my manifest:
<Requirements>
<Sets DefaultMinVersion="1.1">
<Set Name="File" MinVersion="1.1"/>
<Set Name="AddinCommands" MinVersion="1.1"/>
</Sets>
</Requirements>
Upvotes: 0
Views: 472
Reputation: 16563
I'll present my best understanding based on the comments and answers here. I'll try to update this as I get better info.
<Requirements>
tag in manifest -- Your add-in can be installed, but functionality is greatly reduced and is a bad UX. It seems that you can't add ribbon buttons. Users need to "Insert" the add-in each time you want to use it which is kind of like installing it.<Set Name="AddinCommands" MinVersion="1.1"/>
in manifest -- You can't use the add-in at all. The Microsoft folks pointed me to this Microsoft page a few times, but I honestly don't understand what info that page provides about Word 2016. This appears to be the only relevant paragraph:
The build number for Office 2016 installed via MSI is 16.0.4266.1001. This version only contains the WordApi 1.1 requirement set.
My add-in does not work on installations of business Word 2016 with a more recent build number.
Upvotes: 1
Reputation: 172
If you correctly mark the requirement set version in your Addin manifest file, then when users try to insert Addin from AppSource, it only list the addins whose required API requirement set version is supported by your current Office client.
For Word APIs, please check below page for the details:
Word JavaScript API requirement sets
Upvotes: 1