Using Office.onReady() Breaks Outlook 2013 add-ins
up vote
1
down vote
favorite
We're building an Outlook add-in, and recently a customer reported that it does not load in Outlook 2013. I've been able to confirm this locally across a number of different versions of our Add-in. It loads and works fine in Outlook 2016, Outlook Web and Outlook for Mac.
We recently changed from Office.initialize to Office.onReady in order to simplify platform detection. This does not work for Outlook 2013. On the face of it, the problem appears to be that the HostType is coming back as Excel, and many of the API's under Office.context (e.g. diagnostics, roamingSettings, mailbox) are undefined.
If I set the entry-point up using Office.initialize, then everything works fine. If setup using Office.onReady, the add-in will load, so long as all the Office api calls have guardrails around them. This lets me get some context out, as I can access our internal logging system.
Is this a known issue? Our add-in is now completely broken in Outlook 2013.
Update: I previously believed this to be an issue with both onReady and initialize, however I've since found that initialize does in fact still work. It is only onReady that appears to be broken in Outlook 2013
office-js outlook-web-addins
asked Nov 19 at 18:16
Ava
1479
add a comment |
up vote
1
down vote
favorite
We're building an Outlook add-in, and recently a customer reported that it does not load in Outlook 2013. I've been able to confirm this locally across a number of different versions of our Add-in. It loads and works fine in Outlook 2016, Outlook Web and Outlook for Mac.
We recently changed from Office.initialize to Office.onReady in order to simplify platform detection. This does not work for Outlook 2013. On the face of it, the problem appears to be that the HostType is coming back as Excel, and many of the API's under Office.context (e.g. diagnostics, roamingSettings, mailbox) are undefined.
If I set the entry-point up using Office.initialize, then everything works fine. If setup using Office.onReady, the add-in will load, so long as all the Office api calls have guardrails around them. This lets me get some context out, as I can access our internal logging system.
Is this a known issue? Our add-in is now completely broken in Outlook 2013.
Update: I previously believed this to be an issue with both onReady and initialize, however I've since found that initialize does in fact still work. It is only onReady that appears to be broken in Outlook 2013
office-js outlook-web-addins
asked Nov 19 at 18:16
Ava
1479
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
We're building an Outlook add-in, and recently a customer reported that it does not load in Outlook 2013. I've been able to confirm this locally across a number of different versions of our Add-in. It loads and works fine in Outlook 2016, Outlook Web and Outlook for Mac.
We recently changed from Office.initialize to Office.onReady in order to simplify platform detection. This does not work for Outlook 2013. On the face of it, the problem appears to be that the HostType is coming back as Excel, and many of the API's under Office.context (e.g. diagnostics, roamingSettings, mailbox) are undefined.
If I set the entry-point up using Office.initialize, then everything works fine. If setup using Office.onReady, the add-in will load, so long as all the Office api calls have guardrails around them. This lets me get some context out, as I can access our internal logging system.
Is this a known issue? Our add-in is now completely broken in Outlook 2013.
Update: I previously believed this to be an issue with both onReady and initialize, however I've since found that initialize does in fact still work. It is only onReady that appears to be broken in Outlook 2013
office-js outlook-web-addins
asked Nov 19 at 18:16
Ava
1479
We're building an Outlook add-in, and recently a customer reported that it does not load in Outlook 2013. I've been able to confirm this locally across a number of different versions of our Add-in. It loads and works fine in Outlook 2016, Outlook Web and Outlook for Mac.
We recently changed from Office.initialize to Office.onReady in order to simplify platform detection. This does not work for Outlook 2013. On the face of it, the problem appears to be that the HostType is coming back as Excel, and many of the API's under Office.context (e.g. diagnostics, roamingSettings, mailbox) are undefined.
If I set the entry-point up using Office.initialize, then everything works fine. If setup using Office.onReady, the add-in will load, so long as all the Office api calls have guardrails around them. This lets me get some context out, as I can access our internal logging system.
Is this a known issue? Our add-in is now completely broken in Outlook 2013.
Update: I previously believed this to be an issue with both onReady and initialize, however I've since found that initialize does in fact still work. It is only onReady that appears to be broken in Outlook 2013
office-js outlook-web-addins
office-js outlook-web-addins
asked Nov 19 at 18:16
Ava
1479
asked Nov 19 at 18:16
Ava
1479
edited Nov 19 at 19:33
asked Nov 19 at 18:16
Ava
1479
asked Nov 19 at 18:16
Ava
1479
asked Nov 19 at 18:16
Ava
1479
1479
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29
add a comment |
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
This has been identified as a bug in the Office-JS API and a fix is incoming.
To work around the issue in the meantime, you can continue to use Office.initialize. You can get the context provided by onReady's info parameter using Office.context.diagnostics
answered Nov 26 at 21:54
Ava
1479
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
This has been identified as a bug in the Office-JS API and a fix is incoming.
To work around the issue in the meantime, you can continue to use Office.initialize. You can get the context provided by onReady's info parameter using Office.context.diagnostics
answered Nov 26 at 21:54
Ava
1479
add a comment |
up vote
0
down vote
accepted
This has been identified as a bug in the Office-JS API and a fix is incoming.
To work around the issue in the meantime, you can continue to use Office.initialize. You can get the context provided by onReady's info parameter using Office.context.diagnostics
answered Nov 26 at 21:54
Ava
1479
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
This has been identified as a bug in the Office-JS API and a fix is incoming.
To work around the issue in the meantime, you can continue to use Office.initialize. You can get the context provided by onReady's info parameter using Office.context.diagnostics
answered Nov 26 at 21:54
Ava
1479
This has been identified as a bug in the Office-JS API and a fix is incoming.
To work around the issue in the meantime, you can continue to use Office.initialize. You can get the context provided by onReady's info parameter using Office.context.diagnostics
answered Nov 26 at 21:54
Ava
1479
answered Nov 26 at 21:54
Ava
1479
answered Nov 26 at 21:54
Ava
1479
answered Nov 26 at 21:54
Ava
1479
1479
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380486%2fusing-office-onready-breaks-outlook-2013-add-ins%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Thanks for noticing. We're looking into this. Is it correct to say the issue only affects when add-in is running on Windows platform (for Office 2013)? Thanks.
– Sudhi Ramamurthy
Nov 20 at 21:41
Yes, that's exactly right. Outlook 2013 on Windows machines.
– Ava
Nov 22 at 5:29