User are blocked from sending emails in OnSend Event Activation about office-js

[pavelstudeny]

@ztcdsb I have updates from the users - this is marked as completed so if a fix is on the way, at least for the record:

Clearing the cache helps all the affected users. Some of the users had issues with other add-ins and it helped with those as well.

[pavelstudeny]

It did help a few. I should have the info next week if it helped everybody.

[neprasad-microsoft]

Hi @pavelstudeny
Could you please test the behaviour on some other platform (Outlook Web/Mac) and let us know if it happens there also?
Also, if this is a store add-in then please send us the store link. If not, then please share the manifest on [email protected].

[pavelstudeny]

This stops happening when the affected users switch from classic Outlook to New Outlook or OWA. Furthermore, I'm not aware that Mac users would affected. This seems to be specific to classic Outlook for Windows.

Additionally, we don't see this happening to 98% of other classic Outlook users with seemingly the same configuration (Outlook version, Windows version).

So far, we cannot tell whether

1. the JS engine doesn't instantiate for the users
2. Office JS doesn't load
3. or the add-in OnSend handler doesn't evaluate

It's difficult to diagnose this with the users who don't even have admin rights.

The add-in manifest is available at https://addin.outreach.io/ .

[ajays-msft]

@JuaneloJuanelo - FYI

[pavelstudeny]

We have verified with one of the affected users that clearing the cache at %LOCALAPPDATA%\Microsoft\Office\16.0\Wef resolves the issue. What might have affected the cache behavior:

• The cache was fairly big
• Might be related to updates of the add-in assets (e.g. could the OnSend handler be removed from the cache and not downloaded again?) I observe that occasionally, some other assets such as add-in ribbon icons are not displayed in classic Outlook

[ztcdsb]

It could happen if the user get a bad version of bundle.js. Please let us know if clearing the cache resolve the issue for all affected users.

[pavelstudeny]

@ztcdsb more updates: this is still not fixed and users have to clear the cache to keep their add-ins operational. Per the report, they need to do this for multiple add-ins.

[ztcdsb]

@pavelstudeny This should be fixed once the user clear cache and restart add-in, it will download latest bundle file.
Can you ask user to confirm if bundle.js is downloaded?

bundle.js is per add-in basis, it locates in a directory with unique GUID and Base64 encoding.
The highlighted part is the add-in ID
For example:
%LOCALAPPDATA%\Microsoft\Office\16.0\Wef{A1D477E9-63F7-4857-AEC1-7864F9BBB6C1}\SWslFPVB6+BoZ3BWunn15w==\Javascript\ a213afbb-806e-2d05-bbaf-ef3384d30022_1.1.0.0_en-US