This could be concerning for ISVs who may be the true owner of the app and someone uploaded it privately to Google Play first and as a result they need to rename their app package and upload from that point on.ĭetails on publishing an app via Google Play: Therefore, Google Play does not allow other ISVs to reuse the same package name as it would lead to unexpected and insecure behavior.
#Managed google play update
Google has stated once an app is uploaded to the Play store and installed on devices, “unpublishing” the app prevents new users from installing the app, however existing app users are still be able to use the app and even update the app to its latest version. The reason for the error is Google Play doesn’t allow more than one app to reside in the service with same package name.Īnother issue we’ve seen is when customers have uploaded the ISV app privately via Intune or through their Google Developer account and when this occurs, the ISV cannot upload it anymore and are required to change the app package name and upload it to Google Play through their Google Developer environment.
#Managed google play registration
The registration fee is $25 and details may be found here: īy utilizing Managed Google Play with Android Enterprise enrollments, some organizations are beginning to experience errors when they attempt to upload an app an ISV provided (.apk) that already exists in Google Play (public or privately published). Using the Developer Console requires ISVs and app devs to register for a Google Play Developer account. This option is better suited to 3rd parties and ISVs that want to make their apps accessible to multiple organizations. Upload apps thru the Developer Console in Google Play.Upload through the Managed Google Play iframe inside Intune – best suited for companies uploading internally developed apps.
To upload apps to Google Play, Google offers two options: Utilizing MGP to manage app versions and distribution is new to many ISVs and customers and is requiring them to rethink their app distribution processes and leverage MGP vs distributing individual. According to Google deploying through MGP helps ISVs manage versions more easily and provides app scanning during upload to help find vulnerabilities and poor coding practices. This scenario has worked well with Android Device Admin enrollments however, with Device Owner enrollments (Android Enterprise) Google is recommending a more secure way to distribute apps for all Android Enterprise enrollment scenarios through Managed Google Play (MGP). Traditionally, organizations who are issued apps from ISVs and/or are creating their own LOB apps distribute them by uploading the apps to their EMM console and deploying them to Android devices. This month’s post focuses on managing 3 rd party and/or LOB apps with Google Play and distributing those apps to Android devices enrolled via Device Owner (i.e.
0 kommentar(er)
