The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Difference between revisions of "Known issues"

From waze
Jump to: navigation, search
(WinMo welcome.png crash)
(Waze App Bugs and Issues has been obsoleted. Link removal accordingly.)
 
(113 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 +
{{Obsoleted}}
 +
 
=Service Issues=
 
=Service Issues=
 
Check for current known service issues on the [http://status.waze.com Waze Status webpage].
 
Check for current known service issues on the [http://status.waze.com Waze Status webpage].
 +
  
 
=Recent Fixes=
 
=Recent Fixes=
* iPhone 2.2.0.0 fixed the issue where road names displayed near horizontal flip upside down while driving north.
+
-
* House Numbers can be deleted again as of 2011-04-01
+
 
  
 
=Known Issues=
 
=Known Issues=
==Website (Dashboard, Community)==
+
==Waze App==
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
+
|- align="center"
+
| Date
+
! class="unsortable" | Issue Description
+
! class="unsortable" | Workaround
+
! Status
+
|-
+
|
+
| class="unsortable" | Facebook friends is not updating with new friends
+
| class="unsortable" | Go to My Dashboard and click on the Update button. There is ''no need'' to change any information or disconnect from Facebook.
+
| style="color:red;text-align:center" | Open
+
|}
+
  
==Client==
 
===Android 2.2.0.0===
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
|- align="center"
 
! width="7%" | Date
 
! width="30%" class="unsortable" | Issue Description
 
! width="25%" class="unsortable" | Example Image/Link
 
! width="30%" class="unsortable" | Workaround
 
! width="8%" | Status
 
|-
 
| 2010-11-03
 
| class="unsortable" | HTC + Froyo screen problem when using landscape mode.
 
| class="unsortable" | [http://www.waze.com/wiki/images/6/68/Waze_fail_on_hero_froyo.png Screenshot]
 
| class="unsortable" | 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.
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-03-16
 
| class="unsortable" | 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.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-03-28
 
| class="unsortable" | App crashes at the same physical location when driving.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-03-28
 
| class="unsortable" | 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.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-04-06
 
| class="unsortable" | Sometimes, the Recalculate option does not appear in the routing popup menu, especially in landscape mode.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| class="unsortable" |
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-04-07
 
| class="unsortable" | 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.
+
==Website (Dashboard, Community)==
| class="unsortable" | http://www.youtube.com/watch?v=G9mal5Pr6YI (iPhone example)
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|}
+
 
+
===iPhone 2.2.0.0===
+
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
|- align="center"
 
|- align="center"
 
| Date
 
| Date
 
! class="unsortable" | Issue Description
 
! class="unsortable" | Issue Description
! class="unsortable" | Example Image/Link
 
 
! class="unsortable" | Workaround
 
! class="unsortable" | Workaround
 
! Status
 
! Status
 
|-
 
|-
| 2011-03-26
+
|  
| class="unsortable" | When the next turn is an Exit ramp, Waze verbalizes "Exit" correctly, but on-screen, the name of the road segment is the turn ''after'' next. It does not display the name of the exit itself, which has important information such as the exit number.
+
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
| style="color:red;text-align:center" | Open
+
| style="color:red;text-align:center" |  
|-
+
|
+
| class="unsortable" | 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.
+
| class="unsortable" | http://www.youtube.com/watch?v=g3RgPDKBY48
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Pend
+
|-
+
|
+
| class="unsortable" | When the final turn to a destination is a parking lot road, and the road you are on changes names at a straight intersection, the name of the first road stays on the display until the final turn, which is not the correct road name.
+
| class="unsortable" | [http://www.waze.com/cartouche/?zoom=4&lat=45.42431&lon=-122.85144&layers=FBFTFFFFFFFFTFFFFTTTT Location and intersection] is where SW 175th Ave ends at SW Scholls Ferry Rd and SW Roy Rogers Rd takes over heading south. So, going from 175th to Roy Rogers does not require any kind of turn. Routing to a no-name/parking lot road off of Roy Rogers will result in the screen showing the next turn to be Roy Rogers, which is the street we are driving on, not the street we are turning on to.
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|-
+
| 2011-03-16
+
| class="unsortable" | 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.
+
| class="unsortable" | http://www.youtube.com/watch?v=ObLaXpWZwgs
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|-
+
| 2011-04-06
+
| class="unsortable" | Sometimes, the Recalculate option does not appear in the routing popup menu.
+
| class="unsortable" |
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|-
+
| 2011-04-07
+
| class="unsortable" | Waze does not obey the "Event Radius" distance option when navigating, after canceling navigation, or if the routing server returns an error.
+
 
+
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.
+
| class="unsortable" | http://www.youtube.com/watch?v=G9mal5Pr6YI
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
 
|}
 
|}
  
===BlackBerry===
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
|- align="center"
 
! width="7%" | Date
 
! width="30%" class="unsortable" | Issue Description
 
! width="25%" class="unsortable" | Example Image/Link
 
! width="30%" class="unsortable" | Workaround
 
! width="8%" | Status
 
|-
 
|
 
|
 
|
 
|
 
| style="color:red;text-align:center" | Open
 
|}
 
 
===Symbian===
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
|- align="center"
 
! width="7%" | Date
 
! width="30%" class="unsortable" | Issue Description
 
! width="25%" class="unsortable" | Example Image/Link
 
! width="30%" class="unsortable" | Workaround
 
! width="8%" | Status
 
|-
 
|
 
|
 
|
 
|
 
| style="color:red;text-align:center" | Open
 
|}
 
 
===Windows Mobile===
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
|- align="center"
 
! width="7%" | Date
 
! width="30%" class="unsortable" | Issue Description
 
! width="25%" class="unsortable" | Example Image/Link
 
! width="30%" class="unsortable" | Workaround
 
! width="8%" | Status
 
|-
 
| 2011-04-15
 
| class="unsortable" | Application begins to crash after a few uses.
 
| class="unsortable" |
 
| class="unsortable" | The problem appears to be related to the welcome.png file found in Program Files\Waze\skins\default\. Deleting this file allows Waze to run until it downloads a new copy and the crashing will start again.
 
| style="color:red;text-align:center" | Open
 
|}
 
  
==Cartouche (Map Editing)==
+
==Waze Map Editor==
* While server upgrades have markedly increased the speed of [[Cartouche]] there are times of day when it is still very slow. This may be because the servers are performing other tasks or because there are many map editors working at the same time. If you find the map editing to be painfully slow, we don't want you to become discouraged. The best advice is to wait and try again at a different time of day
+
* Always check [http://status.waze.com waze status] for the latest issues and information.
* If you have the GPS Points layer selected it can be difficult or impossible to select a road because you are always selecting a GPS point. This can happen even if the GPS points are not visible at your current [[zoom level]]
+
* Newly plotted (unknown, red-line) roads are not showing in [[Cartouche]] at the 3 minimum [[zoom level|zoom levels]]
+
* [[Bugs can occur when deleting junctions]]
+
  
  
Line 182: Line 35:
 
* All
 
* All
 
* NA (North America)
 
* NA (North America)
* World (Global except for North America)
+
* INTL (Global except for North America)
  
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
 
{| class="wikitable sortable" style="background:none; font-size:80%; margin: 1em auto 1em auto" border="1"
Line 193: Line 46:
 
! width="8%" | Status
 
! width="8%" | Status
 
|-
 
|-
|
+
| 2012-03-21
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Unable to create roads from Archive
+
| class="unsortable" | "My places | Drives" archive is often displaying some drives incorrectly marked as "Yesterday" or "Today".
 +
| class="unsortable" | http://www.waze.com/forum/viewtopic.php?f=10&t=15409&start=210#p145399 + http://www.waze.com/forum/viewtopic.php?f=22&t=16204&start=30#p149788
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Using "Record New Roads" feature in client
 
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
|
+
| 2012-03-21
| align="center" | All
+
| align="center" | INTL
| class="unsortable" | House numbers location changes slightly after saving an update. This is because the house number re-centers to the precise location of the mouse click which selected it. This will cause house numbers to drift.
+
| class="unsortable" | If a lower-ranking editor (no AM) creates all segments, joined in a junction and a higher-ranking editor locks all of them, the segments' former author can still modify their connectivity arrows through the junction.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Recommended to stop creating and updating house numbers.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | NA
 
| class="unsortable" | House numbers repeatedly fail to permanently save (turn blue) due to various reasons.
 
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Recommended to stop creating and updating house numbers.
 
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
|
+
| 2012-03-05
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Changes in street names for house numbers are not saved.
+
| class="unsortable" | City layer does not update when city/state/country attributes are changed on segments.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Recommended to stop creating and updating house numbers.
+
| class="unsortable" | The city layer does update, but seldom, giving the impression it doesn't update at all. Waze will enable faster updates at a date to be determined.
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
|
+
| 2012-02-12
| align="center" | NA
+
| class="unsortable" | House numbers street name turns blank immediately after creating and saving.
+
| class="unsortable" |
+
| class="unsortable" | Recommended to stop creating and updating house numbers.
+
| style="color:red;text-align:center" | Open
+
|-
+
|
+
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | House numbers cannot contain any characters other than numbers.
+
| class="unsortable" | Adding a new segment to an existing segment and panning while adding the new segment because it is longer than will fit on the screen, will cause the editor to duplicate the original segment and this will cause an error and will not save.
| class="unsortable" |  
+
| class="unsortable" | http://www.waze.com/forum/viewtopic.php?f=10&t=16200
| class="unsortable" | This is currently working as designed.
+
| class="unsortable" | Draw a short segment first and save, then extend the segment.
| style="color:red;text-align:center" | Open
+
| style="color:green;text-align:center" | Resolved (2012-11-05)
 
|-
 
|-
| 2011-03-13
+
| 2012-02-12
| align="center" | NA
+
| class="unsortable" | Update Requests changes cannot be saved. Whether you are adding notes, changing type or status, changes to Update Requests result in "Internal Server Error"
+
| class="unsortable" |
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|-
+
| 2011-03-16
+
| align="center" | NA
+
| class="unsortable" | Pending (Deletions) panel does not appear after clicking on the link in the View panel, and the Pending link then disappears.
+
| class="unsortable" |
+
| class="unsortable" | Observed in case of timed-out edit session. Try to refresh the page to re-login.
+
| style="color:red;text-align:center" | Open
+
|-
+
|
+
| align="center" | ALL
+
| class="unsortable" | Pending (Deletions) panel does not show user name of the submitter.
+
| class="unsortable" |
+
| class="unsortable" |
+
| style="color:red;text-align:center" | Open
+
|-
+
|
+
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Landmark changes/updates occasionally fail. This appears to happen on very large landmarks, or landmarks with a large number of perimeter vertices.
+
| class="unsortable" | Cannot delete an unlocked segment last edited by a higher-ranking editor.
 +
 
 +
Location: Outside AM area, inside Editable Area
 +
Object: Unlocked segment
 +
 
 +
Previous edit by: Higher-ranking editor
 +
 
 +
Action not allowed: Deletion
 +
 
 +
Actions allowed: all others
 +
 
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" |
+
| class="unsortable" | Modify segment geometry. The segment can then be deleted.
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
|
+
| 2011-11-13
| align="center" | NA
+
| align="center" | INTL
| class="unsortable" | Cannot update geometry of new (red) roads until the road is given a type, state and name.
+
| class="unsortable" | Sometime, when saving edits (not necessarily to a roundabout), it will result in an error and the highlight will show the error on a roundabout in another country.
| class="unsortable" |  
+
| class="unsortable" | http://www.waze.com/forum/viewtopic.php?f=186&t=13280 + http://www.waze.com/forum/viewtopic.php?f=10&t=15409&p=143027#p142916
| class="unsortable" | This may be working as designed. Workaround is to Edit the street, set the State if not set, and save before attempting to update geometry.
+
| class="unsortable" | Undo some of the changes and try edits again. Possibly the undo is not necessary at all!
| style="color:red;text-align:center" | Open
+
|-
+
|
+
| align="center" | ALL
+
| class="unsortable" | Orphan nodes are hidden and are sometimes selected even when you cannot see them.
+
| class="unsortable" |
+
| class="unsortable" | Delete them when you find them. When deleting road segments, remove them in such a way as to be able to remove road-end segments before deleting the road segment.
+
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Editing roads of multiple types will change all roads to type 'Street' upon saving.
+
| class="unsortable" | Separating line checkbox is unavailable.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Only edit roads of the same type per edit.
+
| class="unsortable" | Separating line will be not be added to the Waze Map Editor, and the display of the separating line on Primary Street road type will be removed. There is no use for this option.
| style="color:red;text-align:center" | Open
+
| style="color:green;text-align:center" | Resolved (removed)
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Alt. Steet (Alias) road names can only be saved for a single segment at a time. Multiple segment selections will result in no changes (add/change/remove) to the Alt names.
+
| class="unsortable" | Map error "Missing Road" shows way too often and in places where there are very few GPS tracks.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Only make changes to Alt Names on single segment edits.
+
| class="unsortable" | There is a flaw in the detection algorithm for this error which has been identified. A fix is supposed to go in by early November 2011. It seemed to work for a while, but recent evidence suggests it is still too sensitive to single outliers.
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | English City Name field cannot be cleared/deleted.
+
| class="unsortable" | Reverse connectivity is enabled when one-way roads are split in Waze Map Editor.
| class="unsortable" |  
+
| class="unsortable" | http://www.waze.com/forum/viewtopic.php?p=92528#p92528
| class="unsortable" |  
+
| class="unsortable" | Select the new junction and use the "Disallow all connections" function or keyboard shortcut, then individually all correct connections.
| style="color:red;text-align:center" | Open
+
 
 +
UPDATE 2012-02-27: Waze Map Editor beta now properly allows all connections according to connected segment directionality.
 +
| style="color:green;text-align:center" | Resolved (2012-11-05)
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Alt Street names are deleted when changing road Geometry.
+
| class="unsortable" | Cannot add alternate names.
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
| style="color:red;text-align:center" | Open
+
| style="color:green;text-align:center" | Resolved (2012-11-05)
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Segments cannot be selected with the "No Name Roads" layer enabled.
+
| class="unsortable" | "Add intersection" sign for crossing segments doesn't appear reliably.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | Find a no-name road with the layer enabled, then disable it to select the road.
+
| class="unsortable" | Segments must be set to the same level, country, state (where applicable) and city. For recently drawn or modified segments which now cross each other at the same level, you may need to use the Permalink to reload the current view. The Add Intersection icon should appear above the intersection when both segments are selected.
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
 
|
 
|
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | Safari on Windows does not display borders of controls (checkboxes, select menus, text boxes) with the Aerial Layer enabled. Checkboxes do not display their state at all.
+
| class="unsortable" | A dead end road with no junction at the end will cause routing problems for the road as a departure point. When creating a new dead-end road in the editor, a junction is not automatically applied.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" |
 
* Use another browser such as Chrome.
 
* Disable Aerial layer as necessary to see the status of checkbox controls. Other controls can still be selected and used, they are just harder to see.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | ALL
 
| class="unsortable" | GPS points are not selectable.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | Highlight connectivity may not display correctly, especially for very recent changes.
 
| class="unsortable" |
 
| class="unsortable" | This is due to database refresh and tile refresh timing. Deselect the segment(s), change zoom level, then select segment(s) again and connectivity highlighting should be correct.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | Restricted turn layer is not accurate.
 
| class="unsortable" |
 
| class="unsortable" | Do not use the Restricted Turn layer
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | NA
 
| class="unsortable" | Only Area Managers can edit a Landmark. If you create a landmark and are an Area Manager, if any portion of the Landmark falls outside your managed area, you will not be able to edit it.
 
| class="unsortable" |
 
| class="unsortable" |
 
* Create Landmarks that fall completely within your managed area.
 
* Request an increase to your managed area.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | The prompt for speed camera speed asks for mp/h, but if your country uses km/h then the entered speed will be taken as km/h.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | Names containing single and double quotes (' and ") are not handled correctly
 
| class="unsortable" |
 
| class="unsortable" | Avoid entering names using single and double quotation marks.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | Need to refresh browser to select roads after adding street
 
| class="unsortable" |
 
| class="unsortable" | This behavior is working as designed in order to reduce the load on the server by batching certain types of updates.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | Autocomplete City and Street text boxes produces inaccurate suggestions.
 
| class="unsortable" |
 
| class="unsortable" |
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-03-08
 
| align="center" | All
 
| class="unsortable" | Cartouche allows panels to be dragged vertically (accidentally) off the screen and they become unretrievable unless cache/cookies are deleted. Both Safari and Firefox allow the panels to be dragged up or left beyond the page and application window. At this point, the browser does not recognize or allow you to scroll up or left to retrieve the panel. Dragging right or down beyond the page does give scrollbars, but not panels dragged up or left.
 
| class="unsortable" |
 
| class="unsortable" | Empty your browser cache.
 
| style="color:red;text-align:center" | Open
 
|-
 
|
 
| align="center" | All
 
| class="unsortable" | When enabling the Map Problems layer, the View Panel defaults to showing problem Type 1, though the map itself seems to display ''all'' errors.
 
| class="unsortable" |
 
| class="unsortable" | Change the Type selection to whatever you wish, typically 'All', 'Scan' or 'Merger' and you will then be able to select the problems which appear on the map.
 
| style="color:red;text-align:center" | Open
 
|-
 
| 2011-02-14
 
| align="center" | All
 
| class="unsortable" | The Map Problem drop-down menu for Type is dramatically different on different browsers.
 
* Firefox has the most limited and badly sorted list; it doesn't contain "Merger" or "All"
 
* Chrome and Safari tie for the longest list
 
* Safari appears to be the best for organization
 
| class="unsortable" | [http://www.waze.com/forum/viewtopic.php?f=10&t=8162 Forum thread "Why? Browser differences in Map Problem Type dropdown menu"]
 
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
Line 414: Line 153:
 
|-
 
|-
 
| align="center" | All
 
| align="center" | All
| class="unsortable" | In general, there is a 200 mile/ 320km restriction on navigation routes.
+
| class="unsortable" | In general, there is a 650 mile/ 1047km restriction on navigation routes.
 
| class="unsortable" |  
 
| class="unsortable" |  
| class="unsortable" | There have been instances where much longer routes have been achieved, especially as of March 2011.
+
| class="unsortable" | Some locations may still be restricted to 200 mile/322 km routes. The client will usually display that it cannot do routes over 1000 miles, but the real limit is around 650.
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|-
 
|-
Line 423: Line 162:
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
 
| class="unsortable" |  
| style="color:red;text-align:center" | Open
 
|-
 
| align="center" | All
 
| class="unsortable" | Roundabout spoken instructions do not consistently speak "At the roundabout, take the nth exit." Instead, it will speak, "Turn left" or "Continue straight." This behavior is working as designed, but the community overwhelmingly desires all roundabouts to consistently use the "exit" instructions.
 
| class="unsortable" |
 
| class="unsortable" | There are ways to construct a roundabout to force the "exit" instructions, but this is not a desireable workaround.
 
 
| style="color:red;text-align:center" | Open
 
| style="color:red;text-align:center" | Open
 
|}
 
|}

Latest revision as of 08:25, 13 April 2015

This information is obsolete and the active links to this page have been reviewed for disconnection or replacement. More current alternate information is likely available and should be followed rather than this information.

Service Issues

Check for current known service issues on the Waze Status webpage.


Recent Fixes

-


Known Issues

Waze App

Website (Dashboard, Community)

Date Issue Description Workaround Status


Waze Map Editor

  • Always check waze status for the latest issues and information.


In the table below, "Region" values are as follows:

  • All
  • NA (North America)
  • INTL (Global except for North America)
Date Region Issue Description Example Image/Link Workaround Status
2012-03-21 All "My places | Drives" archive is often displaying some drives incorrectly marked as "Yesterday" or "Today". http://www.waze.com/forum/viewtopic.php?f=10&t=15409&start=210#p145399 + http://www.waze.com/forum/viewtopic.php?f=22&t=16204&start=30#p149788 Open
2012-03-21 INTL If a lower-ranking editor (no AM) creates all segments, joined in a junction and a higher-ranking editor locks all of them, the segments' former author can still modify their connectivity arrows through the junction. Open
2012-03-05 All City layer does not update when city/state/country attributes are changed on segments. The city layer does update, but seldom, giving the impression it doesn't update at all. Waze will enable faster updates at a date to be determined. Open
2012-02-12 All Adding a new segment to an existing segment and panning while adding the new segment because it is longer than will fit on the screen, will cause the editor to duplicate the original segment and this will cause an error and will not save. http://www.waze.com/forum/viewtopic.php?f=10&t=16200 Draw a short segment first and save, then extend the segment. Resolved (2012-11-05)
2012-02-12 All Cannot delete an unlocked segment last edited by a higher-ranking editor.

Location: Outside AM area, inside Editable Area Object: Unlocked segment

Previous edit by: Higher-ranking editor

Action not allowed: Deletion

Actions allowed: all others

Modify segment geometry. The segment can then be deleted. Open
2011-11-13 INTL Sometime, when saving edits (not necessarily to a roundabout), it will result in an error and the highlight will show the error on a roundabout in another country. http://www.waze.com/forum/viewtopic.php?f=186&t=13280 + http://www.waze.com/forum/viewtopic.php?f=10&t=15409&p=143027#p142916 Undo some of the changes and try edits again. Possibly the undo is not necessary at all! Open
All Separating line checkbox is unavailable. Separating line will be not be added to the Waze Map Editor, and the display of the separating line on Primary Street road type will be removed. There is no use for this option. Resolved (removed)
All Map error "Missing Road" shows way too often and in places where there are very few GPS tracks. There is a flaw in the detection algorithm for this error which has been identified. A fix is supposed to go in by early November 2011. It seemed to work for a while, but recent evidence suggests it is still too sensitive to single outliers. Open
All Reverse connectivity is enabled when one-way roads are split in Waze Map Editor. http://www.waze.com/forum/viewtopic.php?p=92528#p92528 Select the new junction and use the "Disallow all connections" function or keyboard shortcut, then individually all correct connections.

UPDATE 2012-02-27: Waze Map Editor beta now properly allows all connections according to connected segment directionality.

Resolved (2012-11-05)
All Cannot add alternate names. Resolved (2012-11-05)
All "Add intersection" sign for crossing segments doesn't appear reliably. Segments must be set to the same level, country, state (where applicable) and city. For recently drawn or modified segments which now cross each other at the same level, you may need to use the Permalink to reload the current view. The Add Intersection icon should appear above the intersection when both segments are selected. Open
All A dead end road with no junction at the end will cause routing problems for the road as a departure point. When creating a new dead-end road in the editor, a junction is not automatically applied. Open

Routing

Region Issue Description Example Image/Link Workaround Status
All In general, there is a 650 mile/ 1047km restriction on navigation routes. Some locations may still be restricted to 200 mile/322 km routes. The client will usually display that it cannot do routes over 1000 miles, but the real limit is around 650. Open
World The icon display for roundabout directions are incorrect for countries that drive on the left. Open