No. I just had to send my watch in to be re-flashed, since I tried to pair it to my replacement phone, and it still wanted to be unlocked by the old phone to which it was no longer paired.
Thanks for replying! Did they give you a turnaround time estimate? I had to have my iPhone 6+ replaced on Sunday and every since then it's been nothing but problems with my watch. It can't all be beta related.
No. I just had to send my watch in to be re-flashed, since I tried to pair it to my replacement phone, and it still wanted to be unlocked by the old phone to which it was no longer paired.
I did unpair the Watch from the old iPhone. I think the issue might have been that the backup on the new iPhone (which transferred over from the backup of the old iPhone that I restored to the new one) might have "tricked" the Watch into looking for the old iPhone. I didn't notice it until a few hours later (after I had already erased the old iPhone). At that point it was "paired" to the new iPhone, got notifications, etc. and was working fine until I took it off. When I put it back on, I noticed that it wouldn't unlock.I assume this bug could have been avoided if you had unpaired the Watch from the old iPhone before getting the replacement? Or did it not reset after unpairing?