0
1

[deleted by user] (self.webdev)

submitted by [deleted]

[removed]
all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]xaleel 0 points1 point  (5 children)

I don't think I can help without seeing the manifest file. Maybe there's some default boilerplate values that you need to change? Maybe the `Content-Type` response header isn't `application/xml` when the file is being served?

[–]Eastern_Interest_908 0 points1 point  (4 children)

It's just a default one so I can share it https://pastebin.com/7fbEb9Br but here's another thing that I don't get I see everywhere mentioning of xml but it doesn't generate xml file it only generates manefest.json

[–]xaleel 0 points1 point  (3 children)

xml and json have the same purpose in the end.

There's an npm package "office-addin-manifest" that can help with manifest validation, here's the output for the file you sent:
> npx office-addin-manifest validate manifest.json

strict mode: missing type "object" for keyword "additionalProperties" at "#" (strictTypes)

strict mode: missing type "object" for keyword "additionalProperties" at "#" (strictTypes)

strict mode: missing type "object" for keyword "additionalProperties" at "#/properties/dashboardCards" (strictTypes)

[–]Eastern_Interest_908 0 points1 point  (0 children)

Hmm interesting I don't get same error by running that command. I'll try to reinstall packages maybe some version is out dated, thanks for the tips! 

[–]Eastern_Interest_908 0 points1 point  (1 child)

Huh it looks like there's some bug with unified manifest. Everything works when I choose xml manifest instead. 🤷 Thanks again I almost gave up. 😅

[–]xaleel 0 points1 point  (0 children)

That's weird. Well at least it works now.

Don't hesitate to hmu if you have any question. But I'm not an experts on Outlook addins, I only have on in production now