SOTI Pulse Logo

APK installation in Work Managed Profile (Android Enterprise)

SB
Simon Breuer
REWE Systems GmbH

Hello!

I'm struggling with the installation of APKs into the work container of Android Enterprise (work managed profile on Samsung S9, Android 9).

Installation via package in a profile doesn't work as well as the installation via Application Catalog (Enterprise Application).

How can we install APKs into the work container?

The log shows following errors:

8:47:32
Error
Profile "Test_AE - Pre-installed Apps" version 4 failed to install, because all of its payloads cannot be installed.

8:47:32
Error
Package "XXXXXXXXX" version 1.0 failed to install. File IO error on device. Check Storage/Permissions.

8:47:32
Error
Error message received from device (Installierung der Anwendung XXXXXXXX von Paket XXXXXXX.pcg Fehlgeschlagen)
android-enterprise
Edited 6 years ago
Android
ANSWERS
C
Christophe
6 years ago (edited 6 years ago)

Hello simon,

i'm not an expert but perhpas the app you try to install do not ASK the permission !

Is it possible for your team to modify the source of the apk and try ?

SB
Simon Breuer
6 years ago

Hi Christophe,

unfortunately none of the APKs we tried can be installed. We tried various apps from different publishers. :(

ER
emanuel Rodriguez
6 years ago

Hi, 

Im having the same error. Is there any update about this?

S
Scott
6 years ago

Put one of the devices into debug mode and view the log after the installation attempt.  It's possible that play protect is killing you.  I believe something "INSTALL_FAILED_VERIFICATION_FAILURE" will be in the device log.

D
DDMOD@SOTI
5 years ago (edited 5 years ago)

Hello Simon,

Thank you for requesting a response from SOTI Support Staff.

This is a known issue on Android OS6 and OS9 and our development team are working on the fix. I will update you on this post once the resolution is available.

 

J
JVMOD@SOTI
5 years ago

Hello Simon,


Following up on this thread, were you able to resolve the issue? If yes, I would like to know what were the steps taken to resolve the issue and I can mark that as a Solution.

If not, can you please try to use 14.4.0 agent version and see if you were able to resolve the issue?


Regards,

Similar Discussions