Activity GPS issues after watchOS 7 and iOS 14 updates

Maybe that's Apple's ploy to get us to sign up for a 'working' Fitness + and squeeze another Fistful of Dollars out of us .... if so it won't work.

I really peed off at Apple's attitude, I'm updating now to 14.1 so hopefully they've got their finger out and sorted THEIR BUG

I can confirm the update has not fixed the activity issues, the walk I just completed not showing at all in the app. It does however fix the issue with the wrong Watch type showing but only after a reboot of the watch, I now have a SS watch 6, hooray!!

I have my old iPhone 7 still running iOS 13 and it has most of the GPS data missing from my new phone. Is there any way to transfer the GPS data to my new phone without losing the workouts since updating to iOS 14?

Not thru apple health or fitness app. I say import those maps to strava and rungapp app so you have your history maps logged and saved. I was hoping apple was going to fix this and get us our gps maps back but i have my doubts now.

I'd advise anyone on 13.7 to stay there, 14.1 is no better than the BOS that was 14 and 14.0.1

GPS still not working, different readings in WATCH, HEALTH and the totally useless FITNESS for the SAME workout.

I'm sorry I ever updated to 14. Things were working perfectly in 13.7, now if I could go back I would.

Clearly this BUG is way way down at the bottom of Apple's list of priority. I will be most surprised if they sort it out before 14.5 so buckle up for the long ride.

This is the final straw for me re Apple, in future i'll look elsewhere for stuff that actually works at probably half the price.

So much for Apple's customer support, it's non existent. What a bummer, well we know what to do the next time upgrading our tech

STAY WELL AWAY FROM APPLE WHO JUST DON'T CARE IF THEIR SOFTWARE IS CRAP

Ah so that's Apple's plan, totally mess up the Activity app, replace it with a total Ball Of Sh1te and rename it just for fun and to rub their noses in it ...... now what will we call this BOS??? ......... ah, got it FITNESS

Then make it impossible for mugs sorry users to get their old workouts back unless they BUY A SHINY NEW PHONE and we'll fix the Fitness app, call it Fitness + and charge the suckers $29.99 per month for the 'Premium One' ....... sit back and watch the millions fly in ....

Sounds like a plan

After realising that iOS 14.1 did not fix it, and the suggested complete reinstallation will be our only chance, i decided to go through that procedure.

Last second I realised that the complete reset will also delete my eSIM activation, which I can only re-activate through a new letter in the mail from my provider.

Thanks apple for this huge mess. I am so done with apple products after this experience, congrats on loosing a long time customer! No acknowledgment of the issue or any help, what a letdown.

From previous replies I understand that (a) following the fix suggested by Apple (scratch iPhone + Watch + restore from iCloud) is not certain to fix the problem and (b) I need to pay Apple for sufficient iCloud space to back up my iPhone there in order to carry out that procedure. That's hilarious, isn't it ? And (c) a backup and restore from my Mac won't fix the problem (what is the difference ???). Last not least (d) it will take me hours if not a full day to perform (a) as I am not sitting on an extremely fast Internet connection.

I ask again - where is Apple QA (that is Quality Assurance), how much regression testing was done prior to releasing iOS 14 ? Obviously not enough. Why is there no fix yet ?

I am an Apple user since the early 1990s. Apple stuff used to be working well and reliable, and better than the competition. Well integrated, too. These times appears to have past.

Since almost 4800 people have marked the original post as "I have this question too", I would venture to say that many tens of thousands probably have this problem and don't even know where to look for a solution.

I still have a little hope that a future update might bring back the lost data.. My step counter in the health app still goes back six years, same for the heart rate of activities like biking and swimming.

However, the way apple treats this issue (as usual) does not fit AT ALL with their ambition for the watch to become a serious health/medical device. If you rely on the data e.g. as a diabetic, heart conditions or whatever, be aware!!

All my really old garmin data is save on the garmin connect web interface, i can easily download it and do my own backups. Impossible with apple health. And then this issue..

Support asked me to reset and re sync... data gone and no fix! This is absolutely ridiculous. Apple have broken this, given us a time consuming procedure that does not work and have plans for a resolution. Back to a proper watch... the Garmin Fenix watch can show GPS and record activities! https://buy.garmin.com/en-IE/GB/p/552982

Had problem ever since iOS 14 and watch is 7. This is a horrible shame and not worthy of Apple. Can’t get a straightforward answer anywhere; only anecdotal try this and try that. This is a tech issue not psychoanalysis. There should be a straight admission of the problem and a straightforward solution. Unpairing NO GPS ROUTES. Resetting phone NO GPS ROUTES. Bought new Apple Watch 6 NO GPS ROUTES. Bought new iPhone 12 STILL NO GPS ROUTE. .

.

.

c’mon man. Apple get your **** fruit together for your faithful users who have spent thousands of dollars and put our faith in you.

Same. I’ve lost literally everything. This is absolutely insane. Now I’m forced to use Strava but it doesn’t count as a workout in Health/Activity. Been like this for months now. When is a fix coming?

After many tests, run and walk I have noticed that the VO2 data’s are not properly recorded when I use a HRM chest belt such as Garmin or Suunto.

However, when I record a workout (walk, or run) with the Workout App only wearing my AW and therefore the wrist HRM, the VO2 is properly recorded.

It is such a shame because before iOS 14 update and watch os 7 update it used to work perfectly even with third part HRM.

I have already written to Apple Feedback to report this bug.

Does anyone else here have noticed the same ?