How to Fix NameDrop Contact Sharing Not Triggering on Proximity on iPhone 16: Complete Diagnostic Manual
⚡ Quick 60-Second Verdict: What This Issue Means
Your iPhone 16’s NameDrop proximity handshake is failing because the NFC/UWB proximity daemon (nearbyd) has lost its entitlement handshake or the secure element isn’t advertising the contact-sharing payload when the display wakes. This is almost always a software state issue—AirDrop receive settings, Focus mode suppression, or a stale daemon cache—not a hardware fault. The fix path: verify AirDrop is set to “Everyone for 10 Minutes,” disable any Focus/Do Not Disturb filters blocking Nearby Sharing, then force-restart the proximity stack via a hardware reset.
- Do not insert metal tools, SIM ejector pins, or conductive objects into the USB-C port to “clean NFC antennas”—the iPhone 16’s NFC loop antenna wraps the top rear camera bezel and wireless charging coil, not the USB-C connector. Probing the port risks shorting the USB-C controller (CD3240) and Thunderbolt retimer.
- Do not apply heat guns, hair dryers, or ultrasonic cleaners to the rear glass to “reflow NFC solder joints.” The iPhone 16’s NFC flex is bonded to the rear glass with pressure-sensitive adhesive; heat above 60 °C delaminates the ceramic shield and destroys the UWB antenna array embedded in the glass.
- Do not install unsigned .mobileconfig profiles or “NFC unlock” shortcuts from forums claiming to “enable hidden NameDrop entitlements.” These modify
com.apple.developer.nfc.readersession.felica.systemcodesentitlements and will trigger Secure Enclave lockdown, requiring a full DFU restore. - Do not place the iPhone 16 on wireless chargers with thick metal alignment plates or MagSafe wallets containing RFID-blocking material during NameDrop attempts. The UWB ranging (Channel 5/9, 6.5–8 GHz) and NFC (13.56 MHz) near-field zones extend 4 cm from the top edge; any ferromagnetic shield attenuates the handshake below the 0.5 V/m threshold.
1. Immediate Safe Actions (Non-Destructive User Triage)
Three straightforward, non-destructive initial triage steps tailored specifically to NameDrop proximity failure on iPhone 16:
Verify AirDrop Receive Window & Screen State
NameDrop only triggers when both devices are unlocked, awake, and AirDrop is set to “Everyone for 10 Minutes.” Open Settings ▸ General ▸ AirDrop and confirm Everyone for 10 Minutes is selected (not “Contacts Only” or “Receiving Off”). If it reverts to “Receiving Off” after 10 minutes, that is expected behavior—re-enable it before each share attempt. Next, ensure neither iPhone is in a Focus mode (Do Not Disturb, Sleep, Personal, Work) that has “Filter Nearby Sharing” enabled. Check Settings ▸ Focus ▸ [Active Focus] ▸ Apps ▸ Nearby Sharing and toggle Allow Notifications on. Finally, both screens must be on and unlocked (Face ID authenticated or passcode entered); a dimmed or locked display suspends the nearbyd advertising payload.
Remove Case & Magnetic Accessories; Align Top Edges
The iPhone 16’s NFC loop antenna and UWB array are located along the top 15 mm of the rear glass (camera bezel region). Thick cases (> 2 mm), metal kickstands, MagSafe wallets with RFID shielding, or PopSockets centered on the upper half attenuate the 13.56 MHz NFC field and 6.5–8 GHz UWB pulses below the detection threshold. Remove all cases and accessories from both devices. Hold the phones top-edge to top-edge (camera bumps nearly touching) at a 0–5 mm gap, slightly offset so the Dynamic Islands align. Maintain this position for 3–5 seconds until the NameDrop ripple animation appears. Do not tap the backs together—impact shocks the OLED flex and does not improve coupling.
Toggle Airplane Mode to Reset NFC/UWB Radio Stack
A soft radio reset clears the nearbyd daemon’s stuck Bluetooth LE advertising state without a full reboot. Swipe down from the top-right for Control Center, tap Airplane Mode (orange icon), wait 15 seconds, then tap again to re-enable radios. This forces the NFC controller (NXP PN81T) and UWB chip (Apple U2/Proxima) to re-enumerate on the SPI/I²C bus and re-request entitlements from the Secure Enclave. After radios reconnect, verify Bluetooth and Wi-Fi icons are blue in Control Center (indicating active radios), then retry the top-edge alignment from Step 02.

