joeclassic wrote:Enabled debug mode and reproduced the issue twice followed by uploading of logs to WAZE.
tmigar wrote:Exit Waze using home button.
sivigamer wrote:AlanOfTheBerg wrote:tmigar wrote:Exit Waze using home button.
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.
HarveyMRichards wrote:I think sivigamer is saying that the normal iOS way to fully exit an app is to double click the home button, which brings up the recent apps, hold down an app and when the app jiggles, click on the upper left (-) button.
So, when I use the switch off button within the Waze menu, does Waze cease to operate even though it's still active in the recent apps list?
HarveyMRichards wrote:I have found that my GPS apps, Navigon, Motion X, and Trail Maps to name a few, will continue to run while still in the mutli-task list. In fact they will run my battery down very quickly. Therefore, I try to make sure I remove them from the multi-task list.
HarveyMRichards wrote:Will Waze run in the background?
rcenteno_davis wrote:Now I haven't written any iOS app before (and this is directed at the app developers) but is there a way to detect the difference between a true app crash vs. the removal-by-icon-dance?
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)
See error: "Uh-Oh we seem to have encountered a bug..."
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).
Users browsing this forum: Bing [Bot]