Waze App Bugs and Issues
Back to main Known Issues page.
This page is used to capture bugs and usability issues from the community as well as for the Waze client app developers to communicate back to the users which they are aware of and the status of the fix for those bugs and issues.
Acknowledged Bugs and Issues
Waze developers will use this table to list the bugs and usability issues which they have acknowledged, verified and will be fixed in future releases.
|Date||OS||Issue Description||Example Image/Link||Fix Release Versions||Status|
Community-submitted Bugs and Issues
The Waze user community is encouraged to capture verified bugs and usability issues in the following table. As community bugs are acknowledged and verified, the Waze developers will move the information from this table to the table in the Acknowledged Bugs and Issues section above.
|Date||OS||Issue Description||Example Image/Link||Workaround||Status|
|2010-11-03||HTC + Froyo screen problem when using landscape mode.||Screenshot||Starting the app in portrait, then switching to landscape will display the problem as shown in the link, but rotating back to portrait will return the screen to normal. Starting the app in landscape then rotating to portrait does not fix it.||Open|
|2011-03-16||With Automatic Night Mode set to OFF, client does not save the Mode setting for Night. Each time you start the client, the Mode reverts to Day.||Open|
|2011-03-28||App crashes at the same physical location when driving.||Open|
|2011-03-28||Adding a photo to a report freezes at the camera sceen. The back button brings you back to the report screen, but the touch screen does not respond. Hardware buttons (home or back) invoke a OS message that the app has stopped responding, and the question if you want to wait or exit the app. When you chose 'wait', you can wait forever, the only way out is to exit the app through the OS crash message, and restart.||Open|
|2011-04-06||Sometimes, the Recalculate option does not appear in the routing popup menu, especially in landscape mode.||Open|
|2011-04-07||Waze does not obey the "Event Radius" distance option when navigating, after canceling navigation, or if the routing server returns an error. The example video linked here is from the iPhone, but Android suffers the same bug.
EDIT: The Event Radius expands to include the area along your route and destination when navigating. This is by design. The confirmed BUG is that this settings stays in effect if routing is canceled or routing errors out.
|2011-06-01||The name of the next turn is not displayed when the turn after that is on to a segment which is a Ramp road type. The name displayed is the ramp name. The turning direction is correct for the next turn, but the name displayed is for the following turn.||This is a routing server bug. See Routing section below.||Open|
|Bug in code causes the client to be unable to display the following speeds:
||This is currently working as designed, but the client should not be coded in knots and then converted to mph or kph. This causes a loss of accuracy in displaying the correct speed.||Open|
|Map and vehicle take turns "scrolling" which is distracting and looks unprofessional. The map stay perfectly still while the car icon moves along the road for a short distance, then the map scrolls, moving the car backward (backward relative to the physical device, but it stays in the right place relative to the map). Affects both 2D and 3D mode.||Open|
|2011-10-15||Minimize turns setting doesn't stick between client exit/start.||Open|
|2011-10-15||Reporting "other lane" for hazards, police, etc. does not work for split roadways such as "I- 5 S" reporting for "I- 5 N"||Open|
|2011-10-20||Multiple alerts on-screen at the same time can cover up alerts with timers which are about to expire which cannot be tapped on in time.||Open|
|2011-10-20||Approaching hazard, police, speed cam, red light cam will cancel a current on-screen alert which is counting down and waiting for user response.||For example, a police report 400ft from a red-light camera. The pop-up for confirming or "not there" button for the police appears correctly, but having to wait until the right location causes the red-light alert to pop up before the "not there" button can be pressed causing the incorrect police report to remain.||Open|
|2011-10-20||User-selected zoom levels are not saved without autozoom disabled. To recreate: disable autozoom, drive, navigate, select alternate routes, view Map of alternate routes, select route. Waze map will be pinned north up and zoomed out as far as it can go instead of returning to previous user-selected zoom setting.||This issue has been on-going since the 2.0 release||Open|
|2011-10-17||Cannot tap-to-dial a phone number which is returned in search results.||Open|
|2011-10-20||Street names are mispronounced.||Waze is working with the OS built-in Text-To-Speech engine and cannot control pronunciation at this time. A future feature to allow editors to post phonetic pronunciation may be a possibility.||Open|
|2011-10-15||Navigation list is missing.||Removed on purpose. Vote for its return here.||Open|
|2011-10-18||Graphic preview of events along a route is not accurate.||http://www.waze.com/forum/viewtopic.php?f=17&t=12674||This may involve a routing server issue, too.||Open|
|2011-10-19||When the alternate routes are being processed, bonus candies are ignored and will be driven over without getting points. They remain on the map. This may happen when other alerts are on-screen too.||Open|
|2011-10-23||No more than one favorite on an unnamed (null name) street can be added in v3.0. Previous favorites on unnamed streets remain, and you can add only one with v3.0||Open|
|2011-10-25||Some users would love to have the iPod play control put back into Waze so they don't have to switch apps.||Open|
|2011-10-25||The small gray x icon on the right side of text input box gets overwritten by text and looks unprofessional.||http://www.waze.com/forum/viewtopic.php?p=107766#p107766||This may be an iOS issue as this has been seen in other apps.||Open|
|2011-11-05||When enabled, group pop-up reports do not auto close.||Open|
|2011-11-07||Text-to-speech mispronounces non-English accented characters. The é character, which the TTS seems to interpret as 'aa©'||http://www.waze.com/forum/viewtopic.php?f=3&t=13103||Do not use accented characters until resolved.||Open|
Use the following logos for the OS column: