iOS beta 3.5.0.995 feedback thread

[AlanOfTheBerg]

I've been getting this a lot. I agree that it shouldn't pop up until something's been selected.

Is there still a hard limit on route length? I remember it was 200 mi years ago, increased to 1000 mi some time ago, but I used Waze for an 1100+ mile drive last month...

Subsequently, I've verified this isn't limited to contacts searches, but is more related to the very repeatable crash error I posted later.

[AlanOfTheBerg]

Bug: alternate routes map view doesn't display stop route

1. Plan a route and a stop
2. Request alternate routes
3. View Map mode

What shows: routes from current location to destination
What should show: routes from current location to stop point to destination

alt_routes_with_stop_map.png (92.42 KiB) Viewed 443 times

[Dave2084]

Speed Camera units bug:

Speed camera warnings have the same numerical value regardless of the users choice of units. So if a speed camera is recorded as 40km/h in WME then it will trigger an audible warning at 41km/h or 41mph.

For Example, this speed camera is set in WME for 40km/h (25mph):

When set to mph in the Client:
1. Approaching at 25mph (40km/h) does not trigger an audible warning
2. Approaching at 40mph (64km/h) does not trigger an audible warning
3. Approaching at 45mph (72km/h) does trigger an audible warning

When set to km/h in the Client:
1. Approaching at 25km/h (15mph) does not trigger an audible warning
2. Approaching at 40km/h (25mph) does not trigger an audible warning
3. Approaching at 45km/h (28mph) does trigger an audible warning

[jasonh300]

When set to mph in the Client:
1. Approaching at 25mph (40km/h) does not trigger an audible warning
2. Approaching at 40mph (64km/h) does not trigger an audible warning
3. Approaching at 45mph (72km/h) does trigger an audible warning

When set to km/h in the Client:
1. Approaching at 25km/h (15mph) does not trigger an audible warning
2. Approaching at 40km/h (25mph) does not trigger an audible warning
3. Approaching at 45km/h (28mph) does trigger an audible warning

I don't think this is a bug. It's just poorly displayed and documented.

In the U.S., where we use Miles and MPH, if the speed limit is 35 MPH and I set the camera to 35 (ignoring the km/h), it will give the warning if I approach at 36 MPH or higher.

You should do likewise if all of your speeds are posted in MPH.

In countries where km/h is used, if the speed limit is 100 km/h, set it to 100, and since the users all have their clients set to km/h, it should give the warning if they're going 101 km/h.

[Dave2084]

I don't think this is a bug. It's just poorly displayed and documented.

The actual speed should be the same no matter what units are selected, it plain and simple maths.

I'm pretty sure that in the past Waze have told us (in the UK) that we SHOULD be using km/h in WME even though we use miles. I'll try and find the reference.

[Timbones]

You should do likewise if all of your speeds are posted in MPH.

This is only valid if all users in the UK use mile units - there's bound to be some that prefer metric. Just sayin'

[AlanOfTheBerg]

Destination bar and Main menu Mute buttons are not 100% synced. It is very easy to have the main menu show muted while Destination bar does not. These should be totally sync'd so that tapping one immediately changes the state and display of the other.

[AlanOfTheBerg]

This could be a routing server error or something wrong with the app. Unsure, but it happened several times on Friday 11/2. Logs were uploaded at some point. Unsure if this was a beta or 3.5.

There is no way that going .4 miles will take 43 minutes. .4 miles may have been to the next turn perhaps...

[sketch]

This could be a routing server error or something wrong with the app. Unsure, but it happened several times on Friday 11/2. Logs were uploaded at some point. Unsure if this was a beta or 3.5.

There is no way that going .4 miles will take 43 minutes. .4 miles may have been to the next turn perhaps...

I know I got this at least a few times over the last few weeks. I don't pay super close attention to that dialog, but I think most of them were in the 3.4.99.x betas.

[jasonh300]

You should do likewise if all of your speeds are posted in MPH.

This is only valid if all users in the UK use mile units - there's bound to be some that prefer metric. Just sayin'

If the laws set the speed limits in MPH and the signs show MPH, then they should have their unit set to MPH.

I don't disagree with you that it should do the conversion and work either way, but it doesn't.