search

OfficeDev / office-js

A repo and NPM package for Office.js, corresponding to a copy of what gets published to the official "evergreen" Office.js CDN, at https://appsforoffice.microsoft.com/lib/1/hosted/office.js.
https://learn.microsoft.com/javascript/api/overview
Other
690 stars 95 forks source link

OnAppointmentSend add-in is unavailable and time-out after short of time #4883

Open ttuyen1529 opened 2 months ago

ttuyen1529 commented 2 months ago

We have an event-based add-in that trigger OnAppointmentSend event and it released to our customer. Recently, some users from our customer reported that one-two user from them can not send anything and Outlook showing that our add-in is unavailable and can not process this message since we are using Block option on manifest file We had an online session with user who faced this issue and checked the log, also the bundle.js file, clear the cache, etc.... Everything is normal, except that the runtime logging never trigger OnAppointmentSend event

Also I noticed that Viva Insights in his computer also show in the event viewer

Provide required information needed to triage your issue

Your Environment

Here is some screenshot for the log: image image

ttuyen1529 commented 2 months ago

Updated: I can confirm that I can reproduce it on Windows 10 with Outlook version Microsoft® Outlook® for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20206) 32-bit

ttuyen1529 commented 1 month ago

Updated: multiple users from our customer have same issue with Outlook version 2047 Build 17830.20210 also update Outlook to lastest version on Monthly Enterprise Channel see this issue

ttuyen1529 commented 1 month ago

Please help us...any idea @exextoc, many customer of us start to migrate and it is going to critical now in our side

sivachandran-msft commented 1 month ago

Hi @ttuyen1529, thanks for reaching out. Apologies for the delay in response. Is this issue observed in Classic Outlook or in New outlook? Are you seeing any error related to your add-in in the event viewer as well?

ttuyen1529 commented 1 month ago

Hi @sivachandran-msft. this is only observed in Classic Outlook. We have public 2 version, v1 with onSend, v2 with receipt change event adding

One customer have problem when update from v1 to v2 One other roll out v2 in today and feed back that all user cannot send anything since we use send mode as Block in manifest.

And only error show in Event Viewer is "We're sorry, we couldn't access [our add in name]. Make sure you have a network connection. If the problem continues, please try again later."

ttuyen1529 commented 1 month ago

And it only occurred on Monthly Enterprise Channel only, our internal using Current Channel of Office 365 and everything still works as expected

ttuyen1529 commented 1 month ago

FYI: same my account works on lastest version on Current Channel and not works on lastest version of Monthly Enterprise Channel

ttuyen1529 commented 1 month ago

It works only once time when I clear wef and HubAppFileCache folder... then it back to timeout issue

ttuyen1529 commented 1 month ago

The only log in runtime I see is:

10/10/2024 9:28:36 Verbose Runtime [Console] [Log] Platform Bundle - Office exists!
10/10/2024 9:28:36 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions exists!
10/10/2024 9:28:36 Verbose Runtime [Console] [Log] Platform Bundle - Office.actions.associate exists!
10/10/2024 9:28:36 Verbose Runtime [Console] [Log] Outlook Batch JS loaded!
10/10/2024 9:28:36 Verbose Runtime [Console] [Log] Outlook LaunchEvent JS loaded!

the associate action never called...

sivachandran-msft commented 1 month ago

Tagging @zhngx @timwan10 for Outlook desktop.

ttuyen1529 commented 1 month ago

Hi there... I found out that my developers when developing new version have put a syntax not allow on ecmascript, but it still show the difference between update Channel of Office 365.. So could you guys inform me some information on this?

zhngx1 commented 1 month ago

@ttuyen1529 Sorry for the late response. Let me try to repro this issue.

zhngx1 commented 1 month ago

@ttuyen1529 Just to clarify, did you encounter the issue after upgrading Outlook or after releasing the v2 of your app? Does v2 of your app work on older Outlook versions?

Unfortunately the event based add-in uses a different runtime than the taskpane add-in, so not everything supported in the browser is supported for event based add-ins. Here is a documentation about it: https://learn.microsoft.com/en-us/office/dev/add-ins/testing/runtimes#javascript-only-runtime