Similar issue with my 11 Pro. Certain it’s hardware failure.
why would a reboot fix a hardware failure?
I had it happen on my XR. I dropped the phone, and it somehow borked a sensor. With the sensor out, it's somehow tied to the Face ID, so it wouldn't work. Fortunately I had Apple Care, so they just gave me a new phone in store.For some reason, sometimes FaceID stops working on my iPhone X, and it doesn't start working back until I reboot the phone. It doesn't matter if I enter my pin a hundred times. Any idea?
If the OP is in the USA, he doesn't have AppleCare+ and it's over a year old they won't unless you pay out of warranty cost... It's also possible it may be over two years old...This is hard to explain. But this is guaranteed hardware failure. Take the phone to Apple, they will replace your handset.
If the OP is in the USA, he doesn't have AppleCare+ and it's over a year old they won't unless you pay out of warranty cost... It's also possible it may be over two years old...
It happens. On my iPhone 11 a reboot didn’t work. But after resetting faceid and adding back my face it worked again. It’s just iOS 13 being flakey
Similar issue with my 11 Pro. Certain it’s hardware failure.
This is hard to explain. But this is guaranteed hardware failure. Take the phone to Apple, they will replace your handset.
It happens. On my iPhone 11 a reboot didn’t work. But after resetting faceid and adding back my face it worked again. It’s just iOS 13 being flakey
I am having the exact same behaviour on my iPhone X with 13.5 (and 13.5.1) - if I reboot I can FaceID to function again. It's seems like it's breaking when changing network - moving from an area with WiFi to an area without WiFi and perhaps even caused by very poor coverage. Every time I use the elevator to get in our out of my apartment I loose all connections and it seems to be related to this - it never happens when I am at home/work with good WiFy connection.
I have tried resetting my phone to factory settings a reinstalling from an iCloud and setting up FaceID again in the process and this didn't fix the issue for me - I hardly think this is a hardware failure.