Open
Description
Im unsure where to give information about this bug, whether it is an documentation error or teams-api error.
In the V1.16 schema for TeamsApps teams/v1.16/MicrosoftTeams.schema.json there is the version described as:
"version": {
"type": "string",
"description": "The version of the app. Changes to your manifest should cause a version change. This version string must follow the semver standard (http://semver.org).",
"maxLength": 256
},
On http://semver.org the version can be:
<valid semver> ::= <version core>
| <version core> "-" <pre-release>
| <version core> "+" <build>
| <version core> "-" <pre-release> "+" <build>
<version core> ::= <major> "." <minor> "." <patch>
<build> ::= <dot-separated build identifiers>
// removed for brevity
-> So the version "version": "1.0.0+20240226"
should be valid.
With "manifestVersion": "1.15",
this works as expected.
But with "manifestVersion": "1.16",
we get an error from the admin Teams UI "Upload a custom app" (Post https://graph.microsoft.com/beta/appCatalogs/teamsApps) results in 400 error.
{
"error": {
"code": "BadRequest",
"message": "App version supports only numbers in the '#.#.#' format.",
"innerError": {
"code": "UnableToParseTeamsAppManifest",
"message": "App version supports only numbers in the '#.#.#' format.",
"details": [
{
"code": "VersionContainsOnlyNumbersDotSeparated",
"message": "App version supports only numbers in the '#.#.#' format."
}
],
"date": "2024-02-26T15:52:35",
"request-id": "d65a27a7-84d7-4d31-b080-5d589b692a8b",
"client-request-id": "d65a27a7-84d7-4d31-b080-5d589b692a8b"
}
}
}
Metadata
Metadata
Assignees
Labels
No labels