[](https://github.com/doronz88/pymobiledevice3/actions/workflows/python-app.yml "Python application action")
[](https://pypi.org/project/pymobiledevice3/ "PyPi package")
[](https://pepy.tech/project/pymobiledevice3)
[](https://discord.gg/52mZGC3JXJ)
- [News](#news)
- [Description](#description)
- [Installation](#installation)
- [OpenSSL libraries](#openssl-libraries)
- [Usage](#usage)
- [Working with developer tools (iOS \>= 17.0)](#working-with-developer-tools-ios--170)
- [Python API](#python-api)
- [Example](#example)
- [The bits and bytes](#the-bits-and-bytes)
- [Lockdown services](#lockdown-services)
- [Implemented services](#implemented-services)
- [Un-implemented services](#un-implemented-services)
- [Sending your own messages](#sending-your-own-messages)
- [Lockdown messages](#lockdown-messages)
- [Instruments messages](#instruments-messages)
- [Contributing](#contributing)
- [Useful info](#useful-info)
# News
See [NEWS](NEWS.md).
# Description
`pymobiledevice3` is a pure python3 implementation for working with iDevices (iPhone, etc...). This means this tool is
both architecture and platform generic and is supported and tested on:
* Windows
* Linux
* macOS
Main features include:
* Device discovery over bonjour
* TCP port forwarding
* Viewing syslog lines (including debug)
* Profile management
* Application management
* File system management (AFC)
* Crash reports management
* Network sniffing (PCAP)
* Firmware update
* Mounting images
* Notification listening and triggering (`notify_post()` api)
* Querying and setting SpringBoard options
* Automating WebInspector features
* DeveloperDiskImage features:
* Taking screenshots
* Simulate locations
* Process management
* Sniffing KDebug messages (**strace** capabilities++)
* Process monitoring (`top` like)
* Accessibility features
* Sniffing oslog which includes both syslog and signposts
* Backup
# Installation
You can install from PyPi:
```shell
python3 -m pip install -U pymobiledevice3
```
Or install the latest version directly from sources:
```shell
git clone git@github.com:doronz88/pymobiledevice3.git
cd pymobiledevice3
python3 -m pip install -U -e .
```
You can also install auto-completion for all available sub-commands by adding the following into your `~/.zshrc`:
```shell
# python-click<8.0
eval "$(_PYMOBILEDEVICE3_COMPLETE=source_zsh pymobiledevice3)"
# python-click>=8.0
eval "$(_PYMOBILEDEVICE3_COMPLETE=zsh_source pymobiledevice3)"
```
## OpenSSL libraries
Currently, openssl is explicitly required if using on older iOS version (<13).
On macOS:
```shell
brew install openssl
```
On Linux:
```shell
sudo apt install openssl
```
# Usage
The CLI subcommands are divided roughly by the protocol layer used for interacting in the device. For example, all
features derived from the DeveloperDiskImage will be accessible from the `developer`
subcommand. This also means that every feature which isn't there won't require it.
This is the main CLI usage:
```
Usage: python -m pymobiledevice3 [OPTIONS] COMMAND [ARGS]...
Options:
-h, --help Show this message and exit.
Commands:
activation activation options
afc FileSystem utils
amfi amfi options
apps application options
backup2 backup utils
bonjour bonjour options
companion companion options
crash crash report options
developer developer options.
diagnostics diagnostics options
lockdown lockdown options
mounter mounter options
notification notification options
pcap sniff device traffic
power-assertion Create a power assertion (wraps...
processes processes cli
profile profile options
provision privision options
remote remote options
restore restore options
springboard springboard options
syslog syslog options
usbmux usbmuxd options
webinspector webinspector options
version get installed package version
```
## Working with developer tools (iOS >= 17.0)
> **NOTE:** Currently, this is only officially supported on macOS & Windows (up to iOS 17.3.1), but fully supported on
> all platforms starting at iOS 17.4 using the new lockdown tunnel. For windows interaction with iOS 17.0-17.3.1, you'll
> need to install the additional WeTest drivers using: `pymobiledevice3 remote install-wetest-drivers` inside an
> administrator terminal
Starting at iOS 17.0, Apple introduced the new CoreDevice framework to work with iOS devices. This framework relies on
the [RemoteXPC](misc/RemoteXPC.md) protocol. In order to communicate with the developer services you'll be required to
first create [trusted tunnel](misc/RemoteXPC.md#trusted-tunnel) in one of the two forms:
- Launch a tunnel-server named `tunneld` to automatically detect devices and establish connections
- Execute the following:
```shell
# if the device supports remote pairing, such as corellium instances or AppleTVs,
# you'll need to first pair them
# normal iOS devices don't require this step
python3 -m pymobiledevice3 remote pair
# on windows, use a privileged shell
sudo python3 -m pymobiledevice3 remote tunneld
```
- Create tunnel manually using `start-tunnel`
- Execute the following:
```shell
# if the device supports remote pairing, such as corellium instances or AppleTVs,
# you'll need to first pair them
# normal iOS devices don't require this step
python3 -m pymobiledevice3 remote pair
# NOTE: on windows, use a privileged shell for the following commands
# starting at iOS 17.4 you can use the much faster lockdown tunnel
sudo python3 -m pymobiledevice3 lockdown start-tunnel
# if you need this connection type to be also available over wifi, you can enable it
python3 -m pymobiledevice3 lockdown wifi-connections on
# on older iOS version use the following instead
# you may pass `-t wifi` to force a WiFi tunnel
sudo python3 -m pymobiledevice3 remote start-tunnel
```
You will be printed with the following output providing you with the required connection details:
```
Interface: utun6
RSD Address: fd7b:e5b:6f53::1
RSD Port: 64337
Use the follow connection option:
--rsd fd7b:e5b:6f53::1 64337
```
_Ths command must be run with high privileges since it creates a new TUN/TAP device which is a high
privilege operation._
Now, (almost) all of pymobiledevice3 accept an additional `--rsd`/`--tunnel` option for connecting to the service over
the tunnel. The `--tunnel` option specifically, is always attempted implicitly upon an `InvalidServiceError` error to
simplify the work with developer services. You can now try to execute any of them as follows:
```shell
# Accessing the DVT services
# The --tunnel option may accept either an empty string, or a UDID for a specific device
python3 -m pymobiledevice3 developer dvt ls / --tunnel ''
# Or simply without the `--tunnel` option, assuming the tunneld is running
python3 -m pymobiledevice3 developer dvt ls /
# Or we could use the manual tunnel details
python3 -m pymobiledevice3 developer dvt ls / --rsd fd7b:e5b:6f53::1 64337
# And we can also access or the other "normal" lockdown services
python3 -m pymobiledevice3 syslog live --tunnel ''
```
## Python API
You could also import the modules and use the API yourself.
To communicate the device you'll need an instance of `LockdownClient`, from which you can pair with the device and
request to establish a connection to [all its exposed services](#lockdown-services).
To do so, use the following snippet:
```python
from pymobiledevice3.lockdown import create_using_usbmux, get_mobdev2_lockdowns
# Connecting via usbmuxd (you can also specify a specific UDID to connect to)
# Please note usbmuxd allows connecting to devices both on USB or on WiFi
lockdown = create_using_usbmux()
# you can also query network lockdown instances using the following:
async for ip, lockdown in get_mobdev2_lockdowns():
print(ip, lockdown)
```
Now you can connect to which service you'd like. We already [implemented many of the services](#implemented-services),
you can use import and use in the form of: `from pymobiledevice3.service.<SERVICE-NAME> import <SERVICE-CLASS>`.
For example, consider the following piece of code to print all syslog lines:
```python
from pymobiledevice3.lockdown import create_using_usbmux
from pymobiledevice3.services.syslog import SyslogService
# Connecting via usbmuxd
lockdown = create_using_usbmux()
for line in SyslogService(service_provider=lockdown).watch():
# just print all syslog lines as is
print(line)
```
If you need more examples of different cool stuff you can do with the different services, just look at
what [all the CLI commands are already doing](pymobiledevice3/cli).
However, iOS 17.0 introduced a new type of connection called [RSD (RemoteServiceDiscovery)](misc/RemoteXPC.md), used to
establish a connection with the different Developer-Mode services over a trusted tunnel. To do so,
you'll [first need to create a trusted tunnel](#working-with-developer-tools-ios--170).
Afterward, use the following APIs:
```python
from pymobiledevice3.remote.remote_service_discovery import RemoteServiceDiscoveryService
from pymobiledevice3.tunneld import get_tunneld_devices
from pymobiledevice3.services.syslog import SyslogService
# Get a list of all established tunnels in the `rsds` object
# You can treat them as any other LockdownClient
rsds = get_tunneld_devices()
# For example, you could use them to connect to any service as seen in prior example
for line in SyslogService(service_provider=rsds[0]).watch():
# just print all syslog lines as is
print(line)
# Or you could connect manually to a specific tunnel created by `start-tunnel`
host = 'fded:c26b:3d2f::1'
port = 65177
async with RemoteServiceDiscoveryService((host, port)) as rsd:
# you can now use this connection as any other LockdownClient connection
pass
# Alternatively, you can use this API not in a context-manager
rsd = RemoteServiceDiscoveryService((host, port))
await rsd.connect()
await rsd.close()
```
## Example
A recorded example for using a variety of features can be viewed at:
https://terminalizer.com/view/18920b405193
There is A LOT you may do on the device using `pymobiledevice3`. This is just a TL;DR of some common operations:
* Listing connected devices:
* `pymobiledevice3 usbmux list`
* Discover network devices using bonjour:
* `pymobiledevice3 bonjour browse`
* View all syslog lines (including debug messages):
* `pymobiledevice3 syslog live`
* Filter out only messages containing the word "SpringBoard":
* `pymobiledevice3 syslog live -m SpringBoard`
* Restart device:
* `pymobiledevice3 diagnostics restart`
* Pull all crash reports from device:
* `pymobiledevice3 crash pull /path/to/crashes`
* Manage the media directory:
* `pymobiledevice3 afc shell`
* List all installed applications and their details:
* `pymobiledevice3 apps list`
* List query only a specific set os apps:
* `pymobiledevice3 apps query BUNDLE_ID1 BUNDLE_ID2`
* Create a TCP tunnel from your HOST to the device:
* `pymobiledevice3 usbmux forward HOST_PORT DEVICE_PORT`
* Create a full backup of the device:
* `pymobiledevice3 backup2 backup --full DIRECTORY`
* Restore a given backup:
* `pymobiledevice3 backup2 restore DIRECTORY`
* The following will require Web Inspector feature to be turned on:
* Get interactive JavaScript shell on any open tab:
* `pymobiledevice3 webinspector js_shell`
* List currently opened tabs is device's browser:
* `pymobiledevice3 webinspector opened-tabs`
* The following will require also the Remote Automation feature to be turned on:
* Get interactive JavaScript shell on new remote automation tab:
* `pymobiledevice3 webinspector js_shell --automation`
* Launch an automation session to view a given URL:
* `pymobiledevice3 webinspector launch URL`
* Get a a selenium-like shell:
* `pymobiledevice3 webinspector shell`
* Mount DeveloperDiskImage (On iOS>=17.0, each command will require an additional `--rsd` option):
* `pymobiledevice3 mounter auto-mount`
* The following will assume the DeveloperDiskImage is already mounted:
* Simulate location
* Simulate a `lat long` location:
* `pymobiledevice3 developer simulate-location set lat long`
* Or the following for iOS>=17.0:
* `pymobiledevice3 developer dvt simulate-location set --rsd HOST PORT -- lat long`
* Play a .GPX file:
* `pymobiledevice3 developer dvt simulate-location play route.gpx`
* Add random timing noise between -500 and 500ms on the time between two points in the GPX file:
* `pymobiledevice3 developer dvt simulate-location play route.gpx 500`
* Clear the simulated location:
* `pymobiledevice3 developer dvt simulate-location clear`
* Taking a screenshot from the device:
* `pymobiledevice3 developer dvt screenshot /path/to/screen.png`
* View detailed process list (including ppid, uid, guid, sandboxed, etc...):
* `pymobiledevice3 developer dvt sysmon process single`
* Sniffing oslog:
* `pymobiledevice3 developer dvt oslog`
* Kill a process:
* `pymobiledevice3 developer dvt kill PID`
* List files in a given directory (un-chrooted):
* `pymobiledevice3 developer dvt ls PATH`
* Launch an app by its bundle name:
* `pymobiledevice3 developer dvt launch com.apple.mobilesafari`
* Sniff all KDebug events to get an `strace`-like output:
* `pymobiledevice3 developer dvt core-profile-session parse-live`
* Sniff all KDebug events into a file for parsing later with tools such
as [`pykdebugparser`](https://github.com/matan1008/pykdebugparser), `fs_usage` and so on...
* `pymobiledevice3 developer dvt core-profile-session save FILENAME`
* Get device extended information (kernel name, chipset, etc...):
* `pymobiledevice3 developer dvt device-information`
* Monitor energy-consumption for a specific PID:
* `pymobiledevice3 developer dvt energy PID1 PID2 ...`
# The bits and bytes
To understand the bits and bytes of the communication with lockdownd you are advised to take a look at this article:
https://jon-gabilondo-angulo-7635.medium.com/understanding-usbmux-and-the-ios-lockdown-service-7f2a1dfd07ae
## Lockdown services
### Implemented services
This is the list of all the services from `lockdownd` which we reversed and implemented API wrappers for. A click on
each will lead to each one's implementation, where you can learn more about.
* [`com.apple.mobile.heartbeat`](pymobiledevice3/services/heartbeat.py)
* Just a ping to `lockdownd` service.
* Used to keep an active connection with `lockdownd`
* [`com.apple.mobileactivationd`](pymobiledevice3/services/mobile_activation.py)
* Activation services
* [`com.apple.afc`](pymobiledevice3/services/afc.py)
* File access for `/var/mobile/Media`
* Based on afcd's protocol
* [`com.apple.crashreportcopymobile`](pymobiledevice3/services/crash_reports.py)
* File access for `/var/mobile/Library/Logs/CrashReports`
* Based on afcd's protocol
* [`com.apple.pcapd`](pymobiledevice3/services/pcapd.py)
* Sniff device's network traffic
* [`com.apple.syslog_relay`](pymobiledevice3/services/syslog.py)
* Just streams syslog lines as raw strings
* For a more robust structural parsing, it's better to access the `com.apple.os_trace_relay` relay.
* [`com.apple.os_trace_relay`](pymobiledevice3/services/os_trace.py)
* More extensive syslog monitoring
* [`com.apple.mobile.diagnostics_relay`](pymobiledevice3/services/diagnostics.py)
* General diagnostic tools
* [`com.apple.mobile.notification_proxy` & `com.apple.mobile.insecure_notification_proxy`](pymobiledevice3/services/notification_proxy.py)
* API wrapper for `notify_post()` & `notify_register_dispatch()`
* [`com.apple.crashreportmover`](pymobiledevice3/services/crash_reports.py)
* Just trigger `crash_mover` to move all crash reports into crash directory
* [`com.apple.mobile.MCInstall`](pymobiledevice3/services/mobile_config.py)
* Profile management (MDM)
* [`com.apple.misagent`](pymobiledevice3/services/misagent.py)
* Provisioning Profiles management
* [`com.apple.companion_proxy`](pymobiledevice3/services/companion.py)
* Companion features (watches and etc.)
* [`com.apple.mobilebackup2`](pymobiledevice3/services/mobilebackup2.py)
* Local backup management
* [`com.apple.mobile.assertion_agent`](pymobiledevice3/services/power_assertion.py)
* Create power assertion to prevent different kinds of sleep
* [`com.apple.springboardservices`](pymobiledevice3/services/springboard.py)
* Play with device's button layout
* [`com.apple.mobile.mobile_image_mounter`](pymobiledevice3/services/mobile_image_mounter.py)
* Image mounter service (used for DeveloperDiskImage mounting)
* [`com.apple.mobile.house_arrest`](pymobiledevice3/services/house_arrest.py)
* Get AFC utils (file management per application bundle)
* [`com.apple.mobile.installation_proxy`](pymobiledevice3/services/installation_proxy.py)
* Application management
* [`com.apple.instruments.remoteserver`](pymobiledevice3/services/remote_server.py)
* Developer instrumentation service, iOS<14 (DeveloperDiskImage)
* [`com.apple.instruments.remoteserver.DVTSecureSocketProxy`](pymobiledevice3/services/remote_server.py)
* Developer instrumentation service, iOS>=14 (DeveloperDiskImage)
* [`com.apple.mobile.screenshotr`](pymobiledevice3/services/screenshot.py)
* Take screenshot into a PNG format (DeveloperDiskImage)
* [`com.apple.accessibility.axAuditDaemon.remoteserver`](pymobiledevice3/services/accessibilityaudit.py)
* Accessibility features (DeveloperDiskImage)
* [`com.apple.dt.simulatelocation`](pymobiledevice3/services/simulate_location.py)
* Allows to simulate locations (DeveloperDiskImage)
* [`com.apple.dt.fetchsymbols`](pymobiledevice3/services/dtfetchsymbols.py)
* Allows fetching of `dyld` and dyld shared cache files (DeveloperDiskImage)
* [`com.apple.webinspector`](pymobiledevice3/services/webinspector.py)
* Used to debug WebViews
* [`com.apple.amfi.lockdown`](pymobiledevice3/services/amfi.py)
* Used to enable developer-mode
### Un-implemented services
This is the list of services we haven't dedicated time in implementing. If you feel the need to use one of them or any
other that is not listed in here, feel free
to [create us an issue request](https://github.com/doronz88/pymobiledevice3/issues/new?assignees=&labels=&template=feature_request.md&title=)
.
* `com.apple.idamd`
* Allows settings the IDAM configuration (something to do with loading of AppleUSBDeviceAudioDevice)
* `com.apple.atc`
* AirTraffic related
* `com.apple.atc2`
* `com.apple.ait.aitd`
* AirTraffic related
* `com.apple.mobile.file_relay` (Deprecated)
* On older iOS versions (iOS <= 8), this was the main relay used for file operations, which was later replaced with
AFC.
* `com.apple.mobilesync`
* `com.apple.purpletestr` (Deprecated)
* `com.apple.PurpleReverseProxy.Conn`
* Something to do with tethering internet connection to restored devices
* `com.apple.PurpleReverseProxy.Ctrl`
* Something to do with tethering internet connection to restored devices
* `com.apple.dt.remotepairingdeviced.lockdown`
* `com.apple.commcenter.mobile-helper-cbupdateservice`
* `com.apple.carkit.service`
* Used to transfer data to accessories. Data is transferred using iAP2 packets.
* `com.apple.bluetooth.BTPacketLogger`
* `com.apple.streaming_zip_conduit`
* Another relay used to install IPAs
### Sending your own messages
#### Lockdown messages
Every such subcommand may wrap several relay requests underneath. If you wish to try and play with some the relays
yourself, you can run:
```shell
pymobiledevice3 lockdown service <service-name>
```
This will start an IPython shell where you already have the connection established using the `client` variable and you
can send & receive messages.
```python
# This shell allows you to communicate directly with every service layer behind the lockdownd daemon.
# For example, you can do the following:
client.send_plist({"Command": "DoSomething"})
# and view the reply
print(client.recv_plist())
# or just send raw message
client.sendall(b"hello")
# and view the result
print(client.recvall(20))
```
#### Instruments messages
If you want to play with `DTServiceHub` which lies behind the `developer` options, you can also use:
```shell
pymobiledevice3 developer shell
```
To also get an IPython shell, which lets you call ObjC methods from the exported objects in the instruments' namespace
like so:
```python
# This shell allows you to send messages to the DVTSecureSocketProxy and receive answers easily.
# Generally speaking, each channel represents a group of actions.
# Calling actions is done using a selector and auxiliary (parameters).
# Receiving answers is done by getting a return value and seldom auxiliary (private / extra parameters).
# To see the available channels, type the following:
developer.supported_identifiers
# In order to send messages, you need to create a channel:
channel = developer.make_channel('com.apple.instruments.server.services.deviceinfo')
# After creating the channel you can call allowed selectors:
channel.runningProcesses()
# If an answer is expected, you can receive it using the receive method:
processes = channel.receive_plist()
# Sometimes the selector requires parameters, You can add them using MessageAux. For example lets kill a process:
channel = developer.make_channel('com.apple.instruments.server.services.processcontrol')
args = MessageAux().append_obj(80) # This will kill pid 80
channel.killPid_(args, expects_reply=False) # Killing a process doesn't require an answer.
# In some rare cases, you might want to receive the auxiliary and the selector return value.
# For that cases you can use the recv_plist method.
return_value, auxiliary = developer.recv_plist()
```
# Contributing
See [CONTRIBUTING](CONTRIBUTING.md).
# Useful info
Please see [misc](misc)
Raw data
{
"_id": null,
"home_page": null,
"name": "pymobiledevice3",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "doronz88 <doron88@gmail.com>, matan <matan1008@gmail.com>",
"keywords": "ios, protocol, lockdownd, instruments, automation, cli, afc",
"author": null,
"author_email": "doronz88 <doron88@gmail.com>, matan <matan1008@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/b7/8b/efe3547d142b9dbdda9f1dae44096ab632ceb4d4e7e00f2d20419dd3f9bd/pymobiledevice3-4.4.0.tar.gz",
"platform": null,
"description": "[](https://github.com/doronz88/pymobiledevice3/actions/workflows/python-app.yml \"Python application action\")\n[](https://pypi.org/project/pymobiledevice3/ \"PyPi package\")\n[](https://pepy.tech/project/pymobiledevice3)\n[](https://discord.gg/52mZGC3JXJ)\n\n- [News](#news)\n- [Description](#description)\n- [Installation](#installation)\n - [OpenSSL libraries](#openssl-libraries)\n- [Usage](#usage)\n - [Working with developer tools (iOS \\>= 17.0)](#working-with-developer-tools-ios--170)\n - [Python API](#python-api)\n - [Example](#example)\n- [The bits and bytes](#the-bits-and-bytes)\n - [Lockdown services](#lockdown-services)\n - [Implemented services](#implemented-services)\n - [Un-implemented services](#un-implemented-services)\n - [Sending your own messages](#sending-your-own-messages)\n - [Lockdown messages](#lockdown-messages)\n - [Instruments messages](#instruments-messages)\n- [Contributing](#contributing)\n- [Useful info](#useful-info)\n\n# News\n\nSee [NEWS](NEWS.md).\n\n# Description\n\n`pymobiledevice3` is a pure python3 implementation for working with iDevices (iPhone, etc...). This means this tool is\nboth architecture and platform generic and is supported and tested on:\n\n* Windows\n* Linux\n* macOS\n\nMain features include:\n\n* Device discovery over bonjour\n* TCP port forwarding\n* Viewing syslog lines (including debug)\n* Profile management\n* Application management\n* File system management (AFC)\n* Crash reports management\n* Network sniffing (PCAP)\n* Firmware update\n* Mounting images\n* Notification listening and triggering (`notify_post()` api)\n* Querying and setting SpringBoard options\n* Automating WebInspector features\n* DeveloperDiskImage features:\n * Taking screenshots\n * Simulate locations\n * Process management\n * Sniffing KDebug messages (**strace** capabilities++)\n * Process monitoring (`top` like)\n * Accessibility features\n * Sniffing oslog which includes both syslog and signposts\n* Backup\n\n# Installation\n\nYou can install from PyPi:\n\n```shell\npython3 -m pip install -U pymobiledevice3\n```\n\nOr install the latest version directly from sources:\n\n```shell\ngit clone git@github.com:doronz88/pymobiledevice3.git\ncd pymobiledevice3\npython3 -m pip install -U -e .\n```\n\nYou can also install auto-completion for all available sub-commands by adding the following into your `~/.zshrc`:\n\n```shell\n# python-click<8.0\neval \"$(_PYMOBILEDEVICE3_COMPLETE=source_zsh pymobiledevice3)\"\n# python-click>=8.0\neval \"$(_PYMOBILEDEVICE3_COMPLETE=zsh_source pymobiledevice3)\"\n```\n\n## OpenSSL libraries\n\nCurrently, openssl is explicitly required if using on older iOS version (<13).\n\nOn macOS:\n\n```shell\nbrew install openssl\n```\n\nOn Linux:\n\n```shell\nsudo apt install openssl\n```\n\n# Usage\n\nThe CLI subcommands are divided roughly by the protocol layer used for interacting in the device. For example, all\nfeatures derived from the DeveloperDiskImage will be accessible from the `developer`\nsubcommand. This also means that every feature which isn't there won't require it.\n\nThis is the main CLI usage:\n\n```\nUsage: python -m pymobiledevice3 [OPTIONS] COMMAND [ARGS]...\n\nOptions:\n -h, --help Show this message and exit.\n\nCommands:\n activation activation options\n afc FileSystem utils\n amfi amfi options\n apps application options\n backup2 backup utils\n bonjour bonjour options\n companion companion options\n crash crash report options\n developer developer options.\n diagnostics diagnostics options\n lockdown lockdown options\n mounter mounter options\n notification notification options\n pcap sniff device traffic\n power-assertion Create a power assertion (wraps...\n processes processes cli\n profile profile options\n provision privision options\n remote remote options\n restore restore options\n springboard springboard options\n syslog syslog options\n usbmux usbmuxd options\n webinspector webinspector options\n version get installed package version\n```\n\n## Working with developer tools (iOS >= 17.0)\n\n> **NOTE:** Currently, this is only officially supported on macOS & Windows (up to iOS 17.3.1), but fully supported on\n> all platforms starting at iOS 17.4 using the new lockdown tunnel. For windows interaction with iOS 17.0-17.3.1, you'll\n> need to install the additional WeTest drivers using: `pymobiledevice3 remote install-wetest-drivers` inside an\n> administrator terminal\n\nStarting at iOS 17.0, Apple introduced the new CoreDevice framework to work with iOS devices. This framework relies on\nthe [RemoteXPC](misc/RemoteXPC.md) protocol. In order to communicate with the developer services you'll be required to\nfirst create [trusted tunnel](misc/RemoteXPC.md#trusted-tunnel) in one of the two forms:\n\n- Launch a tunnel-server named `tunneld` to automatically detect devices and establish connections\n - Execute the following:\n ```shell\n # if the device supports remote pairing, such as corellium instances or AppleTVs,\n # you'll need to first pair them\n # normal iOS devices don't require this step \n python3 -m pymobiledevice3 remote pair\n \n # on windows, use a privileged shell\n sudo python3 -m pymobiledevice3 remote tunneld\n ```\n\n- Create tunnel manually using `start-tunnel`\n - Execute the following:\n ```shell\n # if the device supports remote pairing, such as corellium instances or AppleTVs,\n # you'll need to first pair them\n # normal iOS devices don't require this step \n python3 -m pymobiledevice3 remote pair\n \n # NOTE: on windows, use a privileged shell for the following commands\n\n # starting at iOS 17.4 you can use the much faster lockdown tunnel\n sudo python3 -m pymobiledevice3 lockdown start-tunnel\n \n # if you need this connection type to be also available over wifi, you can enable it\n python3 -m pymobiledevice3 lockdown wifi-connections on\n\n # on older iOS version use the following instead\n # you may pass `-t wifi` to force a WiFi tunnel\n sudo python3 -m pymobiledevice3 remote start-tunnel\n ```\n\n You will be printed with the following output providing you with the required connection details:\n ```\n Interface: utun6\n RSD Address: fd7b:e5b:6f53::1\n RSD Port: 64337\n Use the follow connection option:\n --rsd fd7b:e5b:6f53::1 64337\n ```\n\n_Ths command must be run with high privileges since it creates a new TUN/TAP device which is a high\nprivilege operation._\n\nNow, (almost) all of pymobiledevice3 accept an additional `--rsd`/`--tunnel` option for connecting to the service over\nthe tunnel. The `--tunnel` option specifically, is always attempted implicitly upon an `InvalidServiceError` error to\nsimplify the work with developer services. You can now try to execute any of them as follows:\n\n```shell\n# Accessing the DVT services\n# The --tunnel option may accept either an empty string, or a UDID for a specific device \npython3 -m pymobiledevice3 developer dvt ls / --tunnel ''\n\n# Or simply without the `--tunnel` option, assuming the tunneld is running\npython3 -m pymobiledevice3 developer dvt ls /\n\n# Or we could use the manual tunnel details\npython3 -m pymobiledevice3 developer dvt ls / --rsd fd7b:e5b:6f53::1 64337\n\n# And we can also access or the other \"normal\" lockdown services\npython3 -m pymobiledevice3 syslog live --tunnel ''\n```\n\n## Python API\n\nYou could also import the modules and use the API yourself.\nTo communicate the device you'll need an instance of `LockdownClient`, from which you can pair with the device and\nrequest to establish a connection to [all its exposed services](#lockdown-services).\n\nTo do so, use the following snippet:\n\n```python\nfrom pymobiledevice3.lockdown import create_using_usbmux, get_mobdev2_lockdowns\n\n# Connecting via usbmuxd (you can also specify a specific UDID to connect to)\n# Please note usbmuxd allows connecting to devices both on USB or on WiFi\nlockdown = create_using_usbmux()\n\n# you can also query network lockdown instances using the following:\nasync for ip, lockdown in get_mobdev2_lockdowns():\n print(ip, lockdown)\n```\n\nNow you can connect to which service you'd like. We already [implemented many of the services](#implemented-services),\nyou can use import and use in the form of: `from pymobiledevice3.service.<SERVICE-NAME> import <SERVICE-CLASS>`.\n\nFor example, consider the following piece of code to print all syslog lines:\n\n```python\nfrom pymobiledevice3.lockdown import create_using_usbmux\nfrom pymobiledevice3.services.syslog import SyslogService\n\n# Connecting via usbmuxd\nlockdown = create_using_usbmux()\nfor line in SyslogService(service_provider=lockdown).watch():\n # just print all syslog lines as is\n print(line)\n```\n\nIf you need more examples of different cool stuff you can do with the different services, just look at\nwhat [all the CLI commands are already doing](pymobiledevice3/cli).\n\nHowever, iOS 17.0 introduced a new type of connection called [RSD (RemoteServiceDiscovery)](misc/RemoteXPC.md), used to\nestablish a connection with the different Developer-Mode services over a trusted tunnel. To do so,\nyou'll [first need to create a trusted tunnel](#working-with-developer-tools-ios--170).\n\nAfterward, use the following APIs:\n\n```python\nfrom pymobiledevice3.remote.remote_service_discovery import RemoteServiceDiscoveryService\nfrom pymobiledevice3.tunneld import get_tunneld_devices\nfrom pymobiledevice3.services.syslog import SyslogService\n\n# Get a list of all established tunnels in the `rsds` object\n# You can treat them as any other LockdownClient\nrsds = get_tunneld_devices()\n\n# For example, you could use them to connect to any service as seen in prior example\nfor line in SyslogService(service_provider=rsds[0]).watch():\n # just print all syslog lines as is\n print(line)\n\n# Or you could connect manually to a specific tunnel created by `start-tunnel`\nhost = 'fded:c26b:3d2f::1'\nport = 65177\nasync with RemoteServiceDiscoveryService((host, port)) as rsd:\n # you can now use this connection as any other LockdownClient connection\n pass\n\n# Alternatively, you can use this API not in a context-manager\nrsd = RemoteServiceDiscoveryService((host, port))\nawait rsd.connect()\nawait rsd.close()\n```\n\n## Example\n\nA recorded example for using a variety of features can be viewed at:\nhttps://terminalizer.com/view/18920b405193\n\nThere is A LOT you may do on the device using `pymobiledevice3`. This is just a TL;DR of some common operations:\n\n* Listing connected devices:\n * `pymobiledevice3 usbmux list`\n* Discover network devices using bonjour:\n * `pymobiledevice3 bonjour browse`\n* View all syslog lines (including debug messages):\n * `pymobiledevice3 syslog live`\n* Filter out only messages containing the word \"SpringBoard\":\n * `pymobiledevice3 syslog live -m SpringBoard`\n* Restart device:\n * `pymobiledevice3 diagnostics restart`\n* Pull all crash reports from device:\n * `pymobiledevice3 crash pull /path/to/crashes`\n* Manage the media directory:\n * `pymobiledevice3 afc shell`\n* List all installed applications and their details:\n * `pymobiledevice3 apps list`\n* List query only a specific set os apps:\n * `pymobiledevice3 apps query BUNDLE_ID1 BUNDLE_ID2`\n* Create a TCP tunnel from your HOST to the device:\n * `pymobiledevice3 usbmux forward HOST_PORT DEVICE_PORT`\n* Create a full backup of the device:\n * `pymobiledevice3 backup2 backup --full DIRECTORY`\n* Restore a given backup:\n * `pymobiledevice3 backup2 restore DIRECTORY`\n* The following will require Web Inspector feature to be turned on:\n * Get interactive JavaScript shell on any open tab:\n * `pymobiledevice3 webinspector js_shell`\n * List currently opened tabs is device's browser:\n * `pymobiledevice3 webinspector opened-tabs`\n * The following will require also the Remote Automation feature to be turned on:\n * Get interactive JavaScript shell on new remote automation tab:\n * `pymobiledevice3 webinspector js_shell --automation`\n * Launch an automation session to view a given URL:\n * `pymobiledevice3 webinspector launch URL`\n * Get a a selenium-like shell:\n * `pymobiledevice3 webinspector shell`\n* Mount DeveloperDiskImage (On iOS>=17.0, each command will require an additional `--rsd` option):\n * `pymobiledevice3 mounter auto-mount`\n * The following will assume the DeveloperDiskImage is already mounted:\n * Simulate location \n * Simulate a `lat long` location:\n * `pymobiledevice3 developer simulate-location set lat long`\n * Or the following for iOS>=17.0:\n * `pymobiledevice3 developer dvt simulate-location set --rsd HOST PORT -- lat long`\n * Play a .GPX file:\n * `pymobiledevice3 developer dvt simulate-location play route.gpx`\n * Add random timing noise between -500 and 500ms on the time between two points in the GPX file:\n * `pymobiledevice3 developer dvt simulate-location play route.gpx 500`\n * Clear the simulated location:\n * `pymobiledevice3 developer dvt simulate-location clear`\n * Taking a screenshot from the device:\n * `pymobiledevice3 developer dvt screenshot /path/to/screen.png`\n * View detailed process list (including ppid, uid, guid, sandboxed, etc...):\n * `pymobiledevice3 developer dvt sysmon process single`\n * Sniffing oslog:\n * `pymobiledevice3 developer dvt oslog`\n * Kill a process:\n * `pymobiledevice3 developer dvt kill PID`\n * List files in a given directory (un-chrooted):\n * `pymobiledevice3 developer dvt ls PATH`\n * Launch an app by its bundle name:\n * `pymobiledevice3 developer dvt launch com.apple.mobilesafari`\n * Sniff all KDebug events to get an `strace`-like output:\n * `pymobiledevice3 developer dvt core-profile-session parse-live`\n * Sniff all KDebug events into a file for parsing later with tools such\n as [`pykdebugparser`](https://github.com/matan1008/pykdebugparser), `fs_usage` and so on...\n * `pymobiledevice3 developer dvt core-profile-session save FILENAME`\n * Get device extended information (kernel name, chipset, etc...):\n * `pymobiledevice3 developer dvt device-information`\n * Monitor energy-consumption for a specific PID:\n * `pymobiledevice3 developer dvt energy PID1 PID2 ...`\n\n# The bits and bytes\n\nTo understand the bits and bytes of the communication with lockdownd you are advised to take a look at this article:\n\nhttps://jon-gabilondo-angulo-7635.medium.com/understanding-usbmux-and-the-ios-lockdown-service-7f2a1dfd07ae\n\n## Lockdown services\n\n### Implemented services\n\nThis is the list of all the services from `lockdownd` which we reversed and implemented API wrappers for. A click on\neach will lead to each one's implementation, where you can learn more about.\n\n* [`com.apple.mobile.heartbeat`](pymobiledevice3/services/heartbeat.py)\n * Just a ping to `lockdownd` service.\n * Used to keep an active connection with `lockdownd`\n* [`com.apple.mobileactivationd`](pymobiledevice3/services/mobile_activation.py)\n * Activation services\n* [`com.apple.afc`](pymobiledevice3/services/afc.py)\n * File access for `/var/mobile/Media`\n * Based on afcd's protocol\n* [`com.apple.crashreportcopymobile`](pymobiledevice3/services/crash_reports.py)\n * File access for `/var/mobile/Library/Logs/CrashReports`\n * Based on afcd's protocol\n* [`com.apple.pcapd`](pymobiledevice3/services/pcapd.py)\n * Sniff device's network traffic\n* [`com.apple.syslog_relay`](pymobiledevice3/services/syslog.py)\n * Just streams syslog lines as raw strings\n * For a more robust structural parsing, it's better to access the `com.apple.os_trace_relay` relay.\n* [`com.apple.os_trace_relay`](pymobiledevice3/services/os_trace.py)\n * More extensive syslog monitoring\n* [`com.apple.mobile.diagnostics_relay`](pymobiledevice3/services/diagnostics.py)\n * General diagnostic tools\n* [`com.apple.mobile.notification_proxy` & `com.apple.mobile.insecure_notification_proxy`](pymobiledevice3/services/notification_proxy.py)\n * API wrapper for `notify_post()` & `notify_register_dispatch()`\n* [`com.apple.crashreportmover`](pymobiledevice3/services/crash_reports.py)\n * Just trigger `crash_mover` to move all crash reports into crash directory\n* [`com.apple.mobile.MCInstall`](pymobiledevice3/services/mobile_config.py)\n * Profile management (MDM)\n* [`com.apple.misagent`](pymobiledevice3/services/misagent.py)\n * Provisioning Profiles management\n* [`com.apple.companion_proxy`](pymobiledevice3/services/companion.py)\n * Companion features (watches and etc.)\n* [`com.apple.mobilebackup2`](pymobiledevice3/services/mobilebackup2.py)\n * Local backup management\n* [`com.apple.mobile.assertion_agent`](pymobiledevice3/services/power_assertion.py)\n * Create power assertion to prevent different kinds of sleep\n* [`com.apple.springboardservices`](pymobiledevice3/services/springboard.py)\n * Play with device's button layout\n* [`com.apple.mobile.mobile_image_mounter`](pymobiledevice3/services/mobile_image_mounter.py)\n * Image mounter service (used for DeveloperDiskImage mounting)\n* [`com.apple.mobile.house_arrest`](pymobiledevice3/services/house_arrest.py)\n * Get AFC utils (file management per application bundle)\n* [`com.apple.mobile.installation_proxy`](pymobiledevice3/services/installation_proxy.py)\n * Application management\n* [`com.apple.instruments.remoteserver`](pymobiledevice3/services/remote_server.py)\n * Developer instrumentation service, iOS<14 (DeveloperDiskImage)\n* [`com.apple.instruments.remoteserver.DVTSecureSocketProxy`](pymobiledevice3/services/remote_server.py)\n * Developer instrumentation service, iOS>=14 (DeveloperDiskImage)\n* [`com.apple.mobile.screenshotr`](pymobiledevice3/services/screenshot.py)\n * Take screenshot into a PNG format (DeveloperDiskImage)\n* [`com.apple.accessibility.axAuditDaemon.remoteserver`](pymobiledevice3/services/accessibilityaudit.py)\n * Accessibility features (DeveloperDiskImage)\n* [`com.apple.dt.simulatelocation`](pymobiledevice3/services/simulate_location.py)\n * Allows to simulate locations (DeveloperDiskImage)\n* [`com.apple.dt.fetchsymbols`](pymobiledevice3/services/dtfetchsymbols.py)\n * Allows fetching of `dyld` and dyld shared cache files (DeveloperDiskImage)\n* [`com.apple.webinspector`](pymobiledevice3/services/webinspector.py)\n * Used to debug WebViews\n* [`com.apple.amfi.lockdown`](pymobiledevice3/services/amfi.py)\n * Used to enable developer-mode\n\n### Un-implemented services\n\nThis is the list of services we haven't dedicated time in implementing. If you feel the need to use one of them or any\nother that is not listed in here, feel free\nto [create us an issue request](https://github.com/doronz88/pymobiledevice3/issues/new?assignees=&labels=&template=feature_request.md&title=)\n.\n\n* `com.apple.idamd`\n * Allows settings the IDAM configuration (something to do with loading of AppleUSBDeviceAudioDevice)\n* `com.apple.atc`\n * AirTraffic related\n* `com.apple.atc2`\n* `com.apple.ait.aitd`\n * AirTraffic related\n* `com.apple.mobile.file_relay` (Deprecated)\n * On older iOS versions (iOS <= 8), this was the main relay used for file operations, which was later replaced with\n AFC.\n* `com.apple.mobilesync`\n* `com.apple.purpletestr` (Deprecated)\n* `com.apple.PurpleReverseProxy.Conn`\n * Something to do with tethering internet connection to restored devices\n* `com.apple.PurpleReverseProxy.Ctrl`\n * Something to do with tethering internet connection to restored devices\n* `com.apple.dt.remotepairingdeviced.lockdown`\n* `com.apple.commcenter.mobile-helper-cbupdateservice`\n* `com.apple.carkit.service`\n * Used to transfer data to accessories. Data is transferred using iAP2 packets.\n* `com.apple.bluetooth.BTPacketLogger`\n* `com.apple.streaming_zip_conduit`\n * Another relay used to install IPAs\n\n### Sending your own messages\n\n#### Lockdown messages\n\nEvery such subcommand may wrap several relay requests underneath. If you wish to try and play with some the relays\nyourself, you can run:\n\n```shell\npymobiledevice3 lockdown service <service-name>\n```\n\nThis will start an IPython shell where you already have the connection established using the `client` variable and you\ncan send & receive messages.\n\n```python\n# This shell allows you to communicate directly with every service layer behind the lockdownd daemon.\n\n# For example, you can do the following:\nclient.send_plist({\"Command\": \"DoSomething\"})\n\n# and view the reply\nprint(client.recv_plist())\n\n# or just send raw message\nclient.sendall(b\"hello\")\n\n# and view the result\nprint(client.recvall(20))\n```\n\n#### Instruments messages\n\nIf you want to play with `DTServiceHub` which lies behind the `developer` options, you can also use:\n\n```shell\npymobiledevice3 developer shell\n```\n\nTo also get an IPython shell, which lets you call ObjC methods from the exported objects in the instruments' namespace\nlike so:\n\n```python\n# This shell allows you to send messages to the DVTSecureSocketProxy and receive answers easily.\n# Generally speaking, each channel represents a group of actions.\n# Calling actions is done using a selector and auxiliary (parameters).\n# Receiving answers is done by getting a return value and seldom auxiliary (private / extra parameters).\n# To see the available channels, type the following:\ndeveloper.supported_identifiers\n\n# In order to send messages, you need to create a channel:\nchannel = developer.make_channel('com.apple.instruments.server.services.deviceinfo')\n\n# After creating the channel you can call allowed selectors:\nchannel.runningProcesses()\n\n# If an answer is expected, you can receive it using the receive method:\nprocesses = channel.receive_plist()\n\n# Sometimes the selector requires parameters, You can add them using MessageAux. For example lets kill a process:\nchannel = developer.make_channel('com.apple.instruments.server.services.processcontrol')\nargs = MessageAux().append_obj(80) # This will kill pid 80\nchannel.killPid_(args, expects_reply=False) # Killing a process doesn't require an answer.\n\n# In some rare cases, you might want to receive the auxiliary and the selector return value.\n# For that cases you can use the recv_plist method.\nreturn_value, auxiliary = developer.recv_plist()\n```\n\n# Contributing\n\nSee [CONTRIBUTING](CONTRIBUTING.md).\n\n# Useful info\n\nPlease see [misc](misc)\n",
"bugtrack_url": null,
"license": "GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007",
"summary": "Pure python3 implementation for working with iDevices (iPhone, etc...)",
"version": "4.4.0",
"project_urls": {
"Bug Reports": "https://github.com/doronz88/pymobiledevice3/issues",
"Homepage": "https://github.com/doronz88/pymobiledevice3"
},
"split_keywords": [
"ios",
" protocol",
" lockdownd",
" instruments",
" automation",
" cli",
" afc"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "78125ce415aa8d40c70134aa5fe43012c0b69dbacc93d4d9799f7a413fd3128d",
"md5": "4affa8d150d4083a0ef5865783d20975",
"sha256": "3abfbdc5c540258d8d2f69a923c733cf8f04348b5d4bde9f1e284442355e318d"
},
"downloads": -1,
"filename": "pymobiledevice3-4.4.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "4affa8d150d4083a0ef5865783d20975",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 635700,
"upload_time": "2024-04-25T23:25:52",
"upload_time_iso_8601": "2024-04-25T23:25:52.438825Z",
"url": "https://files.pythonhosted.org/packages/78/12/5ce415aa8d40c70134aa5fe43012c0b69dbacc93d4d9799f7a413fd3128d/pymobiledevice3-4.4.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b78befe3547d142b9dbdda9f1dae44096ab632ceb4d4e7e00f2d20419dd3f9bd",
"md5": "7f6e590cf7f28d9a7a67867ba1818a76",
"sha256": "dcb56d7b2524888a548f9ab5aa6a2cf4042043e3be27ba5cd595f77d3797fa64"
},
"downloads": -1,
"filename": "pymobiledevice3-4.4.0.tar.gz",
"has_sig": false,
"md5_digest": "7f6e590cf7f28d9a7a67867ba1818a76",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 31544644,
"upload_time": "2024-04-25T23:25:57",
"upload_time_iso_8601": "2024-04-25T23:25:57.072507Z",
"url": "https://files.pythonhosted.org/packages/b7/8b/efe3547d142b9dbdda9f1dae44096ab632ceb4d4e7e00f2d20419dd3f9bd/pymobiledevice3-4.4.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-25 23:25:57",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "doronz88",
"github_project": "pymobiledevice3",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "construct",
"specs": [
[
">=",
"2.9.29"
]
]
},
{
"name": "asn1",
"specs": []
},
{
"name": "click",
"specs": []
},
{
"name": "coloredlogs",
"specs": []
},
{
"name": "IPython",
"specs": []
},
{
"name": "bpylist2",
"specs": [
[
">=",
"4.0.1"
]
]
},
{
"name": "pygments",
"specs": []
},
{
"name": "hexdump",
"specs": []
},
{
"name": "arrow",
"specs": []
},
{
"name": "daemonize",
"specs": []
},
{
"name": "gpxpy",
"specs": [
[
"<",
"1.6.0"
]
]
},
{
"name": "pykdebugparser",
"specs": [
[
">=",
"1.2.4"
]
]
},
{
"name": "pyusb",
"specs": [
[
">=",
"1.2.1"
]
]
},
{
"name": "tqdm",
"specs": []
},
{
"name": "requests",
"specs": []
},
{
"name": "xonsh",
"specs": []
},
{
"name": "parameter_decorators",
"specs": []
},
{
"name": "packaging",
"specs": []
},
{
"name": "pygnuutils",
"specs": [
[
">=",
"0.0.7"
]
]
},
{
"name": "cryptography",
"specs": [
[
">=",
"41.0.1"
]
]
},
{
"name": "pycrashreport",
"specs": [
[
">=",
"1.2.2"
]
]
},
{
"name": "fastapi",
"specs": [
[
">=",
"0.93.0"
]
]
},
{
"name": "uvicorn",
"specs": [
[
">=",
"0.15.0"
]
]
},
{
"name": "starlette",
"specs": []
},
{
"name": "wsproto",
"specs": []
},
{
"name": "nest_asyncio",
"specs": [
[
">=",
"1.5.5"
]
]
},
{
"name": "Pillow",
"specs": []
},
{
"name": "inquirer3",
"specs": [
[
">=",
"0.1.0"
]
]
},
{
"name": "ipsw_parser",
"specs": [
[
">=",
"1.2.3"
]
]
},
{
"name": "remotezip",
"specs": []
},
{
"name": "zeroconf",
"specs": []
},
{
"name": "ifaddr",
"specs": []
},
{
"name": "hyperframe",
"specs": []
},
{
"name": "srptools",
"specs": []
},
{
"name": "qh3",
"specs": [
[
"<",
"2"
],
[
">=",
"1.0.0"
]
]
},
{
"name": "developer_disk_image",
"specs": [
[
">=",
"0.0.2"
]
]
},
{
"name": "opack",
"specs": []
},
{
"name": "psutil",
"specs": []
},
{
"name": "pytun-pmd3",
"specs": [
[
">=",
"2.0.5"
]
]
},
{
"name": "pywintunx-pmd3",
"specs": [
[
">=",
"1.0.2"
]
]
},
{
"name": "aiofiles",
"specs": []
},
{
"name": "prompt_toolkit",
"specs": []
},
{
"name": "sslpsk-pmd3",
"specs": [
[
">=",
"1.0.3"
]
]
}
],
"lcname": "pymobiledevice3"
}
JSON
