Thank you for replying so swiftly. We are using Managed App Config, and the issue comes from how our MDM vendor handles app installation. They state that if an app is added via URL (as would be the case with a Public Unlisted App), it is treated as unmanaged. Because of this, no MDM commands can be applied (the app only shows up in the device’s MDM catalog). The reason I mentioned ABM is that the vendor’s proposed solution is to add the app through ABM, which makes it managed again and restores functionality. Unfortunately, due to company policy, this approach is not available to us. Your clarification about declarative app configuration and legacy managed app configuration not being applicable via a .mobileconfig makes sense, and confirms that this path isn’t possible as a workaround. That leaves us with only two potential options: Ask the MDM vendor to treat URL-added apps as managed, or Republish the application as a Public Listed App. And no other workaround is possible?

I was doing more test and the problem is even worse. Siri announces any handle that it can't find direct correlation in Contacts app, and if it finds one then it says the contact name from there, ignoring completely localizedCallerName! I was deceived by the workaround when I wrote this because I used an email for a contact in Contacts and the name/surname also matches. There is simply no workaround, any CXHandleType will be announces, how is this possible? localizedCallerName is there for a reason...

My team is facing the same exact problem. We were seeing a spike in traffic when users uploaded their image positions (not a frequently used feature) but as this was a minor issue only now we are investigating this. As it turns out both options.scale = 1.0 and options.traitCollection = UITraitCollection(displayScale: 1.0) are now returning the snapshot with the same scale as the device screen, completely ignoring the option we set. Has anyone found a solution?