On iOS 13.1, CNCopyCurrentNetworkInfo occasionally doesn't work.

I’ve seen reports from a number of different developers about weird problems with

CNCopyCurrentNetworkInfo

Still, I agree with your conclusion that having a restart fixes the problem is strong evidence that you’re hitting a bug. Please file a bug report about this, then post your bug number here, just for the record.

When crafting your bug report:

1. Install the Wi-Fi for iOS profile from our Bug Reporting > Profiles and Logs page.

2. Reproduce the problem.

3. Make a note of the time.

4. Trigger a sysdiagnose log.

5. When that’s done, attach the log and your timestamp from step 3, to your bug report.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thanks! I submitted the feedback (FB7339809) with WiFi and device logs. Hope it helps

I'm having the same issue as Glauco, sent in my bug report here FB7348292

https://feedbackassistant.apple.com/feedback/7348292

I just had the same issue this morning using our app and my personal phone (iPhone 11 Pro) as some of our beta testers reported it.

I attached a debugger to my phone and confirmed that CNCopyCurrentNetworkInfo returns nil even if we have appopriate permissions due to new iOS 13 privacy enforcements. I confirm that a reboot fixed the issue.

Do we have any idea if iOS 13.2 resolves this ? I did not installed a beta yet.

Once iOS 13 went GM, I ended up with a bunch of DTS tech support incidents about this. It’s hard to be 100% sure because there are a lot of moving parts here, but at least one bug that can cause this issue (r. 55526060) is supposed to be fixed in the just-released 13.2b2 (17B5068e).

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi,

iOS 13.2 has been released. Any update on this? Is it working as expected or do we need to make something on our part?

Thank You very much.

Is it working as expected … ?

