Welcome to Headwind MDM Q&A, where you can ask questions and receive answers from other members of the community.

Please do not post bug reports, missing feature requests, or demo inquiries. If you have such an inquiry, submit a contact form.

0 votes
I have one app that is getting regular updates...problem is that when i try to push the update, phones keeps the old version.

Example...i have the version 2.1.1 of my app and we develop the version 2.1.4...i upload the new version into HMDM successfully and in one test configuration we upgrade the version. when we refresh the phone, it "downloads" the file but keeps the 2.1.1 version.

We delete the app in the configuration and install again, same.

I delete the 2.1.1 version from the hmdm and keep only the 2.1.4, no luck

only after do a factory reset of the phone, redeploy into mdm, we can get the 2.1.4 version of the app.

What i am missing here?
by (140 points)

1 Answer

+1 vote
This issue is a possible duplicate of https://qa.h-mdm.com/5207/

The most probable reason that app can't be updated is a different app signature (in most cases, this is because you messed up debug and release signature keys).

The preferred option is to sign the updated app with the same keys as the previous version.

You an also force uninstalling the previous version before installing a new one: https://qa.h-mdm.com/1954/
by (37.6k points)
I found it around one hour ago of keeping both versions but the 2.1.1 in "delete" for the test group and the 2.1.4 in "install" for the same group...worked like a charm.
...