iOS 13.2 message: nehelper sent invalid result code [1] for Wi-Fi information request

cncopycurrentnetworkinfo api will no longer return valid wi fi ssid and bssid information
access wifi information entitlement
cncopycurrentnetworkinfo returns nil
nehotspotconfiguration
ios 13 get current wifi ssid
cncopycurrentnetworkinfo example
ios wifi details
ios 13 wifi framework

My app uses locationservices for tracking and geofencing in the background.

Now with iOS 13.2 I see every second the following message in the console:

Anchorwatch nehelper sent invalid result code [1] for Wi-Fi information request

My app does nothing with the WiFi system and when I disable WiFi on the device the message disappears.

While there seem to be no adverse effects by the message I learned the hard way that ignoring message might be a bad idea.

Can anyone hint me to why this message is coming and what I can do to supress it ?

this plugin seems to be broken in IOS 13.0 beta (getCurrentSSID , same functionality works flawless in the latest IOS 12. [6077:1095709] [] nehelper sent invalid result code [1] for Wi-Fi information request However, it does not detect the wifi details on iOS 13.2.3 (dont know about other� 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.

Check out WWDC 19 session 713, It happenes because in iOS13 in order to get WiFi details you should allow location permission, each time you try to pull CNCopyCurrentNetworkInfo data from CNCopySupportedInterfaces array you will get this log.

silly solution may be to try to enable location permission and you will not get this error anymore

On iOS 13.1, CNCopyCurrentNetworkI…, On iOS 13.1, CNCopyCurrentNetworkInfo occasionally doesn't work. This bug continutes to exist in 13.2.2 and severaly impacts our developer abilities to connect IoT devices to I get about every second the message: " nehelper sent invalid result code [1] for Wi-Fi information request" in the console log. iOS 13.2 message: nehelper sent invalid result code [1] for Wi-Fi information request My app uses locationservices for tracking and geofencing in the background. Now with iOS 13.2 I see every second the following message in the console: Anchorwatch nehelper sent invalid result code [

It eventually turned out, that a third party framework that my app uses, launches those calls to CNCopyCurrentNetworkInfo.

After I added WiFi access capabilities as described here to the app itself the error message disappeared

iOS 13.2 message: nehelper sent invalid result code [1 , Now with iOS 13.2 I see every second the following message in the console: Anchorwatch nehelper sent invalid result code [1] for Wi-Fi information request. Stack Overflow | The World’s Largest Online Community for Developers

iOS 13.2 message: nehelper sent invalid result code [1 , Now with iOS 13.2 I see every second the following message in the console: Anchorwatch nehelper sent invalid result code [1] for Wi-Fi information request My� Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.

nehelper sent invalid result code [1] for Wi-Fi information request, iOS 13.2 message: nehelper sent invalid result code [1] for Wi-Fi information request. 0人点赞. 岁月静好. "小礼物走一走,来简书关注我". Stack Overflow Public questions and answers; Teams Private questions and answers for your team; Enterprise Private self-hosted questions and answers for your enterprise; Jobs Programming and related technical career opportunities

ios, iOS 13.2 message: nehelper sent invalid result code [1] for Wi-Fi information request. 发表于 2019-11-10 17:11:40. 活跃于 2019-11-22 17:46:54. 查看133 次. iOS 13.2 message: nehelper sent invalid result code [1] for Wi-Fi information request. 1. Displaying SSID in iOS App using Swift. 3. How to get ssid in Swift 2.0

Comments
  • Yes, I know that. But my app does already use the location services and thus has of course location permissions. My app does not call the networkinfo directly, but it seems the locations service does.
  • In my case it works fine after I gave the location permission!