As part of iOS 26, we get X25519MLKEM768 key exchange group support, but SecP256r1MLKEM768 and SecP384r1MLKEM1024 are not supported. Is there any way to enable these key exchange groups on iOS 26? We need them for WKWebView and NSURLSession. STEPS TO REPRODUCE On iOS 26, connect to the PQC server using Safari. The key exchange group is limited to X25519MLKEM768.

We have observed an internet access issue after the device enters idle mode on iOS 26 beta 9. Although the Ivanti Secure Access Client appears connected, users are unable to access any resources (internet or intranet) after unlocking the device from idle. When we check the log socket connection looks not disrupted, packets are tunnelled but no resource access. Split tunnel enabled and proxy PAC configured. This was observed on both iOS and iPadOS 26 beta. Steps to reproduce: Connecting to the internet, launching the Ivanti client, locking the device, and then unlocking it after a brief period of idle. The issue occurs when the VPN remains connected but no resources are accessible.

We have both App Store and enterprise developer accounts under the same entity name, and we recently received communication from Apple about iOS 18 security changes. The email mentions that sharing the same team name across multiple Apple developer accounts may affect the ability to load apps. Could you please clarify whether having the same entity name for both our App Store and enterprise accounts will cause issues with app distribution? If so, what steps should we take to resolve this issue?

Our VPN client rely on __SCNetworkReachability to detect any network change, It works fine normally but recently we have started seeing some issues with customer environment, Reachability goes down frequently. When we looked at logs we have seen host name resolved to two IP address one IPv4 address and other mapped IPv6 IP (i.e 64:ff9b::b96e:55c5). Irrespective of which IP is being used with Reachability class (IPv4 or mapped IPv6) problem is not going away. VPN connects fine and immediately within 1 or 2 secs reachability changes and this put the VPN back to connecting state. Note: This issue is not observed in WIFI or any mobile network doesn't provide mapped IP.

After upgrading to iOS 15, rvictl does not work as expected. It starts the device at rvi0 successfully but within few seconds rvi0 interface is getting closed. Wireshark says interface no more connected. "rvictl -s" prints "Could not get list of devices" after few seconds. Is this a known issue with iOS 15? Any workaround? I've tried on macOS Big Sur, version 11.6