Adding Public and Private Apps to Esper Tenant for Printing Workflows (Innowi / OrderHub Pattern)

Android

Title: Adding public and private apps to Esper and assigning them to Blueprints

When setting up a multi-app workflow — such as a printing or order management integration — you need each app present in your Esper tenant's App Library before you can install it on devices or include it in a Blueprint. If an app is missing from a Blueprint or fails to install on a device, it is almost always because the app was never added to the tenant, or was added but not yet assigned to the correct Blueprint.

Why this happens

Esper requires every app — whether sourced from Google Play or uploaded as a private APK — to be explicitly approved and added to your tenant's App Library before it can be managed. Apps do not appear automatically even if they are publicly available on the Play Store. Private apps must be uploaded as signed APKs. Only after an app is in the App Library can it be included in a Blueprint and pushed to devices.

Before you begin

Collect the following for each app before starting:

• The Google Play Store URL (for example, https://play.google.com/store/apps/details?id=epson.print) or the APK file for private or sideloaded apps
• For version updates: the exact target version number
• Whether the app should be added to the App Library only, or also assigned to one or more Blueprints
• If assigning to Blueprints: the exact name of each Blueprint

Add a public Google Play app

1. In the Esper Console, navigate to Apps & Configuration → Apps → Approved Apps.
2. Select Add App → Google Play Store.
3. Search by package ID (for example, epson.print or com.epson.mobilephone.android.epsonprintserviceplugin) or paste the full Play Store URL directly. Searching by package ID is more reliable than searching by app name, which can return ambiguous results.
4. Approve and add each app to your tenant's managed Play catalog.

Verify: The app appears under Apps & Configuration → Apps → Approved Apps within a few minutes of approval.

Add a private or sideloaded app

1. In the Esper Console, navigate to Apps & Configuration → Apps → Private Apps.
2. Select Upload APK and upload the APK file. The APK must be signed and target a compatible Android API level; unsigned APKs will be rejected.
3. Confirm the package name, version code, and version name displayed after upload match the expected values for your app.

Verify: The app appears under Apps & Configuration → Apps → Private Apps immediately after a successful upload.

Update an existing app to a new version

1. In the Esper Console, navigate to Apps & Configuration → Apps and select the app by name.
2. Upload the new APK version or approve the updated Play Store version.
3. If the app is pinned to a specific version inside a Blueprint, navigate to Blueprints → [Blueprint Name] → Apps and update the pinned version to the new release. Blueprints that pin a version will not automatically pick up new uploads — the version selection must be changed manually.
4. Save the Blueprint.
5. Apply the updated Blueprint to the target device group and monitor compliance status.

Verify: Devices in the group show the updated app version under Devices & Groups → [Device Name] → Apps once they sync. Devices that are offline will update the next time they reconnect.

Assign apps to a Blueprint

1. In the Esper Console, navigate to Blueprints → [Blueprint Name] → Apps.
2. Add each app. Only apps already present in the App Library will appear here — complete the steps above first if an app is missing.
3. Set the install mode for each app (for example, Auto-install or Managed) based on your deployment requirement.
4. Save the Blueprint.
5. Apply the updated Blueprint to the target device group.

Verify: The Blueprint shows the correct app list and version selections. Devices in the assigned group should reflect the updated app configuration within 5–10 minutes when online, visible under Devices & Groups → [Device Name] → Apps.

Troubleshooting

Play Store app does not appear after approval

1. Confirm your managed Google Play account is correctly linked by navigating to Settings → Android Enterprise and checking the connection status.
2. If the approval has not propagated after 10 minutes, re-sync the managed Play catalog from the same screen.

APK upload is rejected

• Confirm the APK is signed with a valid certificate.
• Check whether a conflicting entry with the same package name already exists in your App Library — duplicate package names are not permitted.
• Confirm the APK targets an Android API level supported by your devices.

Blueprint update is not applying to devices

• Check device connectivity under Devices & Groups. Devices that are offline will receive the Blueprint update automatically the next time they come online and check in with the Esper Agent.
• Review the Activity Feed for the device to confirm whether a push was received and whether any errors were reported.

If this doesn't resolve it

If managed Play approval remains stuck, your Android Enterprise binding appears broken, or APK uploads continue to fail after following the steps above, contact Esper Support. When reaching out, include:

• The package name and version of the affected app
• A screenshot of the error or the current status shown in the Console
• The name of any Blueprint the app is being assigned to
• The Android Enterprise binding status from Settings → Android Enterprise

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.