Open VladislavGatsenko opened 1 month ago
Thanks for this report, @VladislavGatsenko -- it looks like Apple has indeed deprecated their airport
utility as of macOS 14.4 and removed it in 14.5: https://www.intuitibits.com/2024/03/14/goodbye-airport/
If you're comfortable doing so, could you please run wdutil info > wdutil-info-user.txt
and sudo wdutil info > wdutil-info-sudo.txt
and post those files (scrubbed, if desired) here, or email directly to [ Steve (at) ecoAPM (dot) com ] ?
Thanks again! -Steve
Thank you for your response.
Here are the files: wdutil-info-user.txt wdutil-info-sudo.txt
Wow, super speedy response! ποΈ
It looks like info
only returns the currently connected SSID, so let's give the following a try:
/usr/bin/time -v sudo wdutil diagnose > wdutil-diag.txt 2>&1
The troubleshooting is truly appreciated, as I don't have any Apple devices to test with!
I used sudo /usr/bin/time sudo wdutil diagnose > wdutil-diag-3.txt 2>&1, because /usr/bin/time -v sudo wdutil diagnose > wdutil-diag.txt 2>&1:
/usr/bin/time: illegal option -- v
usage: time [-al] [-h | -p] [-o file] utility [argument ...]
wdutil-diag-3.txt WirelessDiagnostics_C02X531FJGH6_2024-07-25_02.01.13
Oof, sorry, I did not expect the output to be so large! Some research this morning shows that Apple has not replaced the required underlying functionality with anything else that works similarly.
I found all the info that's needed in the wifi_scan.txt
file that's part of the diagnostic archive, but that obviously takes too long to generate for Wi-Fi Surveyor's frequency of feedback.
If you're willing to continue providing support from your end, I've got a couple more things I'd like to try with wdutil
to see if we can pull what we need out of it. Could you post both the terminal output and any files created from the following commands?
time sudo wdutil dump
it looks like this creates a file in /tmp
with an auto-generated name, so hopefully the name is specified in the console output?time sudo wdutil log +wifi
I'm not sure if this logs to the terminal or not, and keeps running, or same as dump
outputs to a fileThanks again for all your help with this! -Steve
If the above don't work, we may need to wait for .NET 9 to be able to call Swift code, where the functionality we need does exist: https://github.com/dotnet/runtime/issues/93631
I found no output after running the wdutil commands, which is strange. I tried different command calls, according to the documentation, but the result is β0β. However, I found an alternative option. You can use the command: system_profiler SPAirPortDataType Here is the result of its execution. As it seems to me, this might be a solution.
time system_profiler SPAirPortDataType > 1.txt
Ahh, that is so awesome, thanks for finding that!
Did you need to be root in order to run it? Removing the sudo
requirement would be great!
It seems straightforward enough to parse, so I'll hopefully get a v2.0 out at some point next week π€π»
Yes, it works without specifying sudo.
Thanks for the help :)
Maybe json format for parsing would be more convenient:
time system_profiler -json SPAirPortDataType > 2.txt
Even better! Almost there! The only thing missing is the AP MAC addresses, which I think we can get from:
/usr/sbin/system_profiler -json SPAirPortDataType -detailLevel full > system_profiler.json
π€π»
Mac addresses are unfortunately unavailable.
Arg, that goes against the schema/spec I found. Do MAC addresses show up with sudo
?
Unfortunately, the result is similar, the mac address is still missing.
F, I guess we're going to need to remove some Mac functionality in v2.0 π’
It looks like there's no other option right now. Until either apple finalizes wdutil, or until .NET 9 comes along to use swift.
Steps to reproduce
Expected behavior The wifi adapter should be detected and networks should appear in the application (as it was before)
Observed behavior The application cannot detect the adapter and does not allow access to networks (this is the case now, resetting network settings does not help)