Differnt behaviour when installing with mxconfig and app permissions

Differnt behaviour when installing with mxconfig and app permissions

Hi,

I already read some forum posts about this topic.

It should be possible to install an application and grant the needed permissions if the application is installed with mxconfig and a StageNow xml file. 

I tested this in two ways:

1) manually copy the apk file and xml file (AppMgr to install the apk) to the device. Send script via Soti MobiControl with mxconfig xml file. The application is installed on the device with the needed permissions.

2) Building a Soti package with MC Studio. Copying the files to the device and include a postinstall script. The mxconfig command is in the postinstall script, same command as in 1). The application is installed, but doesn't get the needed permissions automatically like in 1).

I tested differnt applications, same behaviour as mentioned above.

Does anyone have an idea why this isn' working?

Device is Zebra TC56, Android 7.1.2 with Update19 (Non GMS), Agent version 13.7.0.1031.

Soti MobiControl version is 14.3.0.3144.

 

Thanks.

 

6 Answers

Order By:   Standard | Newest | Votes
Matt Dermody | posted this 07 August 2019

You’re on the right track. Did you add the APK to your Package as an APK or as a file? It needs to be added as a File instead of as an APK otherwise SOTI will perform the installation for you before the Mxconfig script is kicked off. I haven’t done this in a while but you may even have to rename it to something other than .apk and then use a script to rename it back before calling mxconfig just so SOTI doesn’t recognize it as an APK and install it for you. I would start with just trying to add it as a file.

  • 1
  • 0
Stefan Devernon | posted this 08 August 2019

Hi Matt. Thanks for your help.

It worked with the renaming of the apk extension and a copy command to copy the file with the correct extension.

Now I got another unusual behavior. This is off topic but maybe you know a solution for this too.

I'm installing the Enterprise Home Screen from Zebra with the package on the devices. In the postinstall script, there is an install command for the EHS and a reboot command. 

This is working fine.

Now the problem occurs, when the device gets dropped in another device group (with no profile for example). 

I guess because of the install command for the EHS in the postinstallscript, the EHS will be automatically deinstalled when the profile gets deinstalled. Now when I'm rebooting the device, it gets locked in the bootscreen and stays there. Only resetting the device with the boot loader is fixing this. Do you have any ideas about this?

I will do more testing tomorrow and will write back my results.

 

  • 0
  • 0
Matt Dermody | posted this 08 August 2019

Can you start a new thread with that exact comment?

  • 0
  • 0
Johan W | posted this 08 August 2019

Hi Matt!

This has stopped working for us. Running on WT6000 devices.

The app permissions are not accepted automatically when using AppMgr to install the APK.
The app we are trying to install is of course SOTI Surf with it's permissions.

  • 0
  • 0
Johan W | posted this 08 August 2019

Hi Matt!

This has stopped working for us. Running on WT6000 devices.

The app permissions are not accepted automatically when using AppMgr to install the APK.
The app we are trying to install is of course SOTI Surf with it's permissions.

 

Found the problem! Package Studio identifies the .APK file as an APK Android APK and not as a file, even when adding the .APK as a file.

Solution, add the .APK as .APK_ and use post-install script to copy the file to a new file with only .APK as extension, and then delete the .APK_ file. After that, mxconfig as usual.

Problem solved! =)

  • 2
  • 0
Ian Stuart | posted this 19 December 2019

Thank you for this! This was the one step I was missing.

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback