APK uploaded to wrong app entry due to debug package name: ensure release build before uploading to production app slot

Android

When you upload an APK to the Esper Console, it may appear under an unexpected app entry if the APK was built with a debug package name instead of a release package name. This article explains why this happens and how to upload the correct APK to your intended production app slot.

Understanding the issue

The Esper Console identifies and organizes apps by their Android package name. If you upload an APK built with a debug package name (for example, com.example.app.debug) to an app entry with a release package name (for example, com.example.app), the Esper Console treats them as separate applications. The debug APK creates or populates a different app entry instead of updating your production app.

This happens because Android debug and release builds commonly have different package names as a deliberate build convention. Once an app is registered in the Esper Console under a specific package name, uploads with different package names always create separate app entries.

Before you begin

Confirm the package name of your intended production app in the Esper Console:

1. In the Esper Console, go to Apps.
2. Find and click your production app entry.
3. Note the package name listed in the app details (for example, com.example.app or dev.yum.poseidon.release).

How to verify the APK package name

Before uploading an APK, verify its package name matches your production app entry. You can inspect the package name using the Android Asset Packaging Tool (aapt):

aapt dump badging <filename>.apk | grep package

Look for the line that shows package= and confirm it matches your production app entry's package name in the Esper Console.

How to upload the correct APK

1. Obtain an APK built with the release/production package name (not a debug build) from your development team.
2. Verify the package name using the aapt command above.
3. In the Esper Console, go to Apps → Private Apps → Upload APK.
4. Upload the corrected APK and confirm it maps to your intended production app entry.
5. Verify the app entry now shows the new version number.

How to clean up the incorrectly uploaded app entry

If an APK with a debug package name was already uploaded, you'll see a separate app entry (for example, "BytePOS-debug"). Remove this entry to avoid confusion:

1. In the Esper Console, go to Apps.
2. Locate the debug app entry (the one created by the debug APK).
3. Before deleting, check whether this app is assigned to any Blueprints or device groups. If it is actively assigned to devices, removing it may cause unintended behavior.
4. If safe to remove, click the debug app entry and delete it.
5. Verify that only your production app entry remains in Apps.

Troubleshooting

The APK is a release build, but it still appears under the wrong app entry.

Use aapt to inspect the actual package name in the APK and share the exact package= value with your development team so they can verify the build configuration matches your production app entry.

You need to keep both debug and release app entries, but want to remove one that is actively assigned to devices.

Check all Blueprints and device groups for references to the app you want to delete. Removing an app that is part of an active Blueprint may cause issues on managed devices. If you need help identifying these references, contact Esper Support.

Still need help?

If the APK package name matches your production app entry but the Esper Console still routes it to a different app slot, or if you need further assistance, submit a support ticket. Include the package name shown in the APK and the name of the app entry where you expected it to appear.