AirDrop not working on Mac: diagnose and fix it from the Terminal
Step-by-step Terminal guide to fix AirDrop on macOS: check awdl0, restart sharingd, bounce the wireless interface, and verify Bluetooth is healthy.
What this covers
When AirDrop stops finding or receiving from nearby devices, the cause is usually one of three things: the awdl0 wireless interface, the sharingd daemon, or the Bluetooth/Wi-Fi radios underneath. This guide walks through each in order so you can fix AirDrop without rebooting.
Symptom
Check the AirDrop wireless interface (awdl0)
AirDrop runs over the awdl0 (Apple Wireless Direct Link) interface, so a dead or missing awdl0 usually explains why AirDrop can't find anyone. Look at its state and flags — if the interface is absent or shows no status at all, the wireless link behind AirDrop is down. This tells you whether to restart the daemon, bounce the interface, or look deeper at Wi-Fi/Bluetooth.
View the current state, flags, and addresses of the awdl0 (Apple Wireless Direct Link) interface used by AirDrop and Sidecar.
$ ifconfig awdl0Confirm Bluetooth is healthy
AirDrop discovery also relies on Bluetooth, so a wedged Bluetooth controller makes AirDrop fail even when awdl0 looks fine. Run a Bluetooth report and confirm your controller is listed and connected devices appear as connected. If Bluetooth looks broken or no devices show up, fixing Bluetooth (e.g., restarting its daemon) may resolve AirDrop too.
One command lists every paired Bluetooth device, whether it is connected, and often its battery level.
$ system_profiler SPBluetoothDataTypeRestart the sharingd daemon
sharingd is the daemon that powers AirDrop, Handoff, and nearby sharing; when it gets stuck, AirDrop freezes with no obvious cause. Quitting it is safe — launchd relaunches it within seconds, so you get a fresh sharingd without a reboot. Wait a few seconds after running this, then try AirDrop again.
Use sudo killall sharingd to quit the sharing daemon; launchd instantly restarts it, fixing a stuck AirDrop without rebooting.
$ sudo killall sharingd▾ Undo
$ No undo needed — launchd automatically relaunches sharingd within seconds.Bounce the awdl0 interface
If restarting sharingd didn't help, the awdl0 interface itself may be in a bad state. Bringing it down and back up forces macOS to rebuild the peer-to-peer link AirDrop uses, which usually fixes the 'can't find nearby devices' symptom. Run this, then give AirDrop a few seconds to re-discover devices.
Bounce the awdl0 interface down and back up to fix AirDrop when it stops finding nearby devices.
$ sudo ifconfig awdl0 down && sudo ifconfig awdl0 up▾ Undo
$ The interface is brought back up by the same command; macOS normally reactivates awdl0 automatically when AirDrop is used again. If needed, run: sudo ifconfig awdl0 upToggle Wi-Fi off and back on
AWDL piggybacks on the Wi-Fi hardware, so a flaky Wi-Fi radio can keep AirDrop from working even after daemon and interface restarts. Cycling Wi-Fi power off and on resets the radio. Only do this if the previous fixes didn't help, and remember to turn Wi-Fi back on — you'll be briefly disconnected from your network.
networksetup -setairportpower switches the Wi-Fi hardware on or off, the same toggle the Wi-Fi menu performs.
$ networksetup -setairportpower en0 off▾ Undo
$ networksetup -setairportpower en0 onVerify Bluetooth and discovery are back
Re-run the Bluetooth report as a final check: the controller should be listed and devices should show as connected, which confirms the radio stack AirDrop depends on is healthy. Then open AirDrop and confirm nearby devices appear and a test transfer completes. If devices still don't show, revisit the diagnose steps.
Use system_profiler with the SPBluetoothDataType to print a detailed report of your Mac's Bluetooth controller and every connected Bluetooth device.
$ system_profiler SPBluetoothDataTypeHow to confirm it worked
Nearby devices reappear in the AirDrop sheet and a test file transfer completes both ways. A Bluetooth report shows the controller and connected devices as healthy.
Undo everything
Every command above can be reverted. Run these in order to undo all of it.
$ networksetup -setairportpower en0 on
The interface is brought back up by the same command; macOS normally reactivates awdl0 automatically when AirDrop is used again. If needed, run: sudo ifconfig awdl0 up
No undo needed — launchd automatically relaunches sharingd within seconds.Review before running — some steps may not be independent.
Sources
- IFCONFIG Command: Configure a network interface in macOSEvidence: The ifconfig utility is used to assign an address to a network interface and/or configure network interface parameters.
- system_profiler — hardware reports (macOS man page)Evidence: SPBluetoothDataType lists connected and paired devices with manufacturer, firmware and battery information.
- networksetup — network configuration tool (macOS man page)Evidence: Documents -setairportpower <device> on|off to switch the wireless interface power state.
Last verified: 2026-09-21
Related guides
Diagnose a stubborn Bluetooth device with system_profiler, then power-cycle Bluetooth and restart bluetoothd to get it connected again.
Find out whether macOS detects your external monitor, re-apply a working display mode with displayplacer, and verify the connection is healthy.
Diagnose and fix repeated Wi-Fi dropouts on macOS using built-in terminal tools: check your connection, read signal stats, reset the interface, and verify the link holds.