Improve reporting with ios list --details - #836
Conversation
outputDetailedList and its NoJSON counterpart already collect device name in allValues. Add DeviceName to DetailsEntry struct and report it. Since user configured device names can contain spaces, adjust outputDetailedListNoJSON to separate tokens with semicolons instead of spaces to avoid ambiguous token separation.
Translates Apple internal device identifiers (e.g. iPhone17,3) into the marketing name (e.g. iPhone 16). Users can more easily identify a particular device shown in "ios list" output with this translation step.
|
/test-devices |
|
❌ Real-device tests failed — see run. |
|
Looks to be that the changes to output of |
|
Good diagnosis, @outcast36 — that's exactly it. The e2e suite has a test that asserts the While you're in there, one related thing worth folding into the same pass: |
2 participants
Adds device name to the output of
ios list --details. Also translates the reported product type to the public marketing name (e.g. iPhone17,3 -> iPhone 16). These two additions make it easier to identify particular devices when there are multiple devices available.Upstream output of
ios list --details:JSON:
NoJSON:
00008140-000278EC3E87001C iPhone OS iPhone17,3 26.2.1 USB
00008110-00087129360A801E iPhone OS iPhone14,4 26.4 USB
Revised output:
JSON:
NoJSON:
00008140-000278EC3E87001C;iPhone OS;iPhone 16;26.2.1;iPhone;USB
00008110-00087129360A801E;iPhone OS;iPhone 13 Mini;26.4;iPhone;USB
Tested with a handful of real iOS devices on Fedora 39.