-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outlook 2016: API v1.5 no longer supported with newest release. #725
Comments
@jargil Pinging you here. |
This is the expected behavior. Outlook 2016 MSI versions (which is the one you are on) only supports uptil requirement set 1.4. Documentation here. If before this update it was sending true for supporting 1.5 that would have been a bug. What APIs are you dependent on that requires you to use requirement sets 1.5 and above? Requirement sets > 1.4 are only supported for outlook through office 365 subscription installations. |
@JefCurtis as previously commented, in that version of Office that's expected (1.5 is not supported there and if you call any 1.5 API will fail).What functionality of 1.5 are you using in your Add-in? Can you confirm such APIs fail in the cited build? |
This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins! |
This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue. |
Hello folks 馃憢
After updating Outlook 2016 using this update it seems that the version of OfficeJS has changed and removed support for Office API
v1.5
and above?Some of our Outlook add-in functionality was dependent on
v1.5
and up so there is a conditional check in the code to confirm that the version of Outlook the add-in is running in does support this version before toggling this feature on. I've been recently receiving reports from some of our users that their version of Outlook (2016) no longer support this functionality even though, before updating, it did work. Testing the same functionality in the browser and Outlook 2019 still works as expected.I can confirm this:
Is this expect behavior? Was there is change to the supported version of OfficeJS with this update?
Your Environment
The text was updated successfully, but these errors were encountered: