In this guide, we will show you a nifty workaround that should help you mitigate the issue of fingerprint lock not working on WhatsApp. When it comes to instant messaging services, then there’s hardly an iota of doubt that the offering from Meta is the best in this domain. While there’s always a privacy risk involved whenever Meta is associated with a service, however, in this app, all the chats and associated data are end-to-end encrypted and it cannot be deciphered by anyone.
To further enhance the security, you could opt for app-based protection measures as well, such as implementing two-factor authentication and a lock screen. if we talk about the latter, then you have the option to protect your chats via a fingerprint. However, as of late, it’s giving quite a tough time to many. Numerous users have voiced their concern that the fingerprint lock isn’t working along the expected lines with WhatsApp.
According to the users, if they open the app for the first time, they do get the fingerprint prompt, but that’s just about it. From subsequent times, no such prompt appears and anyone could easily open the app and access the chats, which could translate to a major privacy scare. So is there a way out? Well, there does exist a nifty workaround that might help you mitigate this issue. So without further ado, let’s check it out.
Fix WhatsApp Fingerprint Lock not working
To rectify this issue, you just need to close the app from the Recent Apps screen. So wipe up from the bottom of the screen and leave it midway. This will bring up the Recent Apps, from there, simply swipe up WhatsApp to close. Now relaunch the app and you should get the fingerprint prompt. Apart from that, you may also force stop the app [via Settings > Apps > All Apps > WhatsApp > Force Stop > OK] to rectify this issue, however, it’s a tad bit lengthier process when compared to its counterpart.
Anyway, the choice is all yours, try out either of the two methods and it should help you fix the issue of the fingerprint lock not working on WhatsApp. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
