No Matches Found!
Try with a different search term
Is there any way that when uploading custom APK into Mobicontol that that it will recoginzed the app version and build number. That way we can use that for versioning our apps. While testing them. Otherwise we have to delete the app and policy before we can upload the newer version. The system only recognizes app version and not build.
You can see it in the enterprise app policy (at least the version):
And if you upload apk files to packages it uses the apk version there as well:
These screenshots are taken from 2024.1.1
Yes, I understand the version information. However, when you upload an custom apk. If the version of the app is 3.1.0 and the build is 2300. The version is the only information that is added. If the developer releases an apk 3.1.0 with build 3200. Mobicontrol will not let you upload the app because it already exists.. Then you have to remove it from all policies and delete the app. Then upload the new build and apply all policy. Instead of just choosing which build.
I think in this case you would need to add the buildnumber to the version in order to get this done.
So your two app versions then finally become 3.1.0.2300 and 3.1.0.3200 or as Soti seem to do it: 3.1.0 Build 3200..
You would have more control over the apk's and versions of your apps by using a package and Soti's package manager to build the .apk into a package (.pcg) file. There you can specify your own versions, (which would presumably match whatever version and build you want), and you would only need to be concerned with the wrap field within the .mcp file which would need to be higher than the previous version of the package. Hope this helps.