Manual APK upload to customer Esper account: signed APK uploaded via internal process

Android

If you need to upload a signed APK to your Esper account and don't have direct access to the Esper Console, or if you want to understand how APK uploads work, this article covers the process and requirements.

Before you begin

To upload an APK to your Esper account, you need:

• A signed release build APK file (unsigned or debug APKs will be rejected)
• Access to the Esper Console with Apps & Configuration permissions
• The correct package name and version information for your app

If you don't have direct console access or prefer assistance with the upload, you can contact Esper Support and provide a download link to your APK file.

How to upload an APK yourself

1. Sign in to the Esper Console.
2. Navigate to Apps → Private Apps.
3. Click Upload APK.
4. Select your signed APK file from your device.
5. Verify that the correct package name and version (for example, 5.5.14) appear after the upload completes.
6. The APK is now available in your app library and can be assigned to Blueprints or pushed to device groups.

How to request Esper Support to upload an APK

If you'd prefer Esper to handle the upload, follow these steps:

1. Contact Esper Support and provide:
   • A download link to your signed APK (SharePoint, Google Drive, Dropbox, or similar)
   • The app name and version number
   • Any relevant account or project details
2. If the download link requires authentication, grant access to the Esper Support team when requested.
3. Esper Support will verify the APK is signed and upload it to your account.
4. You'll receive confirmation once the upload is complete, and the APK will be visible under Apps → Private Apps in your console.

Important requirements

Only signed release APKs can be uploaded. Unsigned or debug builds will be rejected by the Esper platform. If you're unsure whether your APK is signed, check with your development team or review your app build configuration.

Uploading an APK does not automatically push it to devices. After upload, you must either:

• Add the app to a Blueprint and assign that Blueprint to a device group, or
• Use the app push feature to deploy it to specific devices

Troubleshooting

If the download link is expired or access-restricted: Reshare the file or grant access to Esper Support when requested. Do not delay—expired links will prevent the upload.

If the APK fails to upload: The Esper Console will display an error message. Common reasons include:

• The APK is unsigned or debug-signed
• A version of this app already exists in your library
• The target SDK is incompatible

Note the exact error message and contact Esper Support if the error persists after verifying the APK is signed.

If you can't find the APK in your app library after upload: Refresh your browser and navigate back to Apps → Private Apps. If it's still missing, contact Esper Support with your account details.

Still need help?

If you encounter issues uploading an APK or have questions about Apps & Configuration in Esper, submit a support ticket with details about your app and the error you're seeing. Our team is here to help.