What's new 
I’m managing an Android enterprise app in Hexnode and need to keep different versions available for staged testing. Each APK has a different display name in Hexnode, such as version-specific names, and the version codes are different, but the Android package identifier is the same.
When I deploy the newer APK using a custom job, the job completes successfully and the app on the device updates. However, after scanning the installed packages, Hexnode shows an odd state where one of the app entries appears missing even though it is technically the same app package.
Is there a proper way to manage updates when multiple Hexnode enterprise app entries use the same Android package ID?
28 Views
