Bump pymobiledevice3 from 11.15.1 to 11.19.4

[dependabot]

Bumps pymobiledevice3 from 11.15.1 to 11.19.4.

Release notes

Sourced from pymobiledevice3's releases.

v11.19.4

Highlights

🐛 cryptex auto-install no longer crashes cryptexd below iOS 26.4

On iOS 26.0.1, pymobiledevice3 cryptex auto-install made the device's cryptexd crash with asset already present: Cryptex1,GenericVolume, and the command printed only Aborted. (#1991). iOS only installs the DeveloperDiskImage as a cryptex from 26.4. Two things in the firmware change in that release, and from then on they match iOS 27:

• Where cryptexd may mount. Below 26.4 the kernel's platform sandbox policy doesn't let cryptexd mount anything at /System/Developer, where the DDI goes. The reporter's iPad logged deny(1) file-mount /System/Developer. There the DDI has to go through the image mounter instead.
• The device's asset-type table. The install names the disk image by its index in this table. iOS 26.4 reordered it, so on earlier versions the index we send names the image as a volume hash, which is what crashed cryptexd.

cryptex auto-install now refuses below iOS 26.4 before contacting Apple or the device, and points to pymobiledevice3 mounter auto-mount, which mounts the Personalized image there. On iOS 26.4 and later nothing changes.

🐛 A connection dropped by the device is reported as such

When a device closed a RemoteXPC connection between messages, the raw end-of-stream error escaped, and the CLI printed nothing but Aborted.. It's now a terminated connection like any other. When cryptexd drops an install without replying, cryptex auto-install says so and points to pymobiledevice3 syslog live -m cryptexd.

What's Changed

• 652912ff docs: State that the DeveloperDiskImage cryptex needs iOS 26.4 (#1993) (@​doronz88)
• eb622ae4 cryptexd: Only install the DeveloperDiskImage cryptex from iOS 26.4 (#1993) (@​doronz88)
• 4633c96e cryptexd: Explain an install that cryptexd dropped (#1993) (@​doronz88)
• 3e015678 remotexpc: Treat EOF at a frame header as a terminated connection (#1993) (@​doronz88)

Full Changelog: doronz88/pymobiledevice3@v11.19.3...v11.19.4

v11.19.3

Highlights

🐛 mounter auto-mount works on iOS 17.4 - 26.x again

Since v11.19.0, mounter auto-mount installed the Cryptex1 DeveloperDiskImage through cryptexd from iOS 17.4, or over any RSD tunnel. That path had only been verified on iOS 27. On iOS 26, cryptexd drops the install and the command ends with Aborted. (#1991).

auto-mount now installs the cryptex only from iOS 27, and mounts the PersonalizedDMG over the image mounter on iOS 17.0 - 26.x, as it did before v11.19.0:

iOS	Image
< 17.0	the classic DeveloperDiskImage.dmg for that version
17.0 - 26.x	the PersonalizedDMG over the image mounter
27.0+	the Cryptex1 DDI over cryptexd

Devices newer than the DDI, such as the iPhone 18 series, run iOS 27 or later, so they keep the cryptex path. Installing the cryptex directly with cryptex auto-install still fails on iOS 26 and is being investigated in #1991.

What's Changed

• 582519b4 mounter: Only install the cryptex DDI from iOS 27 (#1992) (@​doronz88)

Full Changelog: doronz88/pymobiledevice3@v11.19.2...v11.19.3

v11.19.2

Highlights

🐛 Native tunnel: no more crash at exit (exit 133)

... (truncated)

Commits

• 1281233 Merge pull request #1993 from doronz88/bugfix/cryptex-image-type-index
• 652912f docs: State that the DeveloperDiskImage cryptex needs iOS 26.4
• eb622ae cryptexd: Only install the DeveloperDiskImage cryptex from iOS 26.4
• 4633c96 cryptexd: Explain an install that cryptexd dropped
• 3e01567 remotexpc: Treat EOF at a frame header as a terminated connection
• 7bafa98 Merge pull request #1992 from doronz88/bugfix/cryptex-ddi-from-ios-27
• 582519b mounter: Only install the cryptex DDI from iOS 27
• bcdb027 Merge pull request #1990 from doronz88/bugfix/native-tunnel-reply-callout
• 6e5a620 native_tunnel: Wait for pending reply blocks on cancel
• a3912cb Merge pull request #1988 from doronz88/bugfix/auto-mount-exit-code
• 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)