officedev / microsoft-teams-app-schema Goto Github PK

I'm writing a tiny Personal-Tab app for a client, we were expecting it to be ready for later today so I built it a few weeks ago using a dev tenant; however I cannot publish or remake it in the client's tenant now because App Studio for some reason is giving an error that "MPNID cannot be empty". And, it's returning this error regardless of whether the MPN ID field in the "App details" page actually has a value or not.

I've left it blank, set it to my company's real MPNID, set it to a random 7-digit number, set it to a random 2-digit number, set it to a random 10-digit number (as per the schema's stated max length), set it to an alpha string (why is this even allowed), etc... and none of these work.
I tried to raise this as a bug with App Studio but I couldn't find where that would be, so I'm going to submit this as a schema issue for now.

Since last update to the devPreview manifest the compose extensions commands do not default to "query". It now seems to require explicit setting of "type": "query",

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

This property serves no purpose

the new configurableProperties contain a property for websiteUrl but in the enum of the schema it is named developerUrl. Something is wrong here....
I am talking about the new 1.10 schema version that was released last night.

The releases entries for 1.6, 1.7 and 1.8 are not available in https://github.com/OfficeDev/microsoft-teams-app-schema/releases as specified in the README.md

According to this documentation (https://learn.microsoft.com/en-us/microsoftteams/platform/resources/schema/manifest-schema), the url below should display changes in manifest versions.

https://github.com/OfficeDev/microsoft-teams-app-schema/releases

However, it only shows releases upto v1.12, while the latest version is currently v1.15.

As a developer I'm interested in what changes in these kinds of manifests, so I wonder where the change log is.

Hi, we are currently facing this critical issue: Since around thursday we cannot upload any App Zip anymore, even though nothing has changed on our part.

The upload fails with a 400 Bad Request root | Required properties are missing from object: ["name.short","name.full"]. when uploaded either with the Admin Center or via Teams itself. The "Developer Studio" tool for manifest verification shows no errors.

Attached is the zip in question.
app-dev.zip

We have seen in the Microsoft's OneNote About, it has a carousel with a video and 2 images before the Full description.
How we could it also ?

Would just change it, but not sure what you want here.

Our manifest works correctly without the "context" section. When we include the new context section as below, a "Something went wrong" error is displayed.

The zip was uploaded via the "Upload a custom app" link in the Teams apps section as per the documentation on working with the DevPreview schema.

The relevant parts of the manifest are displayed below:

  "$schema": "https://raw.githubusercontent.com/OfficeDev/microsoft-teams-app-schema/preview/DevPreview/MicrosoftTeams.schema.json",
  "manifestVersion": "devPreview",

  "configurableTabs": [
    {
      "configurationUrl": "https://<redacted>",
      "canUpdateConfiguration": true,
      "scopes": ["team", "groupchat"],
      "context": [
        "channelTab",
        "privateChatTab",
        "meetingChatTab",
        "meetingDetailsTab",
        "meetingSidePanel",
        "meetingStage",
        "callingSidePanel"
      ]
    }
  ]

Is this something that is still rolling out to all regions?

The response with headers are included below if the Server Request Id helps with issue identification.

HTTP/1.1 400 Bad Request
Cache-Control: no-cache, no-store
Content-Type: application/json; charset=utf-8
Vary: Origin,Accept-Encoding
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://teams.microsoft.com
X-ServerRequestId: 926B36EEE3D542398363823A987E9EF3
X-MachineName: mtsvc000009
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-MSEdge-Ref: Ref A: 926B36EEE3D542398363823A987E9EF3 Ref B: SYD03EDGE0212 Ref C: 2020-09-01T04:06:45Z
Date: Tue, 01 Sep 2020 04:06:44 GMT
Content-Length: 45

{"errorCode":"UnableToParseTeamsAppManifest"}

Can i have localization in manifest for names/descriptions of custom tabs, default tabs (like About)

The schema & the documentation state that the version must follow the semver standard (http://semver.org). However the app Upload throws 400 BadRequest when providing e.g. 1.1.0-preview.1 which is valid by semver.

This changed recently as 2 weeks ago we were able to update our teams app with "1.5.2-preview.1" but now we can't upload a new manifest with 1.5.2-preview.2

It seems that both the documentation and the JSON schema are not consistent with what the API actually expects (MAJOR.MINOR.PATCH only)

1.7 localization in manifest not working as expected:

• Manifest:
  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.7/MicrosoftTeams.schema.json",
  "manifestVersion": "1.7",
  "version": "1.0.12",
  "id": "69bac8e5-774e-41fa-90c6-59056ddf0c6f",
  "packageName": "com.kpmg.find",
  "localizationInfo": {
  "defaultLanguageTag": "en",
  "additionalLanguages": [
  {
  "languageTag": "de",
  "file": "de.json"
  }
  ]
  },...
  "name": {
  "short": "KPMG Find",
  "full": "KPMG Find Application"
  },
  "description": {
  "short": "test1",
  "full": "test2"
  },...

• de.json:
  {
  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.7/MicrosoftTeams.Localization.schema.json",
  "name.short": "test3",
  "name.full": "test4",
  "description.short": "test5",
  "description.full": "test6",
  "staticTabs[0].name": "test7"
  }

When loading the app with MS Teams configured in German:

The displayed description is always test1, test2, so short and full description properties specified in manifest.json, and not test5 and test6, specified in de.json file.

Attached the complete manifest. Thanks in advanced for the support!
KPMGFindLocal.zip

https://developer.microsoft.com/en-us/json-schemas/teams/v1.14/MicrosoftTeams.schema.json is being referred by dev.teams.microsoft.com, but is not there.

There is a manifest version 1.17, but there is no release notes for it. Could you add those?

Shouldn't this be a required field? It is in the example provided by @akinolugbade

Getting this issue when i try to upload the manfest zip file. using below manifet file

{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.5/MicrosoftTeams.schema.json",
"version": "1.0.0",
"manifestVersion": "1.5",
"id": "d55d08d9-bacb-4567-942f-afd85d632dcc",
"packageName": "com.microsoft.teams.icebreaker",
"name": {
"short": "Icebreaker",
"full": "Icebreaker Bot For Cocentric Employees, Icebreaker1 Bot For Cocentric Employees"
},
"developer": {
"name": "cocentric",
"websiteUrl": "https://www.cocentric.com",
"privacyUrl": "https://www.cocentric.com/privacy-policy",
"termsOfUseUrl": "https://www.cocentric.com/privacy-policy"
},
"description": {
"short": "Icebreaker is a bot that randomly pairs team members up to build team unity.",
"full": "Icebreaker is a cute little bot that randomly pairs team members up every week to help the team build trust and personal connections."
},
"icons": { "outline": "outline.png", "color": "color.png" },
"accentColor": "#64A2CC",
"bots": [
{
"botId": "{id}",
"scopes": ["personal", "team"],
"isNotificationOnly": true,
"supportsFiles": false,
"supportsCalling":false
}
],
"validDomains": ["icebreaker-bdwdukbzhgoce.azurewebsites.net"],
"localizationInfo": {
"defaultLanguageTag": "en",
"additionalLanguages": [
{ "languageTag": "en", "file": "en.json" },
{ "languageTag": "de", "file": "de.json" },
{ "languageTag": "fr", "file": "fr.json" },
{ "languageTag": "ar", "file": "ar.json" },
{ "languageTag": "ja", "file": "ja.json" },
{ "languageTag": "es", "file": "es.json" },
{ "languageTag": "he", "file": "he.json" },
{ "languageTag": "ko", "file": "ko.json" },
{ "languageTag": "pt-BR", "file": "pt-BR.json" },
{ "languageTag": "ru", "file": "ru.json" },
{ "languageTag": "zh-CN", "file": "zh-CN.json" },
{ "languageTag": "zh-TW", "file": "zh-TW.json" }
]
}
}