Handling ssid scanning exception about pinpoint HOT 3 CLOSED

This happened to me many times. On campus, we will have machines that cannot report data because printer wifi networks cause issues (the stupid HP DIRECT wifi signals). Not sure if some have carriage returns or something, but during the airport scan the xml fetched will quit halfway.

from pinpoint.

So this issue is just to track the hard crash. pinpoint should read the exception and write out an error.

I'm pretty sure it isn't a carriage return issue simply the airport command not being written in a way that it can handle that many SSIDs. I was able to replicate this a few times without pinpoint by calling:

/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport -s --xml 

It does look like I can replace the airport subprocess call with code from the Core WLAN framework. https://developer.apple.com/documentation/corewlan/cwinterface?language=objc That however it going to take a bit of time to write up and test.

from pinpoint.

Switching to CoreWLAN is going to be the better solution. I have a mock up working so I'll switch to that in the next release.

from pinpoint.