Highlights
🐛 --mobdev2 finds devices using a private Wi-Fi address again
v11.16.0 made --mobdev2 --udid connect only to the bonjour advert whose MAC equals the WiFiMACAddress in the device's pair record. A device using a private Wi-Fi address — the iOS default — advertises that randomized MAC instead, so the requested device was never matched:
$ pymobiledevice3 syslog live --mobdev2 --udid <UDID>
ERROR Device is not connected
The mobdev2 advert carries nothing else that identifies the device offline, so the pair record is offered to the advertised devices instead — a device accepts only its own record. With --udid just that device's record is offered, and anything that doesn't come up as the requested UDID is dropped.
The same limitation had always affected tunneld's mobdev2 monitor, which silently skipped paired devices behind a private address. It now offers its pair records to a device no record names, so those devices are tunneled too.
pymobiledevice3 syslog live --mobdev2 --udid <UDID>What's Changed
- 73e48fd lockdown: Offer every pair record to a mobdev2 device we cannot name (#1972) (@doronz88)
- b33017e lockdown: Find a mobdev2 device behind a private Wi-Fi address (#1971) (@doronz88)
Full Changelog: v11.16.0...v11.16.1