In this guide, we will show you the steps to fix the issue of Google Assistant being unable to find WhatsApp contacts in Android Auto on Samsung devices running the latest One UI 5.1. Using Android Auto and the virtual assistant from the Silicon Valley giant, you could send and receive WhatsApp messages without the need to interact with your device. However, as of late, it is giving out a tough time to a particular set of users.
Many Samsung users who have updated their devices to On UI 5.1 have reported that Google Assistant is unable to find WhatsApp contacts in Android Auto. Whenever they issue the said command, the Assistant instead replies “I’m not seeing a WhatsApp number for that contact”. Since four parties are currently involved in this fiasco, we cannot pinpoint the culprit for sure, though all possible signs point the finger toward One UI 5.1.
This is because WhatsApp, Google Assistant, and Android Auto are working well and good with other devices, the issue only occurs when using the latest iteration of the Samsung OS. With that said, there does exist a nifty workaround that should help you rectify this issue. So without further ado, let’s check it out.
Fix Google Assistant cannot find WhatsApp Contacts
- Launch the Contacts app and tap on the hamburger menu.
- Then tap on the settings icon and go to About Contacts.
- Now tap 9 times near the large ‘Contacts’ headline.
- It should then launch the 3rd Party Integrations options.
- Enable the toggle next to WhatsApp and restart your device.
That’s it. These were the steps to fix the issue of Google Assistant being unable to find WhatsApp contacts in Android Auto on Samsung devices running the latest One UI 5.1. Since the aforementioned tweak has worked out for many, it seems to be the case of new functionality being introduced into the app that users need to enable beforehand rather than a bug. And if that is indeed the case, then Samsung should do a much better job in letting its users know of the same at the earliest, rather than silently rolling out this change in the backend.
Anon
Amazing! Thank you so much for this fix. This was bugging me for a very long time!
Mike
Thank you. You’re then man!
Andrew.C
Hi, this worked perfectly thank you.