Before publishing your private apps, make sure the Play Console or Managed Play iframe doesn't show any warnings or errors. Ignoring these may prevent your app from being published. We also recommend following these best practices:
- Your app's package name must be globally unique in Google Play (not just unique within your enterprise or Google Play Developer account). If your package name is the same as a package name already in Google Play, then recompile your app with a different package name.
- Google Play requires APKs to be byte aligned to optimize RAM usage. If your APK isn't byte aligned, you can use the zipalign tool to align your APK file.
- The key you use to sign your APK should have a long validity period. Read Signing considerations for more details.
- Why do I see “For uploading an App Bundle you must be enrolled in Play App Signing” error while uploading app bundle?
- The error occurs because you didn’t upload your app signing key yet. Follow instructions in Upload an AAB for a private app created with an APK section to upload your app signing key.
- Why do I see “You uploaded an APK or Android App Bundle that is signed with a key that is also used to sign APKs that are delivered to users. Because you are enrolled in Play App Signing, you should sign your APK or Android App Bundle with a new key before you upload it”?
- This error occurs when you create a new app by uploading an app bundle signed with an app signing (distribution) key used to sign other APKs. To solve this issue, you can:
- Use a new upload key to sign your app bundle before uploading it, or
- Create your new app by uploading an APK first and then switching to an app bundle following the instructions in Upload an AAB for a private app created with an APK.
- This error occurs when you create a new app by uploading an app bundle signed with an app signing (distribution) key used to sign other APKs. To solve this issue, you can:
- What should I do if I want to use my own signing key to sign the generated APKs delivered to end users?
- To solve this issue, you can:
- Use the Play Console to publish private app or
- From the managed Google Play iframe, upload the APK signed with your own signed key. Then upload the same app signing key to the Play Console. Then, follow instructions in Upload an AAB for a private app created with an APK section then you can start uploading the app bundle from iframe (or Play Console).
- To solve this issue, you can:
- What should I do if I want to use Google generated keys to sign the generated APKs delivered to end users?
- Creating an app using an app bundle from iframe will default to using a Google-generated signing key. No additional steps are required.
- Can I upgrade my app signing key after enrolling in Play App Signing?
- This feature is only supported for standard Play Console developer accounts. It isn’t supported for iframe Play Console accounts distributing private apps.
- Can I request resetting the upload key for iframe Play Console accounts?
- This feature is only supported for standard Play Console developer accounts. This feature isn’t supported for iframe Play Console accounts distributing private apps.
- Can the app signing key choice be changed?
- No, the key that you use in your first release (either your own key by using an APK or a Google-generated key by using an AAB) will become your app signing key.
- Can I switch to APK after uploading an app bundle in the iframe?
- If you initially created your app using an APK and then switched to app bundle by uploading the signing key, you can switch back to APK.
- If an app is initially created using app bundles via iframe, it can’t be switched back to APK.
- Can I use the Play Edit API to upload app bundles for private apps created from iframe?
- Yes, you can. However, you must first upload your signing key in the Play Console. You can then do future releases using the Play Edit API.
- Does Play Custom App Publishing API support app bundle?
- No, Play Custom App Publishing API only supports apps created using APK.
- Can I use Play Custom App Publishing API for app creation then use Play Edit API for updating apps?
- Yes, it is possible. However, you need to provide your signing key in the Play Console before using the Play Edit API for app bundle.
Using trademarked content without permission may result in a violation of Google Play Policy, even if the content belongs to your organization. If your private app:
- Contains trademarked content (brand names, logos, graphic assets, audio, etc.), or
- You're republishing an app that you received from a third party
Notify the Google Play App Review team that you have permission to use the content, and wait for a response from the team before publishing your app.