Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

joema2

macrumors 68000
Original poster
Sep 3, 2013
1,646
866
This has been discussed before but this is a thread to summarize the problem: If you backup your previous watch via unpairing, and if the new watch is on an earlier version of WatchOS, upon pairing to the new watch it will not show the recent backups. There is no guidance in the on-screen dialog such as "incompatible backup detected, only showing old ones". I don't see an Apple KB article discussing this. There are various Apple and 3rd-party articles that simply state "unpair to backup, re-pair with new watch and restore backup". Examples:


It is as if nobody writing all that info considered the possibility a brand new watch might be on an older version of WatchOS and backup/restore between old/new watches might not be possible. Worse yet, it doesn't simply fail but only shows older backups. A person not paying attention could easily restore an old backup to their new watch.

I think the required workaround is first unpair from the old watch, pair to new watch, do not attempt to load backup, upgrade the new watch to the latest WatchOS, unpair from that, re-pair to new watch, load recent backup. If that doesn't work, re-pair to old watch, unpair to make yet another backup, then re-pair to new watch and try to load recent backup. However to my knowledge this isn't well documented and even first and second level Apple support techs are not always aware of it.

Of course if you are an experienced Mac user you may know from experience there can be backup/restore limitations between major software versions like a Final Cut Pro library. But many watch/iPhone users are not thinking in terms of databases and WatchOS versions -- they simply expected the *documented* procedure to work.

It would be an improvement if this was better documented, but the product itself should ideally be designed to avoid this. E.g, when it detects you are trying to pair with a new watch having a backlevel WatchOS vs the most recent backup, it should prompt you and do the WatchOS upgrade -- or something like that.
 
  • Like
Reactions: getrealbro
If I use Nike Watchfaces, the backup will not show up, when setting up my new non nike edition (titanium). If I remove the Nike watchfaces, I can restore from latest setup, even without doing an unpair of my Nike AW.
 
Ugh. I just moved to a replacement phone and the backup option was not there. Very frustrating. It certainly appears to be only patly implemented.
 
. E.g, when it detects you are trying to pair with a new watch having a backlevel WatchOS vs the most recent backup, it should prompt you and do the WatchOS upgrade -- or something like that.
When I recently set up a new S7 watch it told me it needed a software update out of the box and did it as part of the pairing process, so it would appear this has been addressed.
Ugh. I just moved to a replacement phone and the backup option was not there. Very frustrating. It certainly appears to be only patly implemented.
You can move a watch from one phone to another without unpairing it as long as you have the old phone: IIRC if you use Quick Start to do the transfer it will ask you if you want to use the watch with the new phone during setup. If you don’t have the old phone you do need to unpair / repair it, unfortunately.
 
When I recently set up a new S7 watch it told me it needed a software update out of the box and did it as part of the pairing process, so it would appear this has been addressed.

You can move a watch from one phone to another without unpairing it as long as you have the old phone: IIRC if you use Quick Start to do the transfer it will ask you if you want to use the watch with the new phone during setup. If you don’t have the old phone you do need to unpair / repair it, unfortunately.


Thanks. I’m sure that’s how it’s supposed to work :D
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.