Thanks @DTS Engineer sir. The enhancement request has been raised for isSIMInserted to make it available for non carrier apps too. The bug reference number is FB16273814 Regards, Carol

@DTS Engineer Thanks for the prompt reply sir. Query 1: in case if I have any financial app like a money transfer app or UPI/ Bank app we cannot consume this API ? Because right now it will of great help if while using any financial like UPI apps to check the sim availability before sending the SMS Query 2: if I am developing a carrier app what entitlements should be needed from Apple for consuming isSIMInserted API? Reason : Docs related to isSIMInserted don't have detailed explanation about requirements Regards, Carol

Dear @mungbeans @DTS Engineer @DavidFindleyAtATT , Sir, i would like to have this api to be consumed in my stock investment app but i have certain queries as the documentation is not much clear. Is this api only available for mobile carrier apps(like apps for Vodafone, AT&T etc)? Mine is a stock investment app so there is nothing related to mobile carrier . What are the required entitlements If i can use this api in my app and how can i apply for necessary entitlements ? As per the documentation "This value property is true if the system finds a SIM matching the Info.plist carrier information (MCC / MNC / GID1 / GID2)". In which .plist key i should add these values? Please help me in this queries and also clarify if i miss any additional requirements.

@DTS Engineer Hello Eskimo, Any progress on the above issue. Please help us in this regard. Still the feedback chain is in open status with no comments. https://feedbackassistant.apple.com/feedback/14924584 Regards, Carol

I can confirm that CXCallObserver delegate is getting fired while there is an incoming WhatsApp video calls too. Tested with iOS 17.2 version in SE 2 gen. Also it is to be noted that the delegate callObserver:callChanged: only listens to the call status changes and the app should be in foreground before any call status changes happen. For example if we haven't launched our app and and an incoming call is there from some number and after that we launch the app, then the incoming status will not be observed because the app was not active to listen to the call change. In this case if we accept the call while app is in foreground then the hasConnected will be fired.

I found in another apple thread for similar issue and there it is confirmed by an Apple engineer that it is a bug for iOS 18 onwards . https://forums.developer.apple.com/forums/thread/760859 Filed the apple bug for this at: https://feedbackassistant.apple.com/feedback/14924584 FB14924584 Regards, Carol

Hello Eskimo, Filed a bug report for the same at https://feedbackassistant.apple.com/feedback/14924584 FB14924584 Regards, Carol

As an information received a reply from Apple for the raised bug and as of now it recommends to use securityType property instead of the buggy isSecure . So moving forward securityType must be used to find the wifi security type which can be only invoked with -fetchCurrentWithCompletionHandler: available from iOS 14 . Also please note securityType is only available from iOS 15 and above.

Hello Eskimo , Thanks for the confirmation that this is an issue of iOS and even iOS 16.3 have the same bug/issue with isSecure property . As per your request the bug has been filed with the number [FB11985434] FB11985434 Please have a look at it and hope Apple fixes it in upcoming days as I guess this bug has been there for long. Regards, Carol

Hello Eskimo, I can confirm the bug is still present as isSecure is returning always false even though securityType is 2 (i.e .personal) . I am getting SSID of the connected network without any issues but as mentioned in question isSecure is always false  even though  both my Mac and iPhone settings recognise that my network is secure as WPA2 Personal. I am calling NEHotspotNetwork.fetchCurrent(completionHandler:) I have location permissions granted with precise location. Access WiFi Information Entitlement enabled in both Xcode and prov profile I am running on iOS 15.6 this time. Any idea what is wrong here with isSecure in iOS 15 version? Is this bug fixed in iOS 16 SDK? Please help Yours sincerely, Carol