Forum Discussion
omer-astrix
Apr 01, 2024Copper Contributor
Getting BadRequest on UploadDocumentContentRequest when trying to update custom app
Hello
I'm trying to update a custom app in teams admin center, and get the following error:
{
"error": {
"code": "BadRequest",
"message": "Failed to execute AMS backend request UploadDocumentContentRequest. Workload Unknown. Request Url: https://eu-prod.asyncgw.teams.microsoft.com/v1/objects/0-weu-d20-f5f8f6a3978eb61dc1099a988f43c649/content/imgpsh, Request Method: PUT, Response Status Code: BadRequest, Response Headers: MS-CV: f1yATjqU5kWPwk7PIPw9aw.0\r\nX-Instance-Id: ic3-asyncmedia-storage-facek-deployment-8ccdf4cdd-6zb5k\r\nX-Source-Port: 38345\r\nX-Destination-Port: 443\r\nStrict-Transport-Security: max-age=2592000; includeSubDomains\r\nX-MSEdge-Ref: Ref A: 59811B1BA5624DF7931A56DD5E8D5EB2 Ref B: AMS04EDGE2612 Ref C: 2024-04-01T18:51:41Z\r\nDate: Mon, 01 Apr 2024 18:51:41 GMT\r\n, Reason Phrase: Bad Request, Request ID 108E1371CFAC4C4CB77277454C3F8D4A.",
"innerError": {
"code": "UnknownTeamsAppManifestExceptionType",
"message": "Failed to execute AMS backend request UploadDocumentContentRequest. Workload Unknown. Request Url: https://eu-prod.asyncgw.teams.microsoft.com/v1/objects/0-weu-d20-f5f8f6a3978eb61dc1099a988f43c649/content/imgpsh, Request Method: PUT, Response Status Code: BadRequest, Response Headers: MS-CV: f1yATjqU5kWPwk7PIPw9aw.0\r\nX-Instance-Id: ic3-asyncmedia-storage-facek-deployment-8ccdf4cdd-6zb5k\r\nX-Source-Port: 38345\r\nX-Destination-Port: 443\r\nStrict-Transport-Security: max-age=2592000; includeSubDomains\r\nX-MSEdge-Ref: Ref A: 59811B1BA5624DF7931A56DD5E8D5EB2 Ref B: AMS04EDGE2612 Ref C: 2024-04-01T18:51:41Z\r\nDate: Mon, 01 Apr 2024 18:51:41 GMT\r\n, Reason Phrase: Bad Request, Request ID 108E1371CFAC4C4CB77277454C3F8D4A.",
"details": [],
"date": "2024-04-01T18:51:41",
"request-id": "106b0c59-8e09-4b8b-9c53-0cfac9a533f5",
"client-request-id": "106b0c59-8e09-4b8b-9c53-0cfac9a533f5"
}
}
}
Please advise
Thanks
2 Replies
Sort By
- omer-astrixCopper Contributor
This is still happens
The mainfest:
{ "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json", "version": "1.0.3", "manifestVersion": "1.16", "id": ..., "packageName": "com.package.name", "name": { "short": ..., "full": "" }, "developer": { "name": ..., "mpnId": "", "websiteUrl": ..., "privacyUrl": ..., "termsOfUseUrl": ... }, "description": { "short": ..., "full": ... }, "icons": { "outline": "outline.png", "color": "color.png" }, "accentColor": "#0084ff", "bots": [ { "botId": ..., "scopes": [ "team" ], "isNotificationOnly": false, "supportsCalling": false, "supportsVideo": false, "supportsFiles": false } ], "validDomains": [], "webApplicationInfo": { "id": ..., "resource": "" }, "devicePermissions": [ "notifications" ], "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Group", "type": "Application" } ] } } }
- ChetanSharma-msft
Microsoft
Hello omer-astrix - Thanks for raising your query.
Please share complete manifest, so that we can directly upload and test it.
Also, please let us know the repro steps if any.