Latest JS and UI Changes are not reflecting in Outlook Web add-in (TaskPane) in new Outlook (Desktop) about office-js

[ajays-msft]

@geetamshukla - Is your addin running locally, or is it deployed on a server?

[geetamshukla]

@geetamshukla - Is your addin running locally, or is it deployed on a server?
@ajays-msft
I have tried both option . Not able to see latest changes for New Outlook Thick Client

[ajays-msft]

@geetamshukla - In order for any changes related manifest of your locally developed addin , that was first deployed via "npm start" to also show up in New Outlook, you will need to explicitly install the manifest in Outlook on Web.

https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/one-outlook#test-your-add-in-in-the-new-outlook-on-windows

What is the scenario you are trying to achieve? Can you please help me understand?

[rajjha-msft]

Hey @geetamshukla

Are you still facing the issue ?

[geetamshukla]

Hey @geetamshukla

Are you still facing the issue ?

yes ..for any new changes we are updating Manifest version and GUID still changes are not reflecting immediately in end user's m/c

[rajjha-msft]

• Are these changes local or deployed through web ?
• How are you propagating the changes (CD / Sideloading the manifest) ?
• Does it work for OWA or any other client ?

[geetamshukla]

• Are these changes local or deployed through web ?
• How are you propagating the changes (CD / Sideloading the manifest) ?
• Does it work for OWA or any other client ?

Are these changes local or deployed through web ?--> Post deployment /through web
How are you propagating the changes (CD / Sideloading the manifest) ?--> Sideloading the manifest
Does it work for OWA or any other client --> it takes 8-24Hrs to reflect changes if we r not clearing up the cache explicitly ..

How the Manifest gets cached in OWA /Old Thick Client /New Thick Client ? As I have observed that even though we are changing the Manifest version + GUID for each deployment .Still changes are not reflected immediately. We need to explicitly clear the cache to get latest changes which is not ideal for production scenarios . We can not go and clear each users browser cache

Also changing the Manifest version + GUID for each deployment is not good option as when we are re-deploying the manifest it takes 24-48Hrs to push Addin to end user's m/c .

[rajjha-msft]

When you say each deployment takes 24-48 hours, is it through CD ?

[geetamshukla]

When you say each deployment takes 24-48 hours, is it through CD ?
@rajjha-msft
No ,from CD we deploy changes to server within secs .
Its when we are adding user to an AD group and we install/re-install the Manifest in exchange admin ..at that time the Addin takes 24-48hrs to reflect in end users m/c .

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!