Thank you for the reply! I am building on Xcode 16 (I've only upgraded my iOS to version 26) so that's why it won't have the new behavior huh... I assumed that if it's restricted by OS, then we should have little to no control of it, which means it should also show "icon first, then title" for the ContextMenu or Menu in the app on iOS 26. I will try building it in Xcode 26 (I've not set anything about UIDesignRequiresCompatibility) and see if it works. Thanks again!

Is there a plan to extend LegacyAppConfigAssetReference support to iOS 17.2 for the App:Managed declaration? Currently, the App:Managed declaration is supported from iOS 17.2. However, LegacyAppConfigAssetReference, which allows us to deliver existing MDMv1 AppConfig to apps within a DDM context, only supports iOS 18.4 and above. So, it seems the only way to transition MDMv1 AppConfig to DDM using this asset is to wait until the device has upgraded its iOS version to 18.4 or higher.

Is there a plan to extend LegacyAppConfigAssetReference support to iOS 17.2 for the App:Managed declaration? Currently, the App:Managed declaration is supported from iOS 17.2. However, LegacyAppConfigAssetReference, which allows us to deliver existing MDMv1 AppConfig to apps within a DDM context, only supports iOS 18.4 and above. So, it seems the only way to transition MDMv1 AppConfig to DDM using this asset is to wait until the device has upgraded its iOS version to 18.4 or higher.

Is there a plan to extend LegacyAppConfigAssetReference support to iOS 17.2 for the App:Managed declaration? Currently, the App:Managed declaration is supported from iOS 17.2. However, LegacyAppConfigAssetReference, which allows us to deliver existing MDMv1 AppConfig to apps within a DDM context, only supports iOS 18.4 and above so it seems the only way to transition MDMv1 AppConfig to DDM using this asset is to wait until the device has upgraded its iOS version to 18.4 or higher.