chore(deps): bump pymobiledevice3 from 2.46.1 to 9.39.0

[dependabot]

Bumps pymobiledevice3 from 2.46.1 to 9.39.0.

Release notes

Sourced from pymobiledevice3's releases.

v9.39.0

Highlights

⚡ Userspace tunnel: ~+35% bulk-download throughput (RX checksum offload)

The no-root --userspace tunnel now skips the software RX checksum pass on the packets it receives from the device. Every packet arrives through the AEAD-authenticated RemotePairing/CoreDevice tunnel and an in-memory socketpair, so the RFC 1071 TCP/UDP checksum only re-verifies bytes that cannot have been corrupted in transit — and it was the single most expensive step of per-packet parsing. Only the checksum arithmetic is skipped: structural integrity checks, the RFC 8200 §8.1 UDP zero-checksum policy, and all outbound checksums stay active (the device kernel still verifies everything the host sends).

Measured on an iPhone 17 Pro / iOS 26.5 over USB, DSC symbol pull:

# same command, now ~35% faster over the userspace tunnel
pymobiledevice3 developer fetch-symbols download ./dsc --userspace

73.0 → 98.9 MB/s, with a byte-identical result. Interactive latency is unchanged. This rides a new net.rx_cksum_validate sysctl in pmd-pytcp 0.3.0 (the userspace stack), which also brings platform-correct errno handling and strict IPv4 parsing on macOS; pymobiledevice3 now floors on pmd-pytcp>=0.3.0.

What's Changed

• b34b3f81 userspace_tunnel: enable RX checksum offload (~+35% bulk download) (#1783) (@​doronz88)

Full Changelog: doronz88/pymobiledevice3@v9.38.1...v9.39.0

v9.38.1

Highlights

🐛 Userspace tunnel: fix a startup race in tunnel bring-up

The pytcp stack installs the tunnel's interface address from its own tasks shortly after stack.start() returns. A connection opened on the stack before the address lands fails with gaierror ("Malformed remote IP address"). The CLI's dial path usually added enough event-loop round trips to win this race by accident, but nothing guaranteed it — and embedders connecting right after UserspaceRsdTunnel.aopen() had no such slack. UserspaceTun.up() now waits until the address is actually usable before declaring the tunnel up, so the race is gone for every caller.

# embedders can now connect immediately after aopen() without racing the stack
async with UserspaceRsdTunnel(serial=udid) as rsd:
    await rsd.start_lockdown_service("com.apple.mobile.notification_proxy.shim.remote")

What's Changed

• 52856055 userspace_tunnel: wait for the stack address before declaring the tun up (#1782) (@​doronz88)
• cf362f3b tests: fix stale throughput-sysctl assertions from the PLPMTUD migration (#1782) (@​doronz88)

Full Changelog: doronz88/pymobiledevice3@v9.38.0...v9.38.1

v9.38.0

Highlights

🔊 Quieter -v: DTX message traffic now requires -vv

The DTXConnection sent/received DEBUG lines used to flood the output of every developer dvt command at plain -v, burying the logs you actually wanted. The pymobiledevice3.dtx logger is now kept at INFO unless verbosity is raised to -vv or higher.

# clean debug output, no DTX message dumps
pymobiledevice3 -v developer dvt ls /
</tr></table> 

... (truncated)

Commits

• 2251a95 Merge pull request #1783 from doronz88/feature/userspace-rx-cksum-offload
• b34b3f8 userspace_tunnel: enable RX checksum offload (~+35% bulk download)
• 841d9ca Merge pull request #1782 from doronz88/bugfix/userspace-tun-addr-race
• cf362f3 tests: fix stale throughput-sysctl assertions from the PLPMTUD migration
• 5285605 userspace_tunnel: wait for the stack address before declaring the tun up
• 1a63c7b Merge pull request #1781 from doronz88/feature/dtx-debug-vv
• 637def4 cli: require -vv for DTX message traffic logs
• b180e59 Merge pull request #1780 from doronz88/bugfix/afc-pull-ignore-errors-default
• ca44e1c afc: byte-scaled progress bars for single-file push and pull
• 815152c afc: make pull's --ignore-errors optional again
• 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 #24.