“The dmg file resolved has a different identifier” error when uploading app that has the same BundleIdentifierSolved

Hi all,

Scenario in short

I distribute enterprise apps as DMG files.
The usual workflow is to open the existing app entry, click Edit -> Upload, and drop in a newer DMG whose BundleIdentifier is identical but whose version is higher.
But this process doesn’t work for me: the portal claims that the BundleIdentifier is different, although manual inspection shows that the same BundleIdentifier is used.

Steps to reproduce

• Initial upload
  • Hexnode -> Apps -> Add -> Enterprise App
  • Upload MyApp 1.0.0.dmg, save the entry.
  • Deploy to a Mac and confirm version 1.0.0 installs successfully.
• Attempt to update via “Edit -> Upload”
  • Hexnode -> Apps -> Enterprise Apps -> open MyApp.
  • Click Edit -> Upload, choose MyApp 1.0.1.dmg, then Save.

Expected result

The existing app entry updates to version 1.0.1 without errors.

Actual result

A pop-up appears and the save is aborted:

The dmg file resolved has a different identifier. Try Add Apps to add new App

Additional evidence – the IDs are identical

• Uploading the same MyApp_1.0.1.dmg as a new app (Apps -> Add -> Enterprise App) and deploying it to a Mac running 1.0.0 successfully upgrades on the device to 1.0.1.

Questions

1. Has this bug been confirmed in recent Hexnode builds, and is a fix planned?
2. Is there an officially supported way to upload DMG updates that include the Applications alias?
3. For now, are the only work-arounds:
   – re-creating the DMG without the alias
   – converting the app to a PKG before upload?

Thanks in advance for any help!