Office Add-in Error when using Centralized Deployment

1
votes

I am trying to deploy a Microsoft Word Office Add-in through Office 365 using centralized deployment. I created my project using the yeoman generator and VS code. After testing and running on my local machine I built to project using npm run build (this created the dist folder). I then deployed this on a web server. I then took the url to this folder, confirmed that it worked, and updated my xml file. I then deployed the xml through central deployment on office 365. I then opened word and was able to download the add-in through insert -> my add-ins -> manage add-ins in word. However when I click on the add-in to load the taskpane it gives the error enter image description here

My question is what can be causing this error. I have confirmed that I can access the files that I am hosting on my web server, and I double checked that I updated my xml file properly. I have been following this documentation from Microsoft: https://docs.microsoft.com/en-us/office/dev/add-ins/publish/publish-add-in-vs-code

1
office365office-jsoffice-addinsyeoman-generator
Hi there, can you centrally deploy any add-ins from the store? Does the issue only happen while centrally deployed and not sideloading? If you're having issues, I'd also try clearing the Office cache -- docs.microsoft.com/en-us/office/dev/add-ins/testing/clear-cache. Also can you clarify what you mean for "Microsoft Word Office add-in through Office 365".. Is that Word for web, or Windows or Mac? Thanks! – Keyur Patel - MSFT
@KeyurPatel-MSFT I am able to centrally deploy add-ins for the store. It only happens when centrally deploying, the add-in works when sideloading. Clearing the cache did not solve the issue. By "Microsoft Word Office add-in through Office 365" I meant to say an Add-in for Windows/Mac/Web using the Office.js taskpane. Thank you for the response. – nsharma98
Is web server available to public access or only within your network? Did you test your changed manifest file by sideloading it in office online? – Developer
The web server is public and yes the changed manifest does work when sideloaded. – nsharma98

1 Answers

0
votes

I moved my web app to Azure instead of using my local web server, and that solved the issue.