2. Software False Alarm Recovery & Reset Protocol
iPhone 16 Hardware Reset Sequence
This sequence clears volatile RAM, restarts the nearbyd, bluetoothd, and wifid daemons, and forces the Secure Enclave to re-issue NFC/UWB entitlement tickets. Do not confuse this with “Erase All Content and Settings.”
- Press and immediately release Volume Up.
- Press and immediately release Volume Down.
- Press and hold the Side Button (right edge) for 15–20 seconds—ignore the “slide to power off” slider; keep holding until the screen goes black and the Apple logo appears.
- Release the Side Button. Allow the device to complete boot (Face ID setup screen or passcode entry).
- Unlock with Face ID/passcode. Wait 30 seconds for daemons to stabilize, then re-enable AirDrop ▸ Everyone for 10 Minutes (Step 01) and retry NameDrop.
Why this works: The iPhone 16’s Always-On Display (AOD) keeps the display controller and NFC field detector in a low-power polling state. A standard power-off/on does not fully reset the NFC controller’s firmware registers. The hardware reset (force restart) asserts the PMIC_RST_L line, power-cycling the NXP PN81T NFC controller and Apple U2 UWB chip, clearing any stuck RF_FIELD_DET interrupt flags.
3. Advanced Diagnostics & Component Triage
Hardware Telemetry & Sensor Verification
If Steps 01–04 fail, verify the NFC/UWB subsystem health via on-device logs and field test mode. This requires a Mac with macOS 14+ and Apple Configurator 2 (free from App Store).
- Connect iPhone 16 to Mac via USB-C (use the included USB-C charge cable or a Thunderbolt 3/4 cable).
- Open Console.app (Applications ▸ Utilities). Select the iPhone in the sidebar. In the search field, type:
subsystem:com.apple.nearbyd OR subsystem:com.apple.nfc OR category:UWB. - On the iPhone, attempt a NameDrop (top-edge alignment, both unlocked). Observe Console for:
nearbyd: [Proximity] Advertising payload: contact-sharing-v1→ Good (daemon advertising).nearbyd: [Proximity] Failed to start advertising: entitlement missing→ Entitlement loss (proceed to DFU restore).NFC: [PN81T] RF_FIELD_DET_IRQ: 0x0→ No field detected (hardware fault: NFC flex or antenna).UWB: [Proxima] Ranging session failed: NO_RESPONSE→ UWB antenna/calibration issue.
Field Test Mode (no Mac): Open Phone ▸ Keypad, dial *3001#12345#* → tap Call. Navigate: NR/MM Info ▸ NFC. Confirm NFC Tag Detected: YES when an NFC tag (e.g., Apple AirTag in Lost Mode) is tapped to the top edge. If “NO” consistently, the NFC flex or controller is faulty.
Analytics Data: Settings ▸ Privacy & Security ▸ Analytics & Improvements ▸ Analytics Data. Search for nearbyd or NFC. Look for nearbyd_ crash logs—these indicate daemon crashes requiring OS reinstall.

4. Diagnostic & Operating Parameter Matrix
| Diagnostic Indicator / Check | Expected Normal State | Fault Alert Threshold | Verified Resolution Target |
|---|---|---|---|
| AirDrop Receive Setting Settings ▸ General ▸ AirDrop |
Everyone for 10 Minutes active (blue checkmark) |
Reverts to Receiving Off or Contacts Only immediately after selection |
Setting persists for full 10-min window; NameDrop ripple appears on proximity |
| nearbyd Daemon Advertising Console.app filter: subsystem:com.apple.nearbyd |
Advertising payload: contact-sharing-v1 logged within 2 s of wake |
No advertising log entry; or entitlement missing / daemon not running |
Consistent advertising log on every wake/unlock; NameDrop triggers reliably |
| NFC Controller RF Field Detection Field Test: *3001#12345#* ▸ NR/MM Info ▸ NFC |
NFC Tag Detected: YES when AirTag tapped to top rear edge |
NFC Tag Detected: NO on 5+ consecutive tag taps with known-good tag |
Positive detection on 5/5 taps; Console shows RF_FIELD_DET_IRQ: 0x1 |
| UWB Ranging Session Initiation Console.app filter: category:UWB |
Ranging session started: peer=XXXX, channel=5, PRF=64 MHz |
Ranging session failed: NO_RESPONSE or CALIBRATION_INVALID |
Successful ranging log on proximity; NameDrop UI appears within 3 s |
| Focus Mode Nearby Sharing Filter Settings ▸ Focus ▸ [Active] ▸ Apps ▸ Nearby Sharing |
Allow Notifications: ON (green toggle) |
Toggle is OFF or Focus mode auto-activates (Sleep/Driving) suppressing Nearby | Nearby Sharing allowed in all active Focus modes; no suppression logs in Console |
| Secure Enclave NFC/UWB Entitlement Tickets Console.app: subsystem:com.apple.security.enclave |
Entitlement granted: com.apple.developer.nfc.readersession.iso7816.select |
Entitlement denied: missing keybag or ticket expired |
Valid tickets issued on every boot; no denial logs for 7 consecutive days |
5. Frequently Asked Questions (FAQ)
Why does NameDrop work once, then stop until I restart my iPhone 16?
This is a known nearbyd daemon state leak in iOS 17.0–18.1 where the advertising token isn’t refreshed after the first successful handshake. The daemon enters a “zombie” state—still running but not re-registering the contact-sharing payload with the NFC controller. The hardware reset (Step 04) clears this. Apple addressed the root cause in iOS 18.2 (build 22C151) with a watchdog timer that restarts nearbyd if no advertising event occurs within 60 s of wake. Ensure you’re on 18.2 or later: Settings ▸ General ▸ Software Update.
My iPhone 16 shows “NameDrop Not Available” with a yellow warning icon. What does this mean?
That banner appears when the Secure Enclave refuses to sign the NFC advertising payload because the device passcode hasn’t been entered since the last reboot (or 6.5 days have passed per iOS 18’s “USB Restricted Mode” logic). The fix: unlock with Face ID/passcode, wait 5 seconds, then retry. If the banner persists, the Secure Enclave keybag is corrupted—back up via Finder/iCloud, then perform a full DFU restore (not standard recovery) to re-provision the SEP firmware and keybag.
Does a cracked rear glass on my iPhone 16 break NameDrop permanently?
Only if the crack severs the NFC flex antenna trace running along the top 15 mm of the rear glass (see Figure 1). The UWB antenna array is a printed pattern on the inner surface of the ceramic shield; hairline cracks rarely affect it. Test with Field Test Mode (Step 05): if NFC Tag Detected: YES, the NFC loop is intact and NameDrop will work. If “NO,” the NFC flex (part 821-03412) requires replacement—this is a rear-glass assembly swap (Apple Self Service Repair or AASP), not a logic board repair. Do not attempt microsoldering the NFC flex; it’s bonded to the glass with conductive adhesive.
Can I use NameDrop with an iPhone 16 and an older iPhone (XS, 11, 12, 13, 14, 15)?
Yes, but only the iPhone 16 (and 15 series) initiates the UWB ranging handshake. Older models (XS–14) lack the U2/Proxima UWB chip and fall back to Bluetooth LE proximity, which is slower (10–15 s vs. 1–2 s) and requires both devices on iOS 17.1+. On the older iPhone, ensure Bluetooth is ON (not just Wi-Fi) and AirDrop is Everyone for 10 Minutes. The NameDrop UI will appear on the older device first; tap Share there, then the iPhone 16 will receive. If the older device is on iOS 16 or earlier, NameDrop is unsupported—use AirDrop via Share Sheet instead.
Share your OS version, device model, and exact error code in our independent peer Q&A rooms.
Comments