Unable to update teams custom application

Copper Contributor

I am facing issue on updating existing application by uploading the new version of custom teams app. However, it works fine when I upload the custom teams app as a new application.

 

Steps to reproduce:

1. Upload a new teams manifest

2. Change the version in the manifest

3. Upload the updated manifest over the existing application

At this point, I see a success screen. However, the new version is not getting reflected on the teams admin portal.

4. Try to upload the same manifest over the existing application again.

At this point, I see the following error screen:

MicrosoftTeams-image.png

 

Following is the response that I got from the debugger console:

 

While uploading newer version of the app: 

It says success but the changes are not reflected.

 

HTTP/1.1 204 No Content Strict-Transport-Security: max-age=31536000 request-id: 0b34abc7-c31c-48ae-a32d-fcf3922c7003 client-request-id: 0b34abc7-c31c-48ae-a32d-fcf3922c7003 x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"West US","Slice":"E","Ring":"4","ScaleUnit":"001","RoleInstance":"BY1PEPF0000432C"}} Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Location, Preference-Applied, Content-Range, request-id, client-request-id, ReadWriteConsistencyToken, SdkVersion, WWW-Authenticate, x-ms-client-gcc-tenant Date: Fri, 17 Jun 2022 07:12:02 GMT

 

While uploading newer version of the app again:

HTTP/1.1 409 Conflict Transfer-Encoding: chunked Content-Type: application/json Content-Encoding: gzip Vary: Accept-Encoding Strict-Transport-Security: max-age=31536000 request-id: 2f2a88c4-09bd-4643-a6ab-30db4df5a336 client-request-id: 2f2a88c4-09bd-4643-a6ab-30db4df5a336 x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"South India","Slice":"E","Ring":"2","ScaleUnit":"001","RoleInstance":"MA1PEPF00002AFE"}} Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Location, Preference-Applied, Content-Range, request-id, client-request-id, ReadWriteConsistencyToken, SdkVersion, WWW-Authenticate, x-ms-client-gcc-tenant Date: Fri, 17 Jun 2022 07:17:11 GMT

 

{"error":{"code":"Conflict","message":"Update tenant app definition manifest version exists. UserId: '7cb50835-b4bc-4747-ad95-01f8293a87e7', TenantId: '5d92f9c7-28de-46b2-b5ad-147395e589df', AppId: '25766d1a-3891-4155-a05f-ca671b230b93', ExternalId: '5e2d3260-19fe-22eb-9aff-6fb572e94051', exist app version: 3.7.0","innerError":{"message":"Update tenant app definition manifest version exists. UserId: '7cb50835-b4bc-4747-ad95-01f8293a87e7', TenantId: '5d92f9c7-28de-46b2-b5ad-147395e589df', AppId: '25766d1a-3891-4155-a05f-ca671b230b93', ExternalId: '5e2d3260-19fe-22eb-9aff-6fb572e94051', exist app version: 3.7.0","code":"TenantAppDefinitionManifestVersionAlreadyExists","innerError":{},"date":"2022-06-17T07:25:05","request-id":"b644c5ad-1031-4ff3-ae3e-66be5c14c9b1","client-request-id":"b644c5ad-1031-4ff3-ae3e-66be5c14c9b1"}}}

8 Replies

@IvanMaria - We are able to repro your issue. We have raised a bug for it. We will inform you once we have any updates.

@IvanMaria - We have informed engineering team. The team is looking into the issue. We will update you.
I am having this same issue; when we try to update the team's custom application, it tells us that it has been an error, and please try again; we are having the same behavior that the @IvanMaria posted over here. ---- It is literally the same issue.
@IvanMaria, @sblandon - We are actively checking the status of the bug fix. We will let you know once we get any updates from them.

@Nivedipa-MSFT  any update for this? i am facing the same issue. 

@IvanMaria, @Shaun Tukuafu - This bug has been fixed now. Could you please test this and confirm it.

Hi, I have the same Issue where it won't let me push an App Update, I've tried it through the Teams Desktop app on Windows and Mac as well as the Browser Admin Panel with the same result.
It'll let you publish a couple of Updates and then suddenly stop, the only way i found around it was to delete the entire App, Publish the sample App from Microsoft and change it to the back to my own app as an Update

@jpokorny - Sorry for delay in response.
Regarding this issue, bug has already been fixed and published.
Please do verify once and let us know the updates.