Photo: Bogdan Popa/autoevolution
Waze remains a must-have companion for modern drivers who want to deal with nightmare traffic more conveniently. Still, it's no secret that the application sometimes misbehaves in horrible ways.
The Google-owned company keeps rolling out updates at a painfully slow pace, with the new releases typically addressing just a small fix that wasn't even widespread.
The latest iOS update is living proof, as it indeed corrects a bug in the application but leaves many others without a fix after a month and a half of wait.
Waze version 4.101 landed on the App Store on January 29, promising a fix for a glitch that prevented railroad crossings from being shown correctly. It's an important release, considering railroad crossing warnings help prevent fatal accidents, but it leaves users waiting for more. The previous update was released on December 14 as version 4.100, so you can imagine that users hitting other bugs were eagerly anticipating a new build.
It's not like Waze has nothing to improve in the app.
The most recent problem plaguing Android Auto and CarPlay is that the vehicle icon goes missing randomly. As I told you in a different story, the vehicle icon mysteriously disappears with and without navigation on the screen. Most Android Auto users claim the icon is no longer displayed when navigation is not enabled.
In my case, Waze removes the vehicle icon on CarPlay when turn-by-turn guidance is running on the screen. The biggest shortcoming is that you can no longer see your location on the map, as the vehicle icon indicates your position as you drive.
Waze has never confirmed that it's investigating the error, so it's unclear if a fix for this problem is even coming.
Meanwhile, users also complain about routing issues, claiming the application sends them on alternate routes that don't make sense. However, this isn't always a bug, as Waze always looks for the fastest route. It's one of the magic parts of the app, as it helps get you to the destination faster without considering other factors, such as how difficult the route would become for you. As long as you get there faster, Waze suggests the route, obviously according to your navigation settings.
Waze voice commands have also been broken for a few weeks. It means users can no longer speak a destination in the application, so they must rely on touch input to set up navigation. It's a major problem for people who want to set a new destination while driving, as the only workaround is to pull over and use touch for configuration. The bug has plagued Android and Android Auto since December, possibly after the latest update, but no fix has appeared on the radar yet.
The latest iOS update is living proof, as it indeed corrects a bug in the application but leaves many others without a fix after a month and a half of wait.
Waze version 4.101 landed on the App Store on January 29, promising a fix for a glitch that prevented railroad crossings from being shown correctly. It's an important release, considering railroad crossing warnings help prevent fatal accidents, but it leaves users waiting for more. The previous update was released on December 14 as version 4.100, so you can imagine that users hitting other bugs were eagerly anticipating a new build.
It's not like Waze has nothing to improve in the app.
The most recent problem plaguing Android Auto and CarPlay is that the vehicle icon goes missing randomly. As I told you in a different story, the vehicle icon mysteriously disappears with and without navigation on the screen. Most Android Auto users claim the icon is no longer displayed when navigation is not enabled.
In my case, Waze removes the vehicle icon on CarPlay when turn-by-turn guidance is running on the screen. The biggest shortcoming is that you can no longer see your location on the map, as the vehicle icon indicates your position as you drive.
Waze has never confirmed that it's investigating the error, so it's unclear if a fix for this problem is even coming.
Meanwhile, users also complain about routing issues, claiming the application sends them on alternate routes that don't make sense. However, this isn't always a bug, as Waze always looks for the fastest route. It's one of the magic parts of the app, as it helps get you to the destination faster without considering other factors, such as how difficult the route would become for you. As long as you get there faster, Waze suggests the route, obviously according to your navigation settings.
Waze voice commands have also been broken for a few weeks. It means users can no longer speak a destination in the application, so they must rely on touch input to set up navigation. It's a major problem for people who want to set a new destination while driving, as the only workaround is to pull over and use touch for configuration. The bug has plagued Android and Android Auto since December, possibly after the latest update, but no fix has appeared on the radar yet.
Google News