Can't activate apps on other devices

WC
Walter Cunayque
DSB Mobile SAC

Hello good day,

I have a problem when activating applications that were hidden and use a script that allows to activate but the problem I have is that in some devices of the same model they do not activate and it throws an error in the logs.

Manufacturer: samsung Model: SM-A105M

The script I send is: writeprivateprofstring BlockedActivityList

The error message sent by the device: Error message received from device (Failed to parse XML file(IOException) /test)

In some devices of the same model the applications are activated and in other models it does not and sends that error message.

Has anyone had the same problem and had a solution? I'll stay tuned to your comments

   
Edited 5 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
5 years ago

The script command

     writeprivateprofstring BlockedActivityList

is not used to unhide hidden applications.

Please elaborate in more details what you want to do and what is shown on the device screen or in the log tab of your device in the MobiControl web-console.

WC
Walter Cunayque
5 years ago

Hello Raymond,

I have used the script to enable native applications even for public applications that were also hidden, the script was sent to several devices of the same model, in some they were shown and others were not, and in those devices that do not show the applications they return an error message.

This is the error message that the device returns every time I send the script

device error message after sending script

I did the test sent this other script and the result is the same.

another test send script

RC
Raymond Chan Diamond Contributor
5 years ago

Hi Walter,

Your first post using terms like "hide" and "activate" caused confusions.    Based on your log screenshots in the last post,  I can confirm that you actually used related script commands to change the application-run-control (ARC) whitelists/blacklists.  This use is proper, but your terminology used is inaccurate and misleading.

Without the details of the sequence/history and actual arguments used in the script commands, it is difficult to nail down why you have problem in some devices and not in others.   In general,  some related options in feature-control and lockdown-menu, together with the current states of ARC parameters on a device, will affect the overalll application run control policies.  The syntax and argument(s) of your script command may also affect the overall results.   

So, if those devices that have problems are in different device group or have different FC/lockdown and/or have different deployed ARC script command history compared to those devices with no problem, then you have to find out which difference actually causes the problem.