Fitness App Shuts Down During Run

Hey guys, how can you go back to software version 1.02?

It seems that with this version, the problem is solved !!

I have the same problem and turned off the voice. It works. Is there any other solution? #nikepluswillnotwork

Per il momento non ci sono soluzioni. Apple e Nike non si preoccupano del problema. Forse tornare al software precedente 1.02, il problema è risolto. Forse!

Sure, use Ipod 7 without the use of voice seems superfluous

I have this same issue as well, with the same settings appearing to be the trigger. Will test turning off voice feedback and setting a longer than intended run.

Unbelievably frustrating that the BASIC tracking and reporting functionality can be completely lost by using the product as intended and there's been no fix for more than 6 months???

November 2014 and still no fix?

I am from Brazil and also having this issue.

Still no fix, but I can confirm that setting a longer run than you intend to go on stops the shutdown. It's getting near the end of the session that seems to activate the bug for me. I just set it for double the length I intend and stop when it reaches the halfway point. That way you still get the audio feedback to know when to finish.

I'm experiencing the same problem... i'll turn off the voice (as u guys recommended) and try again tomorrow...

My wife went for a run today with her new iPod Nano 7th generation and came back home so discouraged after her run was wiped out. After reading the forums and a quick Google search, I can't believe this problem has been going on for a while, possibly multiple generations and neither Apple nor Nike has done anything about it. Turn off the voice commands? Come on. That's one of the best features of the Fitness app to give you updates. Simply unacceptable Apple! I'm really disappointed.

Hey, everyone:

ISSUE:

I had the same problem. I had 100% consistent crashing in the Fitness app (replicated about 10 times) right at the “one minute remaining” milestone with voice (male or female) enabled, and set to 6 or 7 minute timed runs.

For me, this is the number one reason to own an iPod, so getting the fitness app working was critical.

POTENTIAL FIX:

This fixed the crashing on my device:

If you shift+click restore (PC here), iTunes lets you load an older firmware…

https://discussions.apple.com/thread/3893023

…which you can get here. (This 1.0.2 is running fine on my iPod nano gen 7):

http://forums.ilounge.com/ipod-nano/276450-ipod-nano-7th-generation-firmware-lin k.html

The one minute remaining milestone repeats twice in 1.0.2, but the app doesn’t crash for me. Seems to be some error in how they’re handling the milestone announcements? Can’t believe they haven’t fixed this yet, either.

**edited incorrect firmware link

Utter frustration. Two month old Nano 7th gen has been resetting itself sporadically on me. Put it down, pick it up a day later and it starts from the power on screen. Today it decided to reset itself right at the tail end of my best run ever. Called Nike+ who pointed the finger at Apple. Called Apple and was led by the hand to the unhelpful slippery slope of software restores and "well let's see if it happens again". Dude...here's a discussion thread that shows it's been happening for over a year. How about asking for the crash logs and forwarding them to someone educated enough to actually troubleshoot the problem? Nope, that's not in the script.

With the script they've been given to follow on the phone Apple help appears unable to comprehend or react intelligently to the idea that this device is not working as intended and "let's try this and see if you still lose data randomly on your next important run" is not an appropriate response.

I am in the same boat. I just came from a great run and lost it about 100 meters out. To me, 1/2 the point is the voice and the other 1/2 the record. I am actually on the phone now, let's see what happens...

Yep, she's saying to turn off the spoken feature. I explained all about all of the complaints, that it really needs to be addressed, etc. She'd putting it into an "emerging issue" - I would suggest calling them to get this moved up in priority. I'm looking at returning this one and using the $ to fix my 6th generation which I used for years with no issues at all (till its button got stuck).

heh. "emerging"...on what like a geological or evolutionary time scale? Tell her this is over a year old and in tech that isn't "emerging", it's "ancient".

Hi all,

My girlfriend and I have both an Ipod Nano 7th gen. She's mentioned that her Ipod stopped while at the end of her runs. So I started looking and found this very interesting forum (read all 6 pages).

Mine never experienced the restart, but If I looked at my run, they are all multiple of 5.

My settings are : English_US, Male.

Her settings are : French, Female.

She tried a 6 min run and it failed.

Now she's trying a 6 min no voice feedback.

I'll do a test on my own for 6 minutes.

Keep you posted.

Hi all,

I tried up edit my last post, was not working !?!?

Her settings are : French, Female.

She tried a 6 min run and it failed.

(edited) She's now trying the Male voice : (did not worked)

Now she's trying a 6 min no voice feedback.(edited: worked fine)

I'll do a test on my own for 6 minutes. (do this @ work, walk around for 5 min on your floor )

Did the 6 min test with the Male, it restarted !!

Here is my advice if your want to keep the voice feedback, for 32 minutes run, put 35 and stop it at 3 min remaining.

Male or female work only for multiple of 5 minutes workouts. For distance, I'll be cautious about a 1/2 marathon using the KM. It always will restarted on the 100m mark because it reaches 21KM.

Thanks all of you for your comments.

Just an update to add that this is an ongoing issue - I just bought a new iPod nano, primarily for music while I run, and it regularly cuts out and doesn't record my runs. Like one of the posters above, I've found that it tends to do so more during unusually timed runs (22 mins rather than 25 mins), but also if I tap it for updates lots. Will try the firmware workaround, but it's disgraceful that Apple haven't sorted this yet!