Hexnode MDM app not getting updated in ROM-enrolled deviceSolved

Participant
Discussion
3 years ago

Hey, I have a few devices enrolled using Hexnode’s ROM enrollment method. The devices were enrolled some time back and they were working fine till last few days. The Hexnode MDM app started crashing in a few of the devices recently. First I thought it was cus I didn’t update the app and I tried updating the app and still the same problem was there.. In the Action History page, it was showing that the action had failed with the error message:

“App not installed, The package conflicts with the existing package by the same name.”

Could someone tell me why this issue could be occurring?

Replies (4)

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

Did you try checking the version of the new APK file?

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

Yeah I did. The current version is 12.5.2 and the version of the new APK file is 12.7.

Marked SolutionPending Review
Hexnode Expert
3 years ago
Marked SolutionPending Review

Hey Antonia,

Thank you for reaching out to us!

This issue could arise due to a signature mismatch between the new APK file and the current one. The key used for signing the new APK may be different from the one used to sign the earlier APK. This could result in the Hexnode UEM application not getting updated.

You can contact your vendor and get the latest APK file signed with the same key. Upload the signed APK file to the Hexnode app inventory as an Enterprise application. Update the application with the newly signed APK file using the Install Application action from the Hexnode portal.

Hope this clears your query.

Cheers!
Chris Coleman
Hexnode UEM

Marked SolutionPending Review
Participant
3 years ago
Marked SolutionPending Review

Just got the app resigned by my vendor and the app got updated without any issues. Thanks for the update Chris. Bye!