Bump pymobiledevice3 from 10.11.0 to 11.1.3

[dependabot]

Bumps pymobiledevice3 from 10.11.0 to 11.1.3.

Release notes

Sourced from pymobiledevice3's releases.

v11.1.3

Highlights

🐛 The native tunnel stops guessing which launchd domain holds remotepairingd

v11.1.1 taught the macOS native transport to reach the per-user remotepairingd from a process running as root, by retargeting the XPC connection whenever the effective uid was 0. That keyed off the wrong signal.

What actually decides reachability is which bootstrap namespace the process inherited, not its uid. Plain sudo from a logged-in user's terminal inherits that user's namespace and the ordinary lookup already works there; a LaunchDaemon or anything under launchctl asuser 0 lands in a domain where the service is not registered at all and gets XPC_ERROR_CONNECTION_INVALID back.

So the ordinary lookup is now always tried first, and another uid's domain is searched only once the daemon has actually reported the service missing. The probe is free — the error arrives about 0.2 ms after xpc_connection_activate, not at a timeout — and the outcome is memoized per process, so later browses go straight to whatever answered.

# unchanged, and still works from a root daemon or CI runner
pymobiledevice3 remote start-tunnel
skip the first attempt on a host with no console user
PYMOBILEDEVICE3_NATIVE_TARGET_UID=501 pymobiledevice3 remote start-tunnel
pin the ordinary lookup and disable retargeting entirely
PYMOBILEDEVICE3_NATIVE_TARGET_UID=0 pymobiledevice3 remote start-tunnel

Scope, stated plainly: on every configuration measured — normal user, launchctl asuser 0, plain sudo, and both with and without the environment variable — v11.1.2 and v11.1.3 reach the device equally. The behaviours diverge only when the console user is not the user whose namespace was inherited, such as sudo from one user's SSH session while another is at the console. If v11.1.2 works for you, this release changes nothing you can observe; it removes a guess, and reacts to what the daemon reports instead.

A seeded uid is refused with a warning unless the effective uid is 0, since the retarget SPI traps the process when a non-root caller invokes it.

What's Changed

• ed0afb6e remote: retarget remotepairingd only after the lookup actually fails (#1882) (@​doronz88)

Full Changelog: doronz88/pymobiledevice3@v11.1.2...v11.1.3

v11.1.2

Highlights

🐛 Test suite green again on Windows

The four tests added in v11.1.1 for the native tunnel's root-domain retargeting monkeypatched os.geteuid, which is POSIX-only and does not exist on Windows. Importing pymobiledevice3.remote.native_tunnel there is legal — the module is only useful on macOS, but nothing stops it being imported — so the tests failed on the Windows runner:

AttributeError: <module 'os' (frozen)> has no attribute 'geteuid'

Root detection now probes for the attribute in an _is_root() helper rather than calling it blind, and the tests let setattr create it.

This was a test-only failure — the v11.1.1 wheel is not broken on Windows. native_target_uid() is reachable only from the macOS-only native paths, which raise UserspaceTunnelUnavailableError off Darwin long before they get there. Upgrading from v11.1.1 is only worthwhile if you run the test suite yourself.

What's Changed

• 57019452 remote: fix native target-uid tests on Windows (#1881) (@​doronz88)

... (truncated)

Commits

• 4fcfdd8 Merge pull request #1882 from doronz88/feature/native-target-uid-on-demand
• ed0afb6 remote: retarget remotepairingd only after the lookup actually fails
• 4546d61 Merge pull request #1881 from doronz88/bugfix/native-target-uid-windows
• 5701945 remote: fix native target-uid tests on Windows
• 3195a2f Merge pull request #1880 from doronz88/bugfix/native-tunnel-root-target-uid
• 26ff9fc remote: reach the per-user remotepairingd from a root process
• 5787255 Merge pull request #1878 from doronz88/bugfix/sysmon-keep-monitoring
• f519470 sysmon: Add --keep-monitoring to survive relaunches and transient misses
• e473461 Merge pull request #1877 from doronz88/feature/rsd-auxiliary-metadata
• e5c9602 remote: expose device auxiliary metadata (deviceKVSData) over RSD
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #10.