Hi Support Team!
In the last couple of weeks, we have been facing issues with users that changed their old mobiles to iPhone 17.
When users used to work with their old mobiles, they had no problems.
But, when they moved to iPhone17, they initially get error 5 (PAD_ATTACK) several times, and suddenly, they start getting error 14 (TIMEOUT).
I looked over the FaceIO Community Forum, but I couldn't find any similar case.
1. Do you know about a similar case among your users?
2. Do you know if there is a hardware or software issue with iPhone17 that causes the behavior I described?
3. If so, are you working on a fix to solve it?
Thanks in advance!
Carlos.
iPhone 17 FaceIO Error 5 and 14 Issues
Asked
Modified
Viewed
1408 times
✓ Accepted Solution
Hello,
Thank you for reaching out, and welcome to the FACEIO support center. To answer your inquiry:
We have not identified any systematic issue specifically tied to iPhone 17 devices so far. In most reported cases with newer iPhones, the behavior you describe is usually related to camera pipeline changes, browser camera permissions, or environmental capture conditions rather than a hardware defect.
Regarding the specific errors:
• Error 5 (PAD_ATTACK) typically indicates the anti-spoofing layer detected conditions resembling a presentation attack. With newer iPhones this can happen due to strong HDR processing, screen reflections, aggressive exposure correction, or face proximity to the device screen. Glass reflections, bright lighting, or secondary displays near the face can also trigger it.
• Error 14 (TIMEOUT) usually follows repeated failed capture attempts. The SDK aborts the session when stable frames cannot be obtained within the allowed time window. This is often seen after several PAD detections or unstable camera exposure cycles.
To improve stability on newer iPhones:
- Ensure the camera permission is fully granted and persistent in Safari/Chrome settings.
- Confirm SDK version. We have recently rolled out fio.js v3 (refer our blog announcement post). Please make sure your site is loading the latest version and not an older cached copy.
- Avoid strong backlighting, reflections, or screens close to the face
- Keep the device at a natural arm distance with steady framing
- Make sure users are not switching apps mid-session (iOS camera interruptions can cause timeouts)
- Check that the page is fully HTTPS with no mixed content
We are continuously refining the capture pipeline to adapt to new mobile camera stacks and browser updates. Improvements roll out progressively without requiring changes on your side.
