Oh No: Pixel 4 Owners Getting "Can't Verify Face" Message

Ruben Fields
January 13, 2020

So far, Google doesn't seem to be aware of the Face Unlock problems on Pixel 4 as the company has not officially announced an update to fix the problem. Apparently, users are experiencing issues with this feature on both Pixel 4 and the Pixel 4XL following the last few updates.

For those affected, two subtly different error messages are appearing when they attempt to use face unlock, which could indicate two different but potentially similar problems: "Can't verify face". Meanwhile, a number of users first incurred the problem after updating their Pixel 4 phones with the December security patch. It shows this error "Can't verify face, try again" when the user try to use the biometric authentication in the Pixel device. Multiple reports of vexed Pixel 4 users have surfaced on the official Pixel support forum as well as Reddit.

For some users, they abruptly started receiving system notifications asking them to re-register their face again, despite the face unlock functioning fine. Not only do you get to take advantage of the price cut, you'll also receive a $200 gift card when you buy either of these phones.

Edelman arrested for vandalism, jumping on hood of auto
TMZ Sports reports that the Patriots wide receiver was arrested for allegedly jumping onto someone else's Mercedes-Benz vehicle . According to TMZ Sports, Edelman was walking around Beverly Hills around 9 p.m. when he jumped on a vehicle causing damage.

These messages prompted users to re-add face data but the problem still persists. For many, the issue first appeared immediately after receiving one of Google's (recently delayed) monthly security updates, though it's also occurring without any apparent triggering action for others.

Fixes, like deleting face data and reconfiguring face unlock; and restarting the Pixel 4 in safe mode, don't work. Some users have even tried to factory reset their device but it has not always been successful. If you are experiencing this issue, I hate to say it, but a factory reset might fix you right up.

Other reports by

Discuss This Article