Defect with iOS7.0.x?
Posted: Mon Sep 30, 2013 3:06 pm
I'm not sure if I've started doing something weird or found a problem.
Problem: GetRunning App never prompts to start running (appears to have stopped running).
Environment:
iPhone 5 iOS 7.0.2
Running Apps: Dataman Version 8.0, RunKeeper V4.0.1, (runkeeper starts playlist music), GetRunning 1.10.0
Polar HR7 Bluetooth heart rate sensor
Reproduce:
1) Open RunKeeper, Press Home button, Open GetRunning,
2) Press Home Button, then select Runkeeper, Press "Go Running", Music starts
3) Press Home Button, then select GetRunning, Press "Run Week x (W5R3 and W6R1)"
4) Hear "Begin your warm up...Today we will run ...
5) Press "turn off display button" and put phone in pouch
6) After walking for a long time, realize that Claire should have told me to start running
7) Press "power/display" button, unlock phone, GetRunning is not running, press GetRunning, fast forward till around 50 seconds left in warmup
8) Everything works as expected for the rest of the run.
This behavior has only started in the last three days about the time of the iOS7.0.1 upgrade? Worked fine exactly with this procedure for the prior month.
Problem: GetRunning App never prompts to start running (appears to have stopped running).
Environment:
iPhone 5 iOS 7.0.2
Running Apps: Dataman Version 8.0, RunKeeper V4.0.1, (runkeeper starts playlist music), GetRunning 1.10.0
Polar HR7 Bluetooth heart rate sensor
Reproduce:
1) Open RunKeeper, Press Home button, Open GetRunning,
2) Press Home Button, then select Runkeeper, Press "Go Running", Music starts
3) Press Home Button, then select GetRunning, Press "Run Week x (W5R3 and W6R1)"
4) Hear "Begin your warm up...Today we will run ...
5) Press "turn off display button" and put phone in pouch
6) After walking for a long time, realize that Claire should have told me to start running
7) Press "power/display" button, unlock phone, GetRunning is not running, press GetRunning, fast forward till around 50 seconds left in warmup
8) Everything works as expected for the rest of the run.
This behavior has only started in the last three days about the time of the iOS7.0.1 upgrade? Worked fine exactly with this procedure for the prior month.