What's new 
We manage three Android enterprise APKs for Dev, QA, and Production in Hexnode. They have the same app name and package name, but are uploaded as separate app entries and assigned through different policies.
The problem is with versioning. We wanted to use different semantic versions for each environment while keeping the same build number/version code, so that moving a tablet from a QA policy back to a Production policy would not trigger another app install/update. However, the dashboard does not allow validating an APK when another app entry already uses the same build number.
Is there a way to keep the same version code across separate app entries, or a better way to push updates only to part of the fleet without affecting production devices?
101 Views
