Please refer my comments below. Q) I’m gonna recommend that you promptly file a bug about this. Before I do that, however, I’d like to get a better understanding of where this certificate is coming from. It seems like you’re building an accessory that acts as a Wi-Fi access point (AP). So: . Is this certificate involved in the AP itself? For example, does the AP present it to iOS as part of EAP-TLS authentication? . Or does the AP have an HTTPS server? And thus iOS sees this certificate after it’s joined the AP’s network and connecting to this HTTPS server? This matters because it’ll inform the best diagnostic info to attach to your bug. => A) Yes, this certificate is made by the AP itself, and it is included inside. This certificate is used for SSL/TLS connections (HTTP server <-> clients).

Additionally, it reads and communicates information between devices and apps through SSL while connected to the softap on devices and do not connect with other apps.

We met following issue when our app. tries to connect to the softAp on the IoT device. Steps to Reproduce Launch the app (ex: ThinQ app )on an iOS 26 Beta device. Connect to the IoT device’s SoftAP Wi-Fi network (e.g., SSID: LG_SMART_XXX_XXXX). The app attempts to establish a TLS connection to the device’s TCP server (e.g., IP: 192.168.120.100). TLS handshake fails with error -9825. Expected Behavior The app should successfully establish a TLS connection with the IoT device, as it does in iOS 18 and earlier versions.

The log size is too large to attach and cannot be transferred. Is there a way to transfer it?

I attached sysdiagnose logs to https://feedbackassistant.apple.com/feedback/18597374. One is success logs in iOS18. The other is failed logs in iOS26. Please check these logs.