A phone or tablet producing an unexpected result — wrong location, wrong contact, wrong output — usually traces to a permission, default-app or account setting, not a defect. For iPhone Face ID, first clean the sensor area, remove obstruction and test unlock plus one supported app.
What this covers
- iPhone Face ID with this exact failure state
- Diagnosis across attention/appearance and screen protector versus camera obstruction and hardware
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleRecord exactly which permission, default app or account is active for the feature. Expected behavior: recognize the enrolled face through an unobstructed TrueDepth system under supported conditions.
Isolate the component boundary
ReversibleClean the sensor area, remove obstruction and test unlock plus one supported app. Test with a second account or a different default app assigned to the same action. Boundary to separate: attention/appearance and screen protector versus camera obstruction and hardware.
Correct only the proven cause
ReversibleUpdate, reset and re-enroll Face ID only after passcode and app credentials are available. Correct the permission, default-app assignment or account setting proven by the comparison.
Verify and stop safely
ReversibleRepeat the original action and confirm the correct result with the fix in place. Service after impact, liquid or a TrueDepth unavailable message that persists.
Evidence ledger
Sources behind this answer
Exact questions