Hi everyone,
Has anyone else noticed a serious navigation issue with WeWALK on iOS recently?
Until late August 2026, everything worked perfectly. Whenever I was unsure which direction to take, I could simply stop walking and rotate my iPhone. WeWALK would immediately update the clock-face direction to my next navigation point, announcing something like “at 12 o’clock,” “at 3 o’clock,” etc.
However, since early October, this functionality has stopped working correctly.
Now, when I stop and rotate my phone, the direction to the next navigation point doesn’t update at all. The app just announces “Head” followed by a street name. I have to physically walk another 10–20 metres before it finally updates the direction.
This is extremely frustrating and potentially unsafe, especially when navigating unfamiliar streets. As a blind pedestrian, I need to know which direction to take before I start walking, not after I’ve already walked several metres in a potentially wrong direction.
Here’s what makes this particularly interesting:
* The direction indicator pointing towards my final destination still responds immediately when I rotate my iPhone.
* Apple’s built-in Compass app works perfectly.
* I tested the same functionality on Android, and it works exactly as it should! The direction to the next navigation point updates when rotating the phone, even while standing still.
* The problem therefore appears to be specific to the iOS version of WeWALK, although I can’t rule out an issue affecting particular iPhone models or iOS versions.
My setup:
* iPhone 17 Pro Max
* iOS 27.2
* WeWALK 4.2.1
I’ve already contacted WeWALK support and provided a detailed description of the issue.
I travel internationally quite frequently and have relied heavily on WeWALK for independent navigation. Unfortunately, this regression has made the iOS app practically unusable for me.
Has anyone else experienced this behaviour on iOS? And if you’re using an older iPhone or a different iOS version, does the compass-based guidance to the next navigation point still work correctly?
I’d really appreciate hearing about your experiences. I’m hoping we can figure out whether this is a widespread iOS bug and get WeWALK to investigate it.