Turn off your iPhone, turn it back on again, and launch the existing app, and you will see the local network permissions dialog.

I don't know how that works either. so I think it's a bug.

antondeveloper, it seems to have been fixed in iOS16β6.

Our iOS app can connect to the dashcam via wireless Wi-Fi, allowing users to make configuration changes and verify driving records. To ensure the correct connection between our iOS app and the dashcam, we verify whether the iPhone is properly connected to the dashcam by using the iPhone's Wi-Fi IP address when connecting the iOS app to the dashcam. Therefore, could you please let me know why some iPhones are able to identify the Wi-Fi interface of an iPhone device?

By the way iPhone13 (iOS 16.1.1、16.2.1、16.4、16.4.1(a)) iPhoneXR (iOS 16.4、16.4.1) are able to function properly and establish a successful connection. iPhone13 (iOS 16.3.1、16.4.1) is unable to function properly.

I've got it. Thank you for your response.

I've got it. Thank you for your response!

Thank you for your response. It was very helpful.

Thank you for your prompt response and for providing guidance on where to seek further assistance. I understand that DevForums may not be the appropriate platform for my inquiry regarding the implementation and on-the-wire behavior of Apple’s networking stack. I will follow your suggestion and post my question in the Apple Support Community, specifically in the Business and Education topic area. Thank you again for your assistance and guidance.

I have already posted my query on the Apple Support Community. While I received several responses, none of them resolved the issue. I have also submitted a bug report. It has been two weeks since the submission, but I have not received any response yet. I appreciate any further assistance you can provide on this matter. Best regards,

I have already filed a report regarding the "Inquiry Regarding Differences in Wi-Fi Authentication and Encryption Between iPhone 16 Series and Other iOS 18 Devices" in early December 2024 (FB16045387). Since I have not yet received a response, I am reluctantly reaching out to DevForums for assistance. Additionally, I submitted a new report on the same issue at the end of January 2025 (FB16430182), but I still have not received any response.