What's new in iMazing Profile Editor 1.5.3

Fixes in 1.5.3

Fixed an issue that under certain configurations prevented the saving of VPN and other payloads.
Fixed an issue that prevented the payload removal button from appearing on certain payloads.
Fixed an issue that made certain preference conditionals skip evaluation on initial values.
Fixed a display issue with in-array Boolean properties.
Fixed an issue that led to the app crashing in rare circumstances.

In compliance with recent configuration profile changes announced by Apple, generated PayloadIdentifier values are now guaranteed to be unique
PayloadUUID values are now automatically regenerated when a saved payload changes, except in Certificate payloads
Preference keys in the Restrictions section have been reorganized into more groups
Section documentation can now be accessed via a new dedicated button as well as via a new help menu option (where available)
String fields in arrays now support line breaks using Ctrl+Shift+Enter and on paste
Misconfigured boolean fields can now display errors similar to other field types
Local caches of inactive manifest repositories are now cleaned on launch
Bundled preference manifests updated to the latest available
Maintenance options are now available in the Preferences window

Fixed an issue that in some cases prevented manifest updates when changing to a different branch in the same repository
Fixed an issue preventing values of boolean preference keys without known default from staying set when toggled
Matched the behavior of integer preference keys presented as booleans to that of native booleans in the context of setting to a known default value

Resolved issue preventing profiles which contain multiple payloads of the same type from being deployed to iOS 15. Learn more here: https://digidna.notion.site/IPE-Profiles-iOS-15-Compatibility-0cd72002024c435a96f37bfe6a83e21a

Preference manifests are now updated in-place from an online repository
The User PFM files folder option has been renamed to Local folder for custom and override preference manifests and manifests in that folder can now override those from the online repository
Users can now also define a local repository which can be either a local checkout of ProfileManifests (or forks) or any folder containing at least the general settings manifest
Profile signing is now a preference in the General settings section
Unfamiliar configuration payloads which are those whose domain lacks a defining preference manifest, are now preserved on profile save and can be optionally removed
Support added for custom Dictionary properties via dictionaries loaded from Plist files
Support added for string entry in Data properties that represent hexadecimal strings
Capabilities added for integration with third-party system management software
Notice alerting of failed profile saves added
Bundled preference manifests updated to the latest available