Resolved issues
These are cumulative release notes. If a release does not appear in this section, then there were no associated resolved issues.

-
1561863: License Expiration Date was not displaying the proper valid date. This issue is fixed now.
-
1558297: 'VPN On Demand' configuration can be created successfully now.
-
1538720: Importing a User Group CSV of size up to 2MB is supported now.
-
1531958: '/api/v1/group' will not limit the max rows to 50 now.
-
1529603: When there are no devices present, and if any device cleanup activity is done, then the Audit Trail status is logged as 'Success'.
-
1425686: Previously, the apps which were installed from Apps@Work were not re-installed from the Play Store when:
-
The same app was un-distributed or deleted from App Catalog.
-
The app was deleted or uninstalled from the device.
Trying to redistribute or install the same app again failed. This issue is fixed now.
-

-
1512726: Device compliance ADD button was not working. This issue is fixed now.
-
1507980: Duplicate entries were appearing for apps in the App Inventory page. This issue is fixed now.
-
1493834: Device Groups were not appearing on the Device Group tab. The issue is fixed now.
-
1491464: In configuration details, AVAILABLE, INSTALLED, PENDING and ERROR counts were not updated for the following configurations:
-
Software Update Enforcement
-
Software Update Settings
-
Apple Watch Enrollment
This issue is fixed now.
-
-
1409036: The App list was not getting saved due to the unexpected symbols (such as , ":", "+") present in the bundle id and application name. This issue is fixed now.

-
1500965: The admin can now upload an Apple MDM Certificate to the newly created tenant.
-
1499121: Administrator can now edit System Update configuration even if the zebra OTA is enabled.
-
1497648: Admin > Windows >Windows updates can now be filtered with All / Configured / Unconfigured options.
-
1469606: When editing a dynamic group definition, the same group name was getting listed in the group names. This issue is fixed now.
-
1493371: Updated apps were not delivered to the devices via Google app tracks. This issue is fixed now.
-
1486445: The next page will appear in Ivanti Neurons for MDM from Windows updates, once enough updates are populated.
-
1480118: The Device type (Apple) column now shows the proper device model for iPad devices (Ipad14.8 to ipad14.11).
-
1475141: Searching for Device / User groups while distribution now fetches correct results.
-
1474929: In the Per App VPN configuration, once 'Enable 5G network Slicing' is selected and saved, it remains in the selected state even though it is deselected and saved.
-
1472424: User Group import was failing when any user is deleted and added back. This issue is fixed now.
-
1465089: When the admin clicks on Device Count from the Device Summary section of any specific app, the device count was not displayed correctly. This issue is fixed now.
-
1448620: Distribution details will be updated to the respective app version when the user selects the app version from the list.
-
1422572: Ivanti Neurons for MDM > Users > License Usage option was displaying the consumed licenses only, not the revoked ones. This issue is fixed now and list of all the licenses consumed by the user will be displayed.
-
1379620: Identity certificates were getting deleted if they are used in the Sentry profile, which are in turn used in Managed app configurations, and replaced with another Identity certificate in the Sentry profile.
Certificates that were removed from the Sentry profile on or before the R110 release will get deleted only when the respective Sentry profile is edited from the R112 release.
-
1294760: Device advance search with a Phone # is blank will give proper search results now.
-
1294468: Tenant Status is not changing to failed / error state, if license fails to apply on a newly created tenant.
-
1285399: macOS public apps with the same appStoreId (iTunesId) as iOS apps can now be installed on the macOS platform.
-
1281346: Previously, configurations such as VPN configurations would not accept the specification of some IANA-conformant domains. This issue is resolved and these mechanisms are now accepted in all IANA-conformant domains.