I did my weekly trip through Nottingham and the Cannock/A5 police state zones and every speed cam warning worked as expected on iOS (and there's a lot of them)!

I'll go through recent bug reports on Centrecode and Bugzilla tomorrow and see what I can find.

faitaru wrote:I noticed this bug in iOS versions whilst on the M42 J7-J3A. Had forgotten about it until I saw this.

Happened on a couple of gantry cams. Exactly as described by the Flan.

Will pay special attention tomorrow on the M62

If you're testing for this put your Waze app into debug mode so that enhanced logs can be sent to Waze.

To do this search for 2##2

After that let me know they've been uploaded and I'll then pass the log details to Waze via centercode, screen shots of the came at the same time would be useful to tie in with the logs.

I need the following to submit a bug report:
You Device/OS version and the version of Waze you are running (see my signature for details).

Looks like you were approaching the camera with ID 2567600 here:
https://world.waze.com/editor/?zoom=4&l ... as=2567600

I can include this info in the report.

My estimate of your actual distance from the cam (by measuring the lengths of the adjacent streets) is 400m, not 30 feet!

Oh and were you in Debug mode?

I will post a bug report on Centercode and Bugzilla later. This seems to only be affecting the UK (maybe just imperial RHD countries?).

Just had a thought, can you try it to see if it does in when you're set to km?

One last thing to try ... dump you map cache as although when routing Waze loads the latest maps for your route it DOES NOT update speed cams.

To do this go to:
Menu > Settings > Advanced > Data Transfer > Refresh Map of my Area.

Bets done on Wifi or 3G as if you're on 2G it will take ages of fails altogether. If you do it with that bit of map in view it will be interesting to see if the camera moves.

When I got rid of all the now removed SPECS cams a few weeks ago I also nudged some of the variable speed cams as the gantries are now visible on the aerial photos, so just maybe Waze is confused about it's location and displaying it in the old location but warning of the new location. Probably not but worth a shot.

Bug now raised on Centercode (BUG-1011), I'll wait to see what feedback we get before raising it on bugzilla as well.

Waze have now marked the bug as a "known issue" and it has been allocated to be fixed in the "upcoming" release.