Uploading a new apk file with a different package name to managed Google Play: A step-by-step guide
How to Upload a New APK File with a Different Package Name to Managed Google Play
If you are an enterprise or an organization that wants to distribute your Android apps privately and securely to your employees or customers, you might want to use Managed Google Play. Managed Google Play is a version of Google Play that allows you to control which apps are available for your users, and how they are installed and updated on their devices.
managed google play upload a new apk file with a different package name
An Android application package (APK) is the file format that Android uses to distribute and install apps. Each APK file contains the code, resources, assets, and manifest of your app. When you upload an APK file to Managed Google Play, it becomes an app that you can manage and distribute through your enterprise mobility management (EMM) console.
Sometimes, you might need to upload a new APK file with a different package name to Managed Google Play. A package name is a unique identifier for your app that follows the reverse domain name notation (e.g., com.example.myapp). You might want to change your package name if:
You want to create a new version of your app that is separate from the existing one.
You want to avoid conflicts with other apps that have the same package name.
You want to comply with the Google Play policies and guidelines.
In this article, we will show you how to upload a new APK file with a different package name to Managed Google Play in three easy steps. We will also provide some tips and troubleshooting solutions for common issues that might arise during the process.
Prerequisites
Before you upload a new APK file with a different package name to Managed Google Play, you need to have the following:
A Google Play Developer account that is linked to your EMM console.
An Android app project that you can edit and build using Android Studio or another tool.
A valid key store and key alias that you can use to sign your APK file.
A different package name that is globally unique in Google Play (not just within your enterprise or Google Play Developer account).
Steps to Upload a New APK File with a Different Package Name
Here are the steps you need to follow to upload a new APK file with a different package name to Managed Google Play:
Step 1: Create a new app in the Play Console or managed Play iframe
The first step to upload a new APK file with a different package name is to create a new app entry in the Play Console or managed Play iframe. This is where you will provide the basic information and settings for your app, such as the title, description, category, pricing, and distribution options.
To create a new app in the Play Console, follow these steps:
How to upload a new apk file with a different package name to managed google play
Managed google play private app upload error: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Intune
Managed google play app update: how to change the package name of an apk file
Troubleshooting managed google play app publishing: upload a new apk file with a different package name
Best practices for uploading a new apk file with a different package name to managed google play
Managed google play app approval process: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Citrix Xenmobile
Managed google play app synchronization: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise devices
Managed google play app management: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Google's iFrame
Managed google play app deployment: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise kiosk devices
Managed google play app permissions: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Microsoft Authenticator
Managed google play app reporting: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise work profile devices
Managed google play app testing: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Microsoft Intune
Managed google play app deletion: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise fully managed devices
Managed google play app assignment: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Managed Home Screen
Managed google play app update frequency: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise dedicated devices
Managed google play app types: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Intune Company Portal
Managed google play app categories: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise personally-owned devices
Managed google play app collections: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play using Google Play Console
Managed google play app ratings and reviews: upload a new apk file with a different package name
Upload a new apk file with a different package name to managed google play for Android Enterprise corporate-owned devices
Managed google play app icons and screenshots: upload a new apk file with a different package name
Open Play Console and sign in with your Google Play Developer account.
Select All apps > Create app.
Select a default language and add the name of your app as you want it to appear on Google Play. You can change this later.
Specify whether your application is an app or a game. You can change this later.
Specify whether your application is free or paid.
Add an email address that Play Store users can use to contact you about this application.
In the "Declarations" section, acknowledge the Developer Program Policies and US export laws declarations.
Accept the Play App Signing Terms of Service.
Select Create app.
To create a new app in the managed Play iframe, follow these steps:
Open your EMM console and sign in with your admin account.
Select Managed Google Play > Apps > Add app > Create new app.
Select a default language and add the name of your app as you want it to appear on Google Play. You can change this later.
Specify whether your application is an app or a game. You can change this later.
Specify whether your application is free or paid.
Add an email address that Play Store users can use to contact you about this application.
In the "Declarations" section, acknowledge the Developer Program Policies and US export laws declarations.
Accept the Play App Signing Terms of Service.
Select Create app.
Step 2: Generate a signed APK with a different package name
The next step is to generate a signed APK with a different package name using Android Studio or another tool. A signed APK is an APK that has been digitally signed with a certificate that proves its authenticity and integrity. You need to sign your APK with a valid key store and key alias before you can upload it to Google Play.
To generate a signed APK with a different package name using Android Studio, follow these steps:
Open your Android app project in Android Studio and select Build > Generate Signed Bundle / APK.
Choose APK in the pop-up and click on Next.
If you already have a key store and key alias, select Choose existing and browse to their locations. If you don't have them, select Create new and fill in the required fields. Make sure you remember the passwords and keep the key store file in a safe place.
Click Next and select the build variant (release or debug) and the destination folder for your signed APK. You can also enable signature versions (V1 or V2) and ProGuard settings if you want.
Click Finish and wait for Android Studio to generate your signed APK.
To check the package name and signature of your APK, you can use the apksigner tool or the bundletool command-line tool. For example, you can run the following command:
apksigner verify --print-certs --verbose my-app.apk
This will print out information such as the package name, signer certificate, digest algorithm, signature scheme, etc. You can compare this information with your previous APK file to make sure they are different.
Step 3: Upload your APK to the Play Console or managed Play iframe
The final step is to upload your APK to the Play Console or managed Play iframe, and review and publish your app. This is where you will provide more details and assets for your app's st