Still encountering bug upon APP initialization w/latest rel

These forums are specific to the Waze mobile app. Post here if you experienced a problem while using the app, have a question about the app functionality or a feature such as navigation or search.

Moderators: krankyd, Unholy

Re: Still encountering bug upon APP initialization w/latest

Postby HarveyMRichards » Thu Jan 10, 2013 5:36 pm

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.


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
 
Posts: 6
Joined: Wed Nov 16, 2011 12:24 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby HarveyMRichards » Thu Jan 10, 2013 8:54 pm

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.


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
 
Posts: 6
Joined: Wed Nov 16, 2011 12:24 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby HarveyMRichards » Thu Jan 10, 2013 11:48 pm

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.


I have an app, System Max, https://itunes.apple.com/us/app/system-monitor-battery-max/id386118145?mt=8 that is supposed to show running processes. I'm not sure what processes would be associated with Waze.

Will Waze run in the background?
HarveyMRichards
 
Posts: 6
Joined: Wed Nov 16, 2011 12:24 pm
Has thanked: 0 time
Been thanked: 0 time

Still encountering bug upon APP initialization w/latest rel

Postby joeclassic » Wed Nov 14, 2012 5:51 pm

Still encountering bug upon APP initialization w/latest 3.5.1.0 build.

This issue was previously reported: viewtopic.php?f=3&t=30575&p=285992&hilit=horrifically#p285992

And is still prevailing. Logs have been sent to WAZE team for analysis.
joeclassic
 
Posts: 7
Joined: Sun May 13, 2012 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby joeclassic » Thu Nov 15, 2012 7:51 pm

Thanks YoYoPro15 but I dont have a FaceBook account.

I'll try the recommendation to uninstall, reboot device, and reinstall the APP.

I'll update this post with my findings.
joeclassic
 
Posts: 7
Joined: Sun May 13, 2012 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby joeclassic » Thu Nov 15, 2012 8:04 pm

Roger that AlanOfTheBerg ...

Post reinstall of the APP I still got the "Uh-oh! We seem to have encountered a bug. Help us improve by sending us an error report". Post receipt of the error, I did opt to upload the logs.

I will reproduce via the debug mode and send up logs again.
joeclassic
 
Posts: 7
Joined: Sun May 13, 2012 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby joeclassic » Thu Nov 15, 2012 8:15 pm

AlanOfTheBerg ...

Enabled debug mode and reproduced the issue twice followed by uploading of logs to WAZE.

Opened a ticket and provided required information.

Here is a snippet from that ticket:

iOS 5.1.1(9B206)

Encountering the following every time upon APP initialization "Uh-oh! We seem to have encountered a bug. Help us improve by sending us an error report."

WAZE team request I enable debug mode and send those up along with opening a ticket specifying log upload times.

Enabled debug mode and uploaded logs at the following times: 12:07 PMPST and 12:09 PMPST.

Hope this helps.
joeclassic
 
Posts: 7
Joined: Sun May 13, 2012 2:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Still encountering bug upon APP initialization w/latest

Postby rcenteno_davis » Fri Jan 11, 2013 4:47 pm

I'd like to chime in that Waze is the only app I've seen that has an in-app menu item for "shutting" down. I usually remove apps from the running list by making the icon dance and X-ing it our from the taskbar.

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?
Area Manager: Union City, Fremont, Newark CA
Image
rcenteno_davis
 
Posts: 30
Joined: Sun Jul 22, 2012 2:53 pm
Has thanked: 0 time
Been thanked: 1 time

Re: Still encountering bug upon APP initialization w/latest

Postby rcenteno_davis » Fri Jan 11, 2013 5:02 pm

Alan, me = old dog, menu item = new tricks.
Area Manager: Union City, Fremont, Newark CA
Image
rcenteno_davis
 
Posts: 30
Joined: Sun Jul 22, 2012 2:53 pm
Has thanked: 0 time
Been thanked: 1 time

Re: Still encountering bug upon APP initialization w/latest

Postby sivigamer » Thu Jan 10, 2013 5:02 pm

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.
sivigamer
 
Posts: 1
Joined: Mon Oct 15, 2012 11:56 pm
Has thanked: 0 time
Been thanked: 0 time

PreviousNext

Return to Waze App

Who is online

Users browsing this forum: Google [Bot], Google Feedfetcher