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
2011-10-15		Navigation list is missing.		Removed on purpose in version 3.0. After Lots of community requests Feature added back in to iOS v3.1 and pending release into next Android version.	Pending

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.

}

OS icons

Use the following logos for the OS column:

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-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.		Open
2011-06-02		Bug in code causes the client to be unable to display the following speeds: mph: 7, 15, 22, 30, 38, 45, 53, 60, 68, 76, 83, 91, 99, 106, 114, 121, 129, 137, 144 kph: 2, 4, 6, 8, 10, 12, 13, 15, 17, 19, 21, 23, 26, 27, 28, 30, 32, 34, 36, ...		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
2011-02-03		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.		Minimize turns setting is ignored by the routing server and is always on. This option will likely be removed from the app in the future.	Pending
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-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-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.			Resolved
2012-02-01		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. Edit: The 1st unnamed street favorite disappear only when the application restart.		This was resolved on iOS in version 3.1	Resolved
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-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
2011-12-12		When navigating in landscape mode and the network signal is lost, the "next road" caption at the top of the screen reverts to the size of the portrait mode. It'll stay like this until the route recalculates.			Open
2011-12-14		When in landscape mode, the Report menu icons will disappear if you do this: tap open the report menu, swipe to the 2nd set of icons, turn the phone to porttrait.		Close the report menu and reopen, or rotate back to landscape, which will show you the first icon set again, then rotate back to portrait again.	Open
2012-01-14		Prefer goodie munching doesn't operate properly. It does operate dangerously, telling the driver to make illegal turns and drive the wrong way on 1-way streets.		"Prefer goodie munching" has been removed from the US/Canada infrastructure, but though Waze promised to remove it, as of June 2012, it is still an option for the rest of the world and still causes problems.	Open
2012-01-20		When driving above certains speeds with autozoom by speed turned on, on a normal street in non-navigation mode, the street you are driving on disappears.		This is really just a known limitation.	Open
2012-03-15		Properly named highway and freeway segments do not always properly display the shield and often, for freeways, show a mix of shields and names. This bug is confirmed by Waze.			Open
2012-08-21		v3.2.1.0: 'Show on map/speed cams' is not honored. In France, using this feature is forbidden, and heavy fined.			Open