iOS enterprise app configuration not applying automatically to new IPA versionsSolved

In Hexnode, iOS App Configurations are deployed through policies from Policies > iOS > App Management > App Configurations. However, the configuration must be mapped to a specific app entry in the portal.

If each new IPA build is uploaded as a separate standalone app inventory entry, Hexnode treats it as a different app entry for configuration mapping purposes. Because of this, the existing XML app configuration will not automatically carry over to the newly uploaded entry.

App configurations also cannot be applied directly at the App Catalog group level.

The recommended approach is to update the existing enterprise app entry with the new IPA instead of creating a new app inventory entry for every build. This keeps the app configuration mapping intact, so the same XML configuration continues to apply when the app is updated to the newer version.

Before rolling this out broadly, test the app update on a single device to confirm that the updated IPA installs correctly and receives the expected app configuration.

So the best practice is to keep one app entry and update the IPA inside that entry, instead of creating a new inventory item for each release?

Yes. Updating the existing app entry is the better option when you want the same iOS App Configuration XML to remain linked across app versions. Creating a new app entry for each build is useful if you need to manage versions as completely separate apps, but it also means app configuration mappings, policy associations, and catalog references may need to be handled separately for each entry.