SOTI Pulse Logo

Unable to install application with managed configuration

CS
Chris S

Due to the Android 11 restrictions, we're currently attempting to switch to using managed configuration for our application. When updating the application to include the managed configuration, we're able to upload to the SOTI MobiControl as an enterprise application and configure the default settings for the application. However, every time we attempt to install the package we're receiving "Failed to download %s". 

Where would we be able to find more information regarding why the application is failing to download and install on the application? We're able to install the applications manually on other devices that are not within SOTI MobiControl.

a year ago
SOTI MobiControl
ANSWERS
RC
Raymond Chan Diamond Contributor
a year ago

What are the brand and model of your devices of interest?

Did you create the .pcg package with Package Studio utility .exe or just drag and drop an apk to relevant area in the web-console to get the uploaded app converted automatically into the required .pcg?

Were you able to install the app (in the .pcg enterprise app package) on any enrolled devices if the "managed configuration" option was not enabled?

Had the app already been installed as non-managed app (e.g. with personal Google account configured) on your problematic device before relevant app policy was deployed to the device as "managed app"?

Have you checked the MobiControl DS server log file and device agent log file for more details related to the app deployment problems?

MK
Martin K.
a year ago

We also see this error message from time to time when we dsitribute Enterprise Apps with an App Policy, sometimes multiple checkin and device reboots helped, sometimes we had to erase and reenroll the device.

This whole App Policy function is a big black hole, as there are almost no log files, so you cannot lock why the distribution failed.

Send the policy to exp 50 similiar devices, 45 install the app, 5 not.

MD
Matt Dermody Diamond Contributor
a year ago

Agreed! Very unpredictable and unreliable. Also no Force Package Reinstallation equivalent if you want to reinstall an app or force the Managed Configuration again. I use Package based APK installation every where I possibly can given the added control. 

MK
Martin K.
a year ago

I am glad we are not the only ones that have seen this unfortunate behaviour. We have to use app policies for a specific app, because Managed config is the only way to configure it, configuration with files was removed, after Soti offerend managed enterprise app policies, during development everything looked fine, just as we go to broader rollout we have seen the issues and that app policies is a big black hole. And no policy duplication and the issue of getting wrong configuration if you delete and readd a newer version of the app.

CS
Chris S
a year ago

Thanks for the additional information! Sounds like it may not be worth the hassle of moving towards the managed configuration which is unfortunate. 

We're utilizing lockdown/shared devices, so we're looking for an alternative way to get the user logged in. Previously we were told the correct and easiest way to do this was using the managed configuration but we ended up using an custom .pcg file to write the %ENROLLED_USERNAME% value to a text file that our application can read. Sounds like we'll just have to work through moving the directory that we're utilizing to write that value to Documents or one of the public folders to avoid installation issues.

A
ABMOD@SOTI
a year ago

Hi Chris S,

Thanks for posting on SOTI Pulse, Thanks Raymond, Martin K, and Matt Dermody for responding to the post, your expertise and willingness to help are greatly appreciated!

Apologies from our side, for this particular issue we need to investigate further.

We request you to please raise a support case at log a case so that our agent can work on your query as quickly as possible.

 

Similar Discussions