Open dennis777 opened 1 year ago
Seconded - here's the full logs I got from Xcode. M1 Max 14" Macbook Pro, running macOS Sonoma 14.0
Thirded, I just get the extremely vague error.
@0x0XDev Just checking in, did you get a chance to look at this? Do you have any idea why this may be?
Maybe it's the MacOS version?
Any chance? I see same error Maybe it's the security issue, like access to WIFI device?
looks like this project has been abandoned
Use something like aircrack-ng
Maybe it's the MacOS version?
It still works flawless on Sonoma 14.3 MacBook Pro 2016.
Again see Known Bugs. Believe it or not, I'm still rocking that same MacBook. My guess is that it's related to the newer T2 chip, but as I have no hardware, I can't debug it for newer devices. If somebody has, feel free to debug and submit a pull request.
Maybe it's the MacOS version?
It still works flawless on Sonoma 14.3 MacBook Pro 2016.
Again see Known Bugs. Believe it or not, I'm still rocking that same MacBook. My guess is that it's related to the newer T2 chip, but as I have no hardware, I can't debug it for newer devices. If somebody has, feel free to debug and submit a pull request.
The T2 chip was introduced in 2018 iirc. You Mac doesn't have it, therefore it works. Any Mac with T2 or Apple Silicon Mac (many people such as myself really benefit from the new architecture and performance gains and can't just keep using our old MacBooks) won't work properly.
Theres a more specific error when you disable the app sandbox
Apple80211BindToInterfaceWithService: FAILED to bind to interface en0 - -1/0xffffffff
Also this
Just a wild guess, but if this app is relying on the airport
command under the hood, then that might be the issue here since this command-line utility has been deprecated in macOS Sonoma 14.4.
Hardware: M1 Max 14" MacBook Pro, running macOS Sonoma 14.0
Not sure why, but I can't even get a scan out of this application anymore, before it would at least scan (although not send death packets) but now even the basic scanning capability is lost for whatever reason.
Running it from Xcode yields a rather helpless message:
Did the scan process change in macOS Sonoma? Because you can obviously still scan for wifi within settings. Maybe there some additional permission layer that needs to be toggled?