Open simonmurrell1979 opened 4 months ago
Thanks for reporting this @simonmurrell1979.
@exextoc, could you please investigate?
@simonmurrell1979 Thanks for reaching out. This is wired, because Add-in's sandbox timeout after 5 minutes, it is not likely the signature still got inserted after 5 minutes unless your add-in is blocked by something else.
Can you create a new Outlook profile and install this add-in only. See if the issue persist
I have multiple profiles. I will do this for you on my other profile and see if the same issue occurs. The TypeScript add-ins are doing the exact same in both profiles. I will check what the outlook-set-signature example does in the other profile.
In other profile, Windows Classic it executed even longer than the original profile. Outlook Online it is immediate. There is definitely something up with Outlook Classic.
Hello Guys
I hope you are well. Any update on this issue? Thank you
setSignatureAsync doesn't execute or executes after 5+ mins using the outlook-set-signature example.
Expected behavior
Add-in works perfectly in Outlook for Web, Outlook for Mac and Outlook for Windows Preview. It does not execute on Outlook Classic at all.
Current behavior
Add-in works perfectly in Outlook for Web, Outlook for Mac and Outlook for Windows Preview. It does not execute the setSignatureAsync event on Outlook Classic at all. All the task panes works 100% across all the clients (Web, Mac, Preview and Classic). Tried to write a brand-new add-in and it still doesn't execute the event. Tried the outlook-set-signature example on Outlook Classic and it inserts the signature 5+ mins later.
Steps to reproduce
Created a brand new add-in to see if it did the same thing. I then tried to add "OnMessageCompose" as an additional event to see if it worked or not. I then added outlook-set-signature and it worked 100% but it only inserted the "mock" signature 5+ minutes later. Are there any logs inside of Outlook Classic which I can use to debug the TypeScript. I have sideloaded the add-in but it never bounds to the breakpoints. I
Provide additional details
Here is the code from the command.ts
/*
/ global Office /
Office.onReady(() => { // If needed, Office.js is ready to be called. });
/**
@param event */ function action(event: Office.AddinCommands.Event) { const message: Office.NotificationMessageDetails = { type: Office.MailboxEnums.ItemNotificationMessageType.InformationalMessage, message: "Performed action.", icon: "Icon.80x80", persistent: true, };
// Show a notification message. Office.context.mailbox.item.notificationMessages.replaceAsync("ActionPerformanceNotification", message);
// Be sure to indicate when the add-in command function is complete. event.completed(); }
function checkSignature(event: Office.AddinCommands.Event) {
Office.context.mailbox.item.body.setSignatureAsync("Test", { coercionType: "html" }, function(asyncResult) { if (asyncResult.status === Office.AsyncResultStatus.Succeeded) { console.log("setSignatureAsync succeeded"); } else { console.error(asyncResult.error); } });
event.completed();
}
// Register the function with Office. Office.actions.associate("action", action); Office.actions.associate("checkSignature", checkSignature);
Here is the code from the manifest file.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
Context
Useful logs
Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.