-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manifest.xml is not valid #43
Comments
The images are pushed to this repository so you can use their respective links only. |
As suggested, I had used this link: The response was this :
The hosting requirements for manifest URL's are stated here tl;dr
Hence to experiment I used this link : and then the result was what we are expecting :
|
Bug Report 🐛
When
npm run validate
is run, It gives the following message:The
manifest.xml
is not valid because of the error of the Icon URL which is from the localhostExpected Behavior
After running the
npm run validate
command, the validation should be passedCurrent Behavior
It fails due to LocalHost Icon URL error
Possible Solution
A possible solution might be hosting those logo's on the server and then using a link similar to this:
"https://LoremIspum/Images/ap-16.png"
for Icon URLSteps to Reproduce
npm run validate
Context (Environment)
Although this is not causing any issues right now, but since we want to publish Add-in in MS-Word's catalog, the manifest.xml should be valid and this issue should be fixed beforehand.
Desktop
The text was updated successfully, but these errors were encountered: