Can't install MS Teams through SOTI package

W
WGKWVL_DV
Wit-Gele Kruis West-Vlaanderen

Hi,

We are using SOTI v13.4.0.5276 on production and SOTI v15.1.0.3416 on our testenvironment

(issue is present on both environments)

Created a package with com.microsoft.teams_1416_1.0.0.2020111001.apk (we use this method also for many other .apk)

Our devices (approx.1500) have a lockdown screen, no access tot Google Play Store and the end-user no access to the device settings.

Devices are Panasonic FZ-AZ (Android 6.0.1)

On devices with the lockdown screen temporary lifted installation seems to go, but on other devices: SOTI states 'installed' but the app is actually not installated.

During installation we don't get any indication on what is going wrong.

Any ideas/suggestions how to resolve/debug this ?

Regards,

Dirk

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

Do you have the same problem for other device brand/model?  If the problem is specific to Panasonic FZ-AZ,  maybe you should check the name(s) of any system app(s) or background service(s) run to during the app installation process when kiosk is not enabled.   Then, try to add the bundle-ID/activity name in your kiosk profile or application-run-control whitelist.

MD
Matt Dermody Diamond Contributor
4 years ago

Also where did you source the APK from? If you pulled it from an APK mirror or off a sample device it may not be a complete APK and may be missing components that would work on different devices. Meaning if you installed the APK on a different device model than the FZ-AZ and then extracted the APK from that device it may not be compatible.

Managed Play Distribution would at least ensure that a legitimate version of MS Teams was being installed on your devices, but it would also carry the risk of the app updating at any time without your control which I can understand the concerns around. 

W
WGKWVL_DV
4 years ago

Hi Matt,

Tried with 2 different APKs (1 from APKMIRROR and 1 from APKPURE)

Outside of our lockdown, we can install, from inside our lockdown, on most devices we can not.

(I don't think an incomplete APK is the cause of our problems)

W
WGKWVL_DV
4 years ago (edited 4 years ago)

Hi Raymond,

Tried with the process-viewer (in Remote control), unfortunatly no export possibilities (v13.4), only printscreens.

One process that isn't present in Lockdown mode is com.android.vending (Google Play Store). The process appears when the lockdown is lifted. I suspect installation might be failing because of the absence of this process (in Lockdown)?

Another process that temporarely pops up: com.android.defcontainer ('Helper package')

Dirk

MD
Matt Dermody Diamond Contributor
4 years ago

When the Lockdown and User Mode is active Application Run Control will be applied. It sounds like you may have a blacklist in Application Run Control that is restricting a lot of apps. You could remove them one by one from that blacklist to see what app may be leading to this condition. 

RC
Raymond Chan Diamond Contributor
4 years ago

For security and legal/licensing reasons,   would not recommend my customers to use apk file downloaded from APKMIRROR or APKPURE.

If your devices include any software similar to Google-Play-Protect to scan/filter out potential malware before installation of apk, make sure you have them properly configured/added in your Mobicontrol kiosk/ARC-whitelist.

 

VM
Victor Mung
4 years ago

I just ran into this recently, and it might be a similar issue. Check the Architecture of the APK. We had to use Teams on armeabi-v7a for an older device. APKmirror had these different builds listed under "variants"