The integration with AA continues to be frustratingly limited by the insistence upon making the mobile app unusable while connected.

After recent updates, I find it nearly impossible to navigate anywhere of I'm driving and connected to Android Auto. When I use the voice search, it correctly identifies what I asked to search for but then lists no results. If I tap an address link from my phone (ie: from a Contact detail view) and open the link with Waze, this integration has broken down and the address never gets passed through to the head unit. I can't search for anything using the deck while in motion because it disables the keyboard. So, basically, if I'm in motion and need directions, the only locations Waze will allow me to navigate to while connected are my presets for Home/Work and my most recents. For anything else, I would need to pull over.

This isn't practical; it's a horrible user experience; and it's unlikely to be the solution most users will opt for.

The silly "safety precautions" of limiting interaction on the head unit and doubling down by disabling interaction with the mobile app come from what I would imagine are good intentions: don't encourage distracted driving. My argument against them, though, is that you aren't mitigating that risk: in fact, you're increasing it. People are much less likely to pull off the road just to select an address they already have listed on their phones. They're more likely to simply disconnect AA, let Waze work properly to start navigation, then reconnect AA. Your insistence on making the interaction more tedious and frustrating to use while driving only creates more of a distraction while users are forced to spend even more time not focused on the road.

Please fix the passthrough so that Waze, while connected to AA, can successfully receive an address and start navigating to it while driving.

Also, please stop trying to force good driving habits and general behavior on users and stick to making your app work as great as possible.