feat(ios): Migrate from tidevice to pymobiledevice3 for iOS 17+ support #713
+542
−41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR migrates HydraLab's iOS device management from
tidevicetopymobiledevice3to enable support for iOS 17+ devices while maintaining backward compatibility with older iOS versions.Why this change?
Key Changes
IOSUtils.javaIOSDeviceDriver.javaEnvCapability.javapymobiledevice3capability keywordCommand Migration Summary
tidevice list --jsonpython3 -m pymobiledevice3 usbmux listtidevice -u <udid> screenshotpython3 -m pymobiledevice3 developer dvt screenshot --udidtidevice -u <udid> installpython3 -m pymobiledevice3 apps install --udidtidevice -u <udid> relaypython3 -m pymobiledevice3 usbmux forward --serialSee
TIDEVICE_TO_PYMOBILEDEVICE3_MIGRATION.mdfor complete mapping.Linked GitHub issue ID: N/A (Enhancement)
Pull Request Checklist
Does this introduce a breaking change?
Migration is backward compatible - JSON parsing supports both old (tidevice) and new (pymobiledevice3) field names.
How you tested it
Please check the type of change your PR introduces:
Feature UI screenshots or Technical design diagrams
N/A - Backend changes only. See migration doc for architecture details.
Co-Authored-By: Warp agent@warp.dev