Waze forum

tmigar wrote:I am able to replicate the bug every time by doing the following:

Exit Waze using home button.
Clear Waze from memory (by double clicking home button, holding down Waze and then deleting)
Restart Waze.
See error: "Uh-Oh we seem to have encountered a bug..."

Waze v3.5.1
iPhone 5
OS v6.0.1

I delete Waze from memory to avoid being tracked at home, at work, etc.

The issue persists even after doing a clean install of the app (deleting, hard-reset phone, reinstall).

AlanOfTheBerg wrote:

sivigamer wrote:

AlanOfTheBerg wrote: Like gerben said, use the actual correct way to Exit Waze which is the Switch Off button in the main menu. Otherwise, Waze just runs in the background and then you force-kill it. Not the right way to do it at all.

Using an in app menu is not the normal way to exit an iOS app or any mobile app for that matter. It shouldn't give errors for quitting.

Waze is not a "normal" iOS app and therefore requires something different for proper exit. Apple Maps doesn't quit when I background it either if it's navigation mode. Are you calling that not "normal" as well? There are certain apps which have flags to work in the background, such as VoIP and navigation apps. Many of them do not exit when hitting the home button. That is just the way these kinds of apps are designed to work. Users need to know this to understand how to properly use the apps.

AlanOfTheBerg wrote: Apps in the multi-task list are not necessarily running. All apps recently used, running or not, are listed there. Waze happens to keep running when the home button is tapped. Most applications are not written this way and cease operation and receive no CPU time nor memory allocation once they exit. The applications in the multitask list are, by and large, not using CPU or memory.

When you exit Waze using the "Switch off" button in the main menu or use one of the various voice commands to accomplish the same, it properly exits and is allowed to finish upload of any pending drive data before terminating.

Search the 'net and you'll find many articles about people's misunderstanding of this list.

AlanOfTheBerg wrote: I am curious how one proves they are running, exactly? I would love to be able to find that out. Anecdotal info is one thing, but something which could show CPU time would be excellent. I have had no issues with Waze when shut down the correct way, FYI. The GPS icon stays on for 10-15 seconds, but I think that's an iOS lag.