No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
We are trying to move away from Clasic Enrolment (where we have to side-load all the application via Profile / Package) to a more robust deployment (via Enterprise Google Play Store). I've managed to create the binding between the MDM and Google Play Store and get any application available in Google Play Store to get installed on the Work Profile (we are using COPE- Corporate - Personal Enrolment method). I was also able to upload a custom Android application via the same method. The issue surfaced when I've try to upgrade the custom application to a new version. When attempt to edit the custom application and load the new apk, I am getting Cannot update a published APK.
I have an application that I'm installing on our iPads using an app policy. I also have a profile that enables single-app mode pointing to that application. I have an issue where the single-app mode profile is kicking in before the application is installed, and it is throwing an error on my device. The only way around it is to wait for the application to finish installing, and then reboot the device. My question: Is it possible to have the profile kick in after the application is fully installed on the device?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