I think that’s for you to tell us, right? (-:

As I wrote in my 15 Oct post, 13.2 contains at least one fix for this issue. Whether that’s the only fix required is uncertain. If you continue to have this problem on 13.2, you should file your own bug about it per my 30 Sep post (or, if you’ve already filed a bug, update it with your latest test results).

Oh, one slight amendment to that post: In addition to installing the Wi-Fi for iOS profile, you should also install the Location Services for iOS profile. If there’s one concrete thing we’ve learnt in this process, is that these bugs live at the boundary between Wi-Fi and location.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Ok so I confirm that the issue is still present in iOS 13.2.

It happens less often because I did not reproduce the bug myself on my debug devices, however some of our clients using iOS 13.2 still see a specific screen we made in our app that pops up whenever the returned SSID is nil (and again, even though we are appropriate permissions).

Unfortunately, I don't have those profiles installed so I'll install those right now and if the issue happens, I'll file a sysdiagnose.

Thanks for keeping us informed!

We are also having customers report issues around this area in iOS 13.2.

We're not using NEHotspotConfiguration, but are instead getting location permission in order to read the SSID.

We were able to replicate the issue on one device when it was running iOS 13.1.3 (17A878), however it appeared to fix itself after the device had its "Location & Privacy" reset via Settings.app

Our users have the same problem, but restarting the phone has not been resolved. How can I fix this?

Same here as reported above. Can confirm it still happens in app linked against 13.2 SDK (Xcode 11.2 (11B52)). Randomly happens on some phones and reboot is required to temporarily work around it. After reboot, app works normally for some time then it starts failing to get SSID via CNCopyCurrentNetworkInfo().

if let interfaceInfo = CNCopyCurrentNetworkInfo(interface as! CFString) as NSDictionary? {
    ssid = interfaceInfo[kCNNetworkInfoKeySSID as String] as? String
} else {
    print("Getting InterfaceInfo (is nil) failed for \(interface)")
}

Also turning location access permissions to Ask Next Time in Settings.app and then restarting the app doesn't fix it either. Setting to Never and restarting app doesn't fix it either. Reboot is only way (I've found) to make it work again (temporarily).

Can confirm it still happens in app linked against 13.2 SDK (Xcode 11.2 (11B52)).

Hmmm, it’s not the SDK linkage that the issue here, but the OS version.

If you continue to see problems when running on iOS 13.2 (and that seems likely given the reports from others on this thread), please see me 31 Oct post.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I confirm that some users are occasionally reporting this to me too. One has fixed by reinstalling. Another one by rebooting. Experience is definitely crazy and randomic.

Funny enough, I had just started charging people for an app feature based on that, and Apple decides to break it. Room for bad ratings and more time wasted to update the FAQ on my website. The time and patience we developers wasted on iOS 13 bugs -which remain unfixed for months- have become very, very hard to calculate.

I'll file the umpteenth, useless report anyway. Useless because I got no fix nor relevant help from Apple about any of my multiple reports. Instead, the overall developer community helped a lot during this disgraceful 2019.

Somebody may not like the rant but man, this is a job for many of us and you're making it a constant challenge. The text view bug in Xcode is like... gosh, I won't even start with what it took me to sort out my Catalina/Xcode work environment.

Apple must stop rushing all these awful releases. The quality bar has gotten so unbearably low with iOS 13 and Catalina. Come on, you used to be much better than this.

Our customers report this issue in 13.2 (up to 13.2.2 still exists).

Because in their devices, there are no such iOS profiles installed, so that they/we cannot report the bug with the logs.

However, getting the current wifi SSID is a very key feature for some apps.

So I hope you and your teams can fix this issue as soon as possible.

Thanks a lot.

Note, rebooting the device did resolve this issue temporarily.

It is even worse, as it affects apps that don't use the WiFi interface on it's own.

I have an app which uses location service in background mode which used to run for days without trouble pre 13.2.

Now it terminates after a variable number of hours. Reason I figured is the WiFi interface implicitly used by the location service.

I get about every second the message: "

nehelper sent invalid result code [1] for Wi-Fi information request" in the console log.

Using Instruments I noticed that those calls to CNCopyCurrentNetworkInfo have a memory leak - with foreseeable consequences for the app.

Switching off WiFi on the device settings solved that particular problem, though turning off WFi seems to be a bit radical solution 😉

Is there anyway to use location services without it using WiFi ?

Hi eskimo1,

This bug continutes to exist in 13.2.2 and severaly impacts our developer abilities to connect IoT devices to our app through IoT device pairing and onboarding. I've submitted an additional ticket to help raise priority, thank you for swift reponse and resolution.

Ticket: Nov 19, 2019 at 9:51 AM – FB7455848

I've submitted an additional ticket

Thanks for that, but I don’t see a sysdiagnose log attached to that bug report. Please review my 31 Oct and 15 Oct for suggestions on how to file bugs about this.

ps I edited your post to prevent my email address showing up in plain text. I get enough spam already! (-:

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Any idea when we are going to get a fix for this? It's beginning to affect more and more of my users -- it was just isolated to a couple but now it seems to be growing. Definitely an iOS 13.x thing. None of the iOS 12.x users have experienced it. I spend more time explaining to users that it's an iOS/Apple bug (for which I can't get around) than I do working on the product. Rebooting is the only thing that will work around it -- and then only temporarily until it pops up again.

Hi,

Xcode has finally fixed this issue in the latest release. Please update to Xcode Version 11.3.1

Thanks,

Jitender

I am on the same boart here.. wondering when the fix is coming....

Is the problem completely fixed? There are still customer service feedback on this issue.

Is the problem completely fixed?

I think so. Certainly, the absence of traffic on this thread suggests that it’s working for most folks.

Two things:

• As CNCopyCurrentNetworkInfo has been deprecated, I recommend that you move over to NEHotspotNetwork.fetchCurrent(completionHandler:).

• If you continue to have problems after that, start a new thread with the details. Tag it with NetworkExtension so that the right folks see it.

Note While the official docs for fetchCurrent(completionHandler:) leave a lot to be desired, there’s a bunch of useful doc comments in the <NetworkExtension/NEHotspotNetwork.h> header.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

@eskimo as of 2022-02-25, we came across this thread from another article saying calling CNCopyCurrentNetworkInfo will lead to massive memory leak, with Xcode 13.2.1, iOS 14, while the app has no location auth and call this API. It will return NULL, and lots of internal objects leak, please see attached screenshot.

our test code:

for (int i = 0; i < 100000; i++) {
        @autoreleasepool {
            NSString *ssid = [UIDevice currentWifiSSID];
            NSString *bssid = [UIDevice currentWifiBSSID];
        }
    }

currentWifiBSSID will be like:

    NSArray *interfaces = (__bridge_transfer NSArray *)CNCopySupportedInterfaces();
    NSString *ssidStr = nil;
    for (NSString *name in interfaces) {
        NSDictionary *networkInfo = (__bridge_transfer NSDictionary *)CNCopyCurrentNetworkInfo((__bridge CFStringRef)name);
        ssidStr = [networkInfo objectForKey:(__bridge NSString *)kCNNetworkInfoKeySSID];
        if([ssidStr isKindOfClass:[NSString class]] && ssidStr.length > 0) {
            return ssidStr.copy;
        }
    }
    return nil;
}

Any plan to fix CNCopyCurrentNetworkInfo?

Any plan to fix CNCopyCurrentNetworkInfo?

While it’s reasonable to file a bug about the memory leak, note that CNCopyCurrentNetworkInfo has been deprecated in favour of the shiny new NEHotspotNetwork.fetchCurrentWithCompletionHandler: method. Does that also leak?

If you do file a bug, please post your bug number, just for the record.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"