krankyd wrote:From what I can see, the map has updated since (see attached).
Can you please try and 'refresh map' on your Android? Or try and install the latest beta (if supported on your device) to see if this issue is still happening?
I don't think there's a general problem with all updates of a specific date.
rlpl wrote:As it has been mentioned before, routing works fine despite the broken tiles and the new tiles are correct if the roads have been edited after the issue. Of course I don't know all details so may be wrong but it really looks like forcing rebuild of the broken tiles should fix the problem.
rlpl wrote:krankyd wrote:Or try and install the latest beta (if supported on your device) to see if this issue is still happening?
... could this issue be version dependent? Does 2.9/3.0 series use different map tiles? Will the tiles for 2.0.x be left broken?
rlpl wrote:foxitrot wrote:rlpl wrote:... could this issue be version dependent? Does 2.9/3.0 series use different map tiles? Will the tiles for 2.0.x be left broken?
I can not imagine Waze would maintain even more different sets of tiles 3a) 3b) 3c)... for various clients...
Why not? If they already maintain 3 or maybe 7 tile sets why not to have the 8th set? They said that 3.0 client is rewritten from scratch, why shouldn't it use a separate tile set?
foxitrot wrote:Yes, seems like we've got fresh new maps today (from 29.12.2011), thanks.
Maybe the problem is indeed not general. But single instances still do exist. One example from my side: [image1] Corresponding Papyrus permalink and screenshot: https://world.waze.com/cartouche/?zoom= ... =141882804 [image2]
redmek wrote:I don't get a map at all since upgrading to version 3.0 on ice cream sandwich (Galaxy Nexus)