Open madhukar4e opened 3 days ago
Here are some similar issues that might help you. Please check if they can solve your problem.
Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)
This should be resolved. Please let us know how that looks for you now. Apologies for the disruption.
Reference:
From your sample code you do not appear to be registered for item change events. If you want to support pinning, you need to call addHandlerAsync() with the itemChanged event. I've created a short ScriptLab gist file with an example here: https://gist.github.com/exextoc/cdda502b27dbb69bfd98a9e5b12f4767
Reference:
Depending on your scenario, you can have useEffect
in both initialize and the addHandlerAsync. A number of things could stop working if AddHandlerAsync / ItemChanged is not included with a pinnable taskpane, even though getUserIdentityTokenAsync()
does not depend on the item. Calls to getUserIdentityToken
should succeed once you include addHandlerAsync()
no matter when they were called.
Reference:
Powered by issue-sentinel
I am working on a previously fully-functional Outlook Add-in that is having issues retrieving the mailbox.getUserIdentityTokenAsync only for some Outlook accounts.
Your Environment
Expected behavior
All Outlook accounts are able to successfully retrieve an ExchangeIdentityToken upon calling: Office.context.mailbox.getUserIdentityTokenAsync()
Current behavior
Some accounts (no discernable pattern) fail to retrieve the token and produce the following error response: "Internal protocol error: '-2147467259'." and "AccessRestricted".
Steps to reproduce