Device information
Everything the device will state about itself, in one pane.
What is there
Section titled “What is there”| Field | Why you care |
|---|---|
| Name and model | Which handset this actually is, not what the sticker says |
| UDID | The identifier a development provisioning profile has to contain before a build will install |
| Serial number | Warranty and provenance |
| iOS / iPadOS version | The single most common explanation for “only on that phone” |
| Storage | Total and free. A nearly-full device fails installs and behaves strangely under memory pressure |
| Battery health | Capacity against design, and cycle count |
| Battery serial | Whether the battery is the original one |
| Chip and memory | What the performance numbers should be read against |
| Network | Carrier, and whether Wi-Fi debugging is available |
The UDID
Section titled “The UDID”This is what you need most often. A development or ad-hoc profile lists the devices it may install on, by UDID; if the device is not in that list, installing the IPA fails with a signature error and no useful explanation.
Copy it from here and add it to the profile — no Mac and no Xcode in the loop.
Telling a stock device from an altered one
Section titled “Telling a stock device from an altered one”Worth doing before a device joins a test fleet, and worth doing when a bug reproduces on exactly one handset:
- Battery serial against the device serial. A replaced battery is not a problem in itself, but it tells you the device has been opened.
- Cycle count against apparent age. A “nearly new” device with 800 cycles is not nearly new.
- Storage against the model. A capacity that does not correspond to any shipped configuration is a strong signal.
- iOS version against what Apple ships. A build number that does not exist deserves a second look.
- Installed profiles. An unexpected MDM or configuration profile changes how the device behaves, sometimes drastically.
None of these is proof on its own; together they are usually enough to decide whether a device belongs in a test result.
Device operations
Section titled “Device operations”Two small things that live here and save a walk across the room:
- Restart the device.
- Rename it, which is how a rack of eleven identical iPhones becomes navigable.
Reading performance in context
Section titled “Reading performance in context”Before comparing two performance captures, compare the two devices. Different chip, different memory, different iOS version, different thermal state, different battery health — any one of those makes the comparison meaningless. Note the device information alongside the capture.