JamWiFi icon indicating copy to clipboard operation
JamWiFi copied to clipboard

Scan Fails

Open dennis777 opened this issue 2 years ago • 12 comments

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.

Screenshot 2023-09-21 at 09 32 22

Running it from Xcode yields a rather helpless message:

image

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?

dennis777 avatar Sep 21 '23 16:09 dennis777

Seconded - here's the full logs I got from Xcode. M1 Max 14" Macbook Pro, running macOS Sonoma 14.0

Screenshot 2023-09-26 at 9 27 31 AM

Leo133 avatar Sep 26 '23 16:09 Leo133

Thirded, I just get the extremely vague error.

Gunmoon80 avatar Oct 14 '23 00:10 Gunmoon80

@0x0XDev Just checking in, did you get a chance to look at this? Do you have any idea why this may be?

dennis777 avatar Nov 02 '23 03:11 dennis777

Maybe it's the MacOS version?

martinepedro avatar Dec 19 '23 04:12 martinepedro

Any chance? I see same error Maybe it's the security issue, like access to WIFI device?

philzyk avatar Jan 12 '24 23:01 philzyk

looks like this project has been abandoned

antwake avatar Feb 07 '24 12:02 antwake

Use something like aircrack-ng

acheong08 avatar Feb 07 '24 13:02 acheong08

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.

anonymouz4 avatar Feb 11 '24 20:02 anonymouz4

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.

dennis777 avatar Feb 11 '24 20:02 dennis777

Theres a more specific error when you disable the app sandbox

Apple80211BindToInterfaceWithService: FAILED to bind to interface en0 - -1/0xffffffff

image

dennis777 avatar Jun 11 '24 17:06 dennis777

Also this image

dennis777 avatar Jun 11 '24 17:06 dennis777

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.

dbilgili avatar Sep 14 '24 11:09 dbilgili