apk installation failed
The first thing I would check is to try copying and installing the apk file originally included in your pcg package directly onto the device to see if the apk is compatible with your device firmware.
I have two similar C-five device with the same Os version, software and hardware configurations.
The apk is correctly installed on the first device but failed on the second.
BRUNO RAME Project Deployment Coordinator / SOTI Mobicontrol Specialist
File IO error can also occur if you are attempting to perform a direct upgrade over a previous version of the Android app. The following conditions must be met in order for that to be successful
- The new version of the APK must literally be a new version, with an incremented APK version
- The new version of the APK must be signed the same way as the previous version
- I believe you also need to have the new APK built using the original SOTI Package MCP or at least match the name, but with an updated package version.
If those conditions are not met then SOTI will not be able to install the APK until the previous version is removed. This can be accomplished with a Pre-install script built into the new APK delivery package that uninstalls any pre-existing versions. Note that this will have the effect of wiping out the App Cache and resetting any previously granted App permissions which may not be desirable.
More info on the recommended process:
If you failed to install the manually copied apk file directly (i.e. not with MobiControl pcg) on one device, then you can narrow down the actual cause(s) as follows:
1. compare the following between functional and problematic devices:
- device agent version and build numbers
- whether there is sufficient free memory space in the problematic device
- the permission settings enabled for the device agent
- whether there is any difference in the profile(s)/rule(s) "deployed" to the devices (especially if the devices reside in different device groups), and the actual status of the profile
- the version/build numbers of the installed app to be upgraded
- whether the apps to be upgraded were installed with the same method/procedure in the past
2. check if you have the same problem with the apk in other device brands/models. Sometimes, poorly implemented apk is the actual cause of the problem.
Thanks for referencing
in which I interacted with Christophe on similar installation problem some time ago.
However, I have to clarify one of your point, namely
The new version of the APK must literally be a new version, with an incremented APK version
Actually, for apk deployment with MobiControl pcg package, the new apk version need not be higher than the app version already installed. This means that MoibControl pcg deployment mechanism allow administrator to enforce apk downgrade. I did tests on v10/11 years ago to confirm this, but I don't know if there has been any change in more recent MobiControl versions.
I also notice a small number of Android device brands/modesl have firmwares that only allow app to be upgraded in-place, and app downgrade can only be done by first uninstalling the installed version completely. However, this is not the case for most top Android device brands.