No Matches Found!
Try with a different search term
Hello
When staging Android Plus devices, many times we get a failed package installation, or partial installation.
Usually with "File IO error on device" log.
We then go to Mobicontrol webconsole and do a "Force package reinstallation"
Then it works every time, without changing anything on the device, server or package.
Does anyone have any theory why this is happening?
Mobicontrol 15.5 server
Android 11 devices
Regards
Are you having devices using plugins?
If yes: Then it could be related to that for some reason the plugin installation happens too late (because installation of it fails as well at the beginning) so packages trying to store files on the system fail because Mobicontrol doesn't have access to those destinations because of permissions granted by the plugin are missing.
When you then try later the installation, the plugin is installed so the force reinstallation succeed.
You could try to provide the plugins via profile as well and create a dependency on the other (failing) profiles as well so they won't tried to be installed before the plugin is in place.
But this is just a guess.
Hi Per,
If many app packages are to be deployed when staging your Android plus devices of interest, your problem may be related to the order of installation of two or more related packages. These can be .apk enterprise package or managed app deployed from Google App store, and is not restricted to MobiControl plug-in as mentioned in earlier post.
Test different installation order manually to confirm. Once the required order is found, deployment related policies can be re-partitioned and ordered using filter expression(s) or device group(s).
To Raymond:
I never said its restricted to the plugin, i just mentioned a possibility we already saw ourselves in the past (question followed by a "could" (not a will be or similar!),...).
...
you start again shouting at others posts without reasons instead of just mentioning another possibility.
You have really a great knowledge but sometimes it's just *** what you wrote about someone others answer...
On A11+ the SOTI agent needs to have the MANAGE_EXTERNAL_STORAGE permission silently granted to it before it can perform any installation of file based packages. Unfortunately SOTI seems to have not built any intelligence into their solution to wait for this permission to be granted before attempting file based operations and therefore the agent will attempt to perform them before it is capable of doing so. This is likely what you're experiencing given that a force reinstall shortly after then works. This is typically evidence of the agent not having the permission in place during the first attempt and it then being there by the time you make the second manually reinstall attempt. A OEM Plugin often performs the job of silently granting this permission so you can sometimes add a dependency or filter on the bundle ID of the plugin as some way to introduce some order of operations to your package installs. On newer Zebra devices however they do not use the Plugin as frequently and instead rely on some built in MX commands to self grant these permissions. It is more difficult on these devices as a result to detect that the agent has the correct permission before enabling the assignment of file based packages. I think ultimately SOTI should just implement a more robust system to intelligently detect that the permission is granted and to wait until it is in place so that we as admins aren't stuck trying to come up with creative workarounds to the problem.
Hi Per Eriksson,
Thanks for posting on SOTI Pulse, Thanks Rafael, Matt and Raymond for responding to the post, your expertise and willingness to help are greatly appreciated!
Have you had an opportunity to see the information shared by Matt , Raymond and Rafael, and has it successfully addressed your query?
If not, or If you have any additional questions or concerns, please don't hesitate to reach out. We're dedicated to providing assistance and support.
Hey Per,
have you created after the Failed installation to get a "Debug Report" from the Device?
Manually installing on the Device is working Fine ?
Do you have configured "dependencies" in your Profile ?
Last Question:
Is it a self Developt app or a Regular one what can be also assigned over the Playstore ?
Might with Android 11 Devices or higher soon - to think about to Update your Enviroment to 15.6.6 ?