Describe the problem*:
UK postcodes aren’t being read correctly. For example, I was travelling to “AL1 1SE” and TTS (UK Kate) read “… destination Al One, One South East” (“Al” as in short for “Albert”).
Even though there is some co-ordination with the first part of the postcode, convention is to always read it in full - “W12 8QT” would be “Double You Twelve, Eight Queue Tea” rather than “West Twelve, …” even though it’s in West London.
What device were you using?:
beta-mobile-app
What is the bug affecting?:
Sound (Prompts, TTS, Voices)
When did you send the logs? Date and time:
2025-07-23T17:33
Can you reproduce it?:
Always Happens
Did you send logs for this bug?:
Yes
Operating system:
beta-ios
Device Information*:
iPhone 16 Pro
Waze Version Number*:
5.9.5.1
How badly did this affect use of the product?:
Low
Thanks for your feedback. This isn’t actually a map bug, but an issue with the Text-to-speech changes that the UK volunteer community is in charge of. I’m moving this to the UK editors category so it can be visible there.
I’ve made a slight change to SE SW NW NE strings, which should fix the issue of them being read out as cardinal directions when next to other characters (such as within a postcode). I’m waiting for Waze HQ to apply the changes, and then I’ll do some further testing.
Apologies, I left this in the wrong place!
You’ve raised another bug in the app bug reports, but I said it wasn’t an app bug and was attempting to fix it. Why have you raised another report there?
That’s where I meant to raise it in the first place - you said it wasn’t a map bug, sorry, I misunderstood. I’ll try and delete the other.
I’m running v5.10.90.900 and it’s still not reading the postcode correctly, but it is different - it currently reads “AL1 1SE” as “Al One On Shay”.