Can't upload manifest.xml to 365 admin Center

[PierreAdmin]

Provide required information needed to triage your issue

Hello everyone, and thank you in advance for your help. I've been working all week on a manifest.xml and a function.js. The goal is simple: create a button in the Outlook ribbon to open a predefined URL.

After having my manifest validated twice by Yeoman, I tried to upload it via the admin console. I can see the project appear. I only selected my user to run a test before pushing it to all the company's users. I can see the logo, the publisher's name, etc., but when it came time to deploy, here's the error code: "This operation failed. Here are the possible reasons: Learn more about the eligibility requirements." I've seen a lot of posts on this topic but no clear answer. Can you help me?

Your Environment

• Platform [PC desktop, Mac, iOS, Office on the web]: Office on web
• Host [Excel, Word, PowerPoint, etc.]: Outlook
• Operating System: Windows
• Browser (if using Office on the web): Chrome

Expected behavior

Tell us what you expected to happen --> Can i say work?

Steps to reproduce

1. Upload Manifest

Context

Upload manifest.xml

Useful logs

• Console errors
• Screenshots
• Test file (if only happens on a particular file)

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• CustomTab manifest cannot be installed via Microsoft 365 admin center. #4335
• Can't Upload Excel Add-In Manifest to 365 Admin Center #3214

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Hi @FreeSoftwareServers! Apologies for the delay in response here. It helps our team to debug the issue if we have a network trace. However, we understand the limitations you might have on your side to get new software deployed. In such case, we'll try to trace the issue from our back end logs. For that could you please try this again and share error message with ID? Appreciate your patience and collaboration!

Reference:

• Can't Upload Excel Add-In Manifest to 365 Admin Center #3214 (comment)

Solution 2:

Hi @FreeSoftwareServers, Update on this one: I checked logs around that date "July 19 2023 12:38 Vancouver time", and I found the root cause of the issue being the tenant is a multi-forest tenant and the org mailbox is in some different forest and the admin's mailbox is in some different forest. This caused failure in deployment as we didn't have support for this scenario. Good news is that, this week only, we rolled out the changes which allows the above scenario to work. So, the deployment should work fine now for your admin user. Please try again and let us know if there are still any issues, otherwise we can mark this issue as closed.

Reference:

• Can't Upload Excel Add-In Manifest to 365 Admin Center #3214 (comment)

Powered by issue-sentinel

[PierreAdmin]

I already dead everything on this.. Never resolve my problem.. 🥲

[PierreAdmin]

Update,

I contacted the tenant admin, who was able to upload the file but encountered an error (Echec, manifest not OK):

I don't understand how the file can have this error when it was configured AND validated by Yeoman...

You can find the manifest.xml file on my Github/addin

[Oleg-O]

It appears there are a few things wrong with your manifest:

1. there is an unexpected requirement set with name "OpenBrowserWindowApi" - please remove it
2. all 3 icon resid values (e.g., "Icon16") don't match the id values in the Resources section (e.g. "Icon.16x16")
3. SuperTipDescription appears in ShortStrings resources but should be in LongStrings resources

Have you made these modifications in your manifest by any chance? Once I fix these, your manifest installs successfully.

Hope this helps.

Unfortunately, the validator tool only mainly checks the XML schema and does not check all the things that actual ingestion pipeline checks, and mismatched IDs and unexpected requirement sets are among them.

[PierreAdmin]

Hello @Oleg-O

Thanks for help, i appreciate.

I'm a complete novice with XML; the OpenBrowser API part was taken from another codebase...

For the images, it's a format error. I had modified it in my version 4. However, the LongStrings are a good idea. I'll upload it to the office tomorrow and will be sure to keep you informed if everything is OK.

For the process, I found some great inspiration here:

https://medium.com/nexl-engineering/part-3-open-link-from-a-ribbon-button-building-outlook-add-in-with-react-a49fc130810

[PierreAdmin]

@Oleg-O

Sorry for the inconvenience, I had also made another modification, FunctionFileUrl pointing directly to the JS, it was not a problem? Because in my last version, I pointed it to a .html (as indicated on the microsoft website, and in the html, there is the JS path.

[Oleg-O]

That would be a problem at runtime, it's not something we check and enforce at installation. Yes, it should be pointing at an HTML as described in the FunctionFile element documentation.