Open akanksha-atrey opened 6 months ago
The same problem occurred. This is caused by the airport command used by node-wifi being deprecated in MacOS Sonoma. https://github.com/friedrith/node-wifi/blob/1a4364e67c9789555a00656d35287f0cebb3add8/src/macOS/scan/command.js#L2
Yes, I realized that. I figured out a hack using pyobjc modules for CoreWLAN/CoreLocation. Not a pretty way of doing it, but does the job for the time being.
I did some research at lunch and found a hint here: https://github.com/friedrith/node-wifi/issues/195#issuecomment-2063874988
Then I found this: https://stackoverflow.com/questions/78153143/assistance-in-extracting-fields-and-formatting-using-pyobjc-and-corewlan
Maybe there is a way to use this here?
I just wanted to chime in and mention that I am also experiencing this issue on my end. After updating to MacOS Sonoma 14.4 (23E214), my system is unable to detect the SSID. Any insights or workarounds would be greatly appreciated.
Expected behavior
The package was detecting networks as expected.
Current behavior
After updating to MacOS Sonoma 14.4, the package is not detecting any networks.
Which are the affected features
Which is your operating system?
MacOS
Environment
MacOS Sonoma 14.4 (23E214)
Version of node-wifi
2.0.16
Steps to Reproduce
Solutions
Is this a bug or a local issue?