Office.onReady() and Office.Initialize() get stuck/hangs intermittently in spam addins. about office-js

[glr0221]

Hello Swathy. Unfortunately, it is the only email right now where this is happening. I have seen this happen before in other emails but could not reproduce with those emails any longer. This one email though can reproduce it 100% as of right now. We will be sending the video and other details to Microsoft directly as we are communicating via email with the spam addin team as well. Thank you.

[mmanjaree-msft]

@glr0221 Can you please share any console logs you see for new outlook when you run into this issue. This will help us in out investigation. Also if possible any screenshot of the behavior you are seeing

[glr0221]

@mmanjaree-msft would be happy to help. How do I get the logs from the browser or new look outlook? Or are you referring to the browser's console logs? Thanks

[mmanjaree-msft]

@glr0221 Whenever and wherever this issue is encountered please share the browser console logs. To open devtools in new desktop outlook follow this https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/one-outlook#debug-your-add-in.

Also if possible please share your initialization code

[glr0221]

@mmanjaree-msft

Thank you for your responses. As for the initialization code, I am using the same code as the spam addin sample :

// Ensures the Office.js library is loaded.
Office.onReady(() => {
  /**
   * IMPORTANT: To ensure your add-in is supported in the classic Outlook client on Windows,
   * remember to map the event handler name specified in the manifest to its JavaScript counterpart.
   */
  if (Office.context.platform === Office.PlatformType.PC || Office.context.platform == null) {
    Office.actions.associate("onSpamReport", onSpamReport); }
});

As for the console logs, there was nothing in there. Except that a deprecated feature is used warning gets incremented each time the Office.onReady() is called.

I hope this helps.

[Swathy-Mothilal]

@glr0221 Unfortunately, we are unable to repro the issue on our end. Could you please share a repro video, logs and the manifest where you are experiencing the issue? This will help us debug more effectively.

Since you mentioned that you can repro the issue in one particular email, could you please try to repro it in other emails and let us know the results please?

[glr0221]

@Swathy-Mothilal @mmanjaree-msft

I agree on closing this ticket. I have not reproduced this for quite some time now. I have lost track of the two email samples I had that could reproduce this issue 100%. What I remember though is that, these 2 emails where the bug could be reproed, were moved from inbox-to-deletedItems for so many times. That was the only clue I had. But right now, I could not reproduce it anymore.

Thank you very much.