Highlights
🐛 --mobdev2 no longer offers pair records to devices that aren't yours
A mobdev2 advert names its device by a MAC that is randomized whenever the device uses a private Wi-Fi address, so v11.16.1 found such devices by offering the pair records to every advertised device — including ones that were never paired with this host.
The advert does say which hosts the device is paired with: its TXT record carries one tag per paired host (authTag, authTag#1, …), derived from the HostID that is already in every lockdown pair record — the same check Apple's MobileDevice performs. pymobiledevice3 now offers a device only the records of the hosts it names, and skips a device that names none of ours without contacting it. No re-pairing is needed.
This applies to --mobdev2 (with or without --udid) and to tunneld's mobdev2 monitor. Adverts without tags (older iOS) are handled as before.
pymobiledevice3 syslog live --mobdev2 --udid <UDID>What's Changed
Full Changelog: v11.16.1...v11.16.2