Teams custom app update not propagated to users and store

Question

I have a problem updating a custom app in Microsoft Teams (scope "personal"). I changed the manifest (added some tabs, increased the version, kept the app-id). I uploaded the new package in the Teams admin center under https://admin.teams.microsoft.com/policies/manage-apps/{app-id}

In Teams admin center I can now see the increased version number and description. The app is shown as published and allowed to be used. Also I have no pending approvals. But when I open my personal custom app in the Teams client or browser the app is not updated. (Old version number, old description,...). Same in the store under "Apps developed for your organization". Old version, old description.

I already put the app-package through the validator and everything was perfect. I also waited >24 hours and now am out of ideas where to look.

Any suggestions how I can get my updated app?

Ben

How did you install the app originally? Through the company store, or through App Studio? — Hilton Giesenow
I’m sorry, but I don’t remember. It’s been over a year ago. Would this have any impact? — ben
Also deleting and re-installing the app isn’t an option, because the app was rolled out to ~1600 user by policy and the effects are unclear — ben
After thinking about your question, I think it was published through app studio. — ben

Hilton Giesenow Hilton Giesenow · Accepted Answer · 2020-12-29T08:26:22

Based on the chat above, I think the issue is you kind of have two "duplicate" deployments of the app - one deployed through App Studio, and one deployed through the "company store". If you just want, simply, to update your app, then do it through App Studio - either make the changes there and redeploy, or DELETE your app in App Studio and re-import using the new manifest (then redeploy from there). Alternatively, if you want to test the "normal user" install/update cycle, then DELETE the app installation itself (right click the app in the left menu and uninstall), then delete the app in the Admin centre, install the old version into there, install it for the user, test the upgrade, etc. (bit of a business). Basically, this is why to have a separate 'Dev tenancy' :-).

On that note, if your company is a Microsoft Partner, you might have access to multiple temporary test tenants.

Teams custom app update not propagated to users and store

1 Answers