-
Notifications
You must be signed in to change notification settings - Fork 261
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 does not work with extension field content making Bot + Outlook add-in not possible #1397
Comments
Hello, I don't know if that helps but I found someone with a similar issue. The investigation is ongoing: |
Hi @jayzhang , Any updates on your side? |
Also hitting this issue when attempting to convert an add-in to use the unified manifest as per this tutorial; |
@Sphinx95 Thanks for reporting. I can not successfully reproduce the the command: The raw The normal step is: 1. create sample app ![]()
Alternatively, you can run command Could you please share your zip package without credential information in it? |
Hi @jayzhang , Thanks for the update. Please find the .zip file attached. |
Hello,
I'm new to programming and github so I don't know if I'm allowed to create issue.
I take the manifest sample on this repo:
hello-world-teams-tab-and-outlook-add-in/appPackage/manifest.json
I run the command: teamsapp package --manifest-file ./appPackage/manifest.json --output-package-file ./appPackage/build/appPackage.test.zip
I try to upload appPackage.test.zip in the Teams admin center but I get this error:
{
"error": {
"code": "BadRequest",
"message": "Failed to execute settings store request: https://emea.settings.teams.internal.office.com/v1.0/settings/teams/apps/6c4ec7c0-98a1-403c-ad61-f56d7a9585fb/definitionv2, StatusCode: 400, ReasonPhrase: Schema validation errors, X-MSEdge-Ref: 907de1a5-0d71-4763-beea-d7960e2e31f6",
"innerError": {
"code": "BadRequest",
"message": "Failed to execute settings store request: https://emea.settings.teams.internal.office.com/v1.0/settings/teams/apps/6c4ec7c0-98a1-403c-ad61-f56d7a9585fb/definitionv2, StatusCode: 400, ReasonPhrase: Schema validation errors, X-MSEdge-Ref: 907de1a5-0d71-4763-beea-d7960e2e31f6",
"details": [],
"date": "2025-02-08T18:20:37",
"request-id": "09ec8965-b8b7-49ce-8782-f6fe2d1e3958",
"client-request-id": "09ec8965-b8b7-49ce-8782-f6fe2d1e3958"
}
}
}
If I remove all the content in the extensions field then it works:
{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#appCatalogs/teamsApps/$entity",
"id": "cdbb4740-169f-4ec1-95df-5088ce90f644",
"externalId": "61c6407f-5b07-402e-bad5-14d404a1922b",
"displayName": "Contoso",
"distributionMethod": "organization"
}
Does anyone know what is happening? I went through 4 customer support tickets, no one knows how to solve this.
My understanding is that the extensions can be used to for example have a Teams app with a Bot AND an Outlook taskpane for example.
Thank you for your help!
The text was updated successfully, but these errors were encountered: