Understand readiness checks
Distinguish a connected computer, a visible phone, and a phone ready for automation.
Check readiness from the computer outward: PC Agent, Host Deps, then the individual Device.
Check the three layers
| Check | Meaning | Next action if it needs attention |
|---|---|---|
| PC Agent connection | Titan can communicate with the computer running the agent | Open the agent and check the host's internet connection |
| Host Deps | The computer's required device services and bundled tools have been checked | Follow the affected dependency's guidance |
| Device readiness | The particular iPhone meets the reported runtime or provisioning checks | Open the device and resolve the named check |
An online device is not automatically ready for every operation. An unknown or unavailable check also does not count as passed.
Runtime Readiness
Open Devices, select the phone, and choose Runtime Readiness. Read the summary and the checks needing attention. These can relate to device communication, the automation control service, or screen capture.
If a check exposes Re-check, Retry, or another action, use the action for that check and wait for fresh status. Keep the phone connected and respond to any prompt on its screen.
Provisioning Readiness
This section reports checks such as:
- Supervised: whether the phone has the supervision setup needed by supervised workflows.
- Trusted (paired): whether the host has the required trust relationship.
- Wi-Fi profile: whether the expected profile is present.
- Trust-popup blocked: whether the required supervision profile is applied.
- Developer Mode: whether the phone reports Developer Mode enabled.
- Passcode off: whether the phone meets the passcode requirement of the supervised setup.
Use the supervision manual for provisioning. Developer Mode and passcode changes require action on the iPhone; a dashboard check cannot silently change them.
Recheck after a change
After enabling a setting, repairing trust, installing profiles, or reconnecting a phone, use Re-check or the relevant validation action. Wait for the displayed result to update.
If an action's result is unconfirmed, recheck the device before sending it again. A missing response does not prove the original action failed.
If the computer's checks are failing too, resolve Host Deps first.