[GH-ISSUE #8473] [Feature] iOS device acquisition lane mirroring the ADB suite (BYO libimobiledevice) #6616

New issue

Open

opened 2026-11-01 21:12:42 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:12:42 +00:00

Owner

Originally created by @lostsock1 on GitHub (Nov 1, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/8473

Context

Android analysis has a full BYO acquisition suite (list_adb_devices, inspect_adb_device, list_adb_packages, pull_adb_file, start/stop_adb_app, …). iOS has static IPA lanes (inspect-artifact, project-apple-application-graph) and Frida attach/spawn, but no device lane at all — community toolkits list libimobiledevice, ios-deploy, and Objection for this gap, all outside REA's evidence model.

Suggested direction

Mirror the ADB suite with bring-your-own libimobiledevice tools (idevice_id, ideviceinfo, ideviceinstaller, ideviceapp2cp), resolved like REA_ADB_PATH:

Read-first: list paired devices, device info (product, version, UDID), installed app inventory, pull an app data container.
Device-mutating (install, launch) declared with explicit effects, mirroring rea_install_adb_package discipline.
Every fact carries Evidence; no jailbreak or code-signing bypass assumptions.

Open questions

Verification hardware: the lane needs a paired device for real verification; CI can only cover the client-inspection and malformed-path boundaries.
Windows depends on iTunes/Apple Mobile Device Service (usbmuxd) — is a Windows admission restriction acceptable initially?
Should syslog capture (idevicesyslog) be in the first increment, or device/app inventory only?

Originally created by @lostsock1 on GitHub (Nov 1, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/8473 ## Context Android analysis has a full BYO acquisition suite (`list_adb_devices`, `inspect_adb_device`, `list_adb_packages`, `pull_adb_file`, `start/stop_adb_app`, …). iOS has static IPA lanes (inspect-artifact, project-apple-application-graph) and Frida attach/spawn, but no device lane at all — community toolkits list libimobiledevice, ios-deploy, and Objection for this gap, all outside REA's evidence model. ## Suggested direction Mirror the ADB suite with bring-your-own libimobiledevice tools (`idevice_id`, `ideviceinfo`, `ideviceinstaller`, `ideviceapp2cp`), resolved like `REA_ADB_PATH`: - Read-first: list paired devices, device info (product, version, UDID), installed app inventory, pull an app data container. - Device-mutating (install, launch) declared with explicit effects, mirroring `rea_install_adb_package` discipline. - Every fact carries Evidence; no jailbreak or code-signing bypass assumptions. ## Open questions 1. Verification hardware: the lane needs a paired device for real verification; CI can only cover the client-inspection and malformed-path boundaries. 2. Windows depends on iTunes/Apple Mobile Device Service (usbmuxd) — is a Windows admission restriction acceptable initially? 3. Should syslog capture (idevicesyslog) be in the first increment, or device/app inventory only?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#6616

No description provided.

Rows
Columns