As for why the alert appearing or not matters — I've been thinking along the same lines, but since this is being flagged as a behavior change, I need to explain to our QA team why it's happening. At this point, I'm wondering if this is simply an OS-level behavior change rather than something specific to an Apple API — though would openURL be considered part of that? Our app doesn't call it directly, but I believe the MSAL library is using it under the hood.

Thank you for your reply! Unfortunately, I haven't been able to reproduce it reliably — even after uninstalling and reinstalling the app, resetting the device, etc., it rarely appears. The alert looks similar to the "This page will open in another application." confirmation dialog shown in this Stack Overflow question: https://stackoverflow.com/questions/54586806/firebase-dynamic-link-behaving-strangely-in-chrome-ios

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.