Office.context.mailbox.item.displayReplyAllForm doesn't start callback. We don't update our code, but this function doesn't start call back after we update Outlook through Microsoft Update (not sure but probably it may affect).
Office.context.mailbox.item.displayReplyAllForm invoke callback function as written in document.
Office.context.mailbox.item.displayReplyAllForm create reply all form and inject html body expectedly, but it doesn't invoke callback.
I investigated through displaying error. I can see 'Start' but can't see 'CallBack' in browser debugger view with following code.
console.log('Start')
Office.context.mailbox.item.displayReplyAllForm({
htmlBody: 'Insert html body'
// eslint-disable-next-line @typescript-eslint/no-explicit-any
callback: (asyncResult: Office.AsyncResult<any>) => {
console.log('Callback')
}
})
Office.context.mailbox.item.displayReplyAllForm. You may call this method from button.In 1 ~ 2 weeks ago, my colleague repro this issue, but I didn't have issue in my environment even if we have same OS version and Outlook version. But I can repro today, so I'm not sure about correct repro step and root cause.
If you want to see the problem, I can make time to have Teams call (screen sharing) with product team or I can send captured video if product team share me email address.
We want to communicate with server side after user see reply email form. If this callback is not invoked, we can't post necessary data to server side, as a result following process stops.
No log and screen shot, because callback is not invoked and can't write log.
Hello, I have been facing this issue when trying to invoking Office.context.mailbox.displayNewMessageForm
My Environment is:
NB: Office.context.mailbox.displayNewMessageForm works on Windows Outlook 365 Desktop version and on browser(Safari,outlook and Chrome)
We are able to repro the issue. Thanks for reporting it. It has been put on our backlog. We unfortunately have no timelines to share at this point.
Until this issue is fixed, the following workaround may work for you:
Update 3/13 -
(sorry I earlier had a workaround here) - This workaround is not supported and should not be used. We will update this thread when the bug has been fixed.
Internal tracking ids: Office:4016849 and OutlookWeb:79527
We have fixed the bug and the fix should be available in latest build.
Most helpful comment
Hello, I have been facing this issue when trying to invoking
Office.context.mailbox.displayNewMessageFormMy Environment is:
NB:
Office.context.mailbox.displayNewMessageFormworks on Windows Outlook 365 Desktop version and on browser(Safari,outlook and Chrome)