I am curious how common this issue is...
Since receiving my Apple Watch Ultra 2 (initially running watchOS 10.0, now 10.0.2), my watch will seemingly randomly respring/reboot throughout the day. The display shows the Apple logo, reboots, and then requests my password. Sometimes, I catch it in the act; other times, I am just prompted for my password. It's frustrating because I am not getting health tracking or activity credit while it's unlocked. I confirm my watch is tight against my wrist.
In reviewing my error logs (Privacy & Security -> Analytics & Improvements -> Analytics), I see a kernel panic log ("panic-full...") for each time this has happened. It's been two times each day this week and four times already today. I was inclined to see this as a hardware issue and seek a replacement watch during my two-week return period, but my partner's new AW9 has the same issue (though she's only experienced it twice). In every instance, we were working in front of our Macs, so perhaps there's a Continuity or Handoff bug or else in the software?
Has anyone else experienced this kernel panic / respring issue with watchOS 10? You may only notice your watch asking you for a password and assume that it was loose on your wrist and became unlocked. It's easy to miss the respring. Thanks!
Since receiving my Apple Watch Ultra 2 (initially running watchOS 10.0, now 10.0.2), my watch will seemingly randomly respring/reboot throughout the day. The display shows the Apple logo, reboots, and then requests my password. Sometimes, I catch it in the act; other times, I am just prompted for my password. It's frustrating because I am not getting health tracking or activity credit while it's unlocked. I confirm my watch is tight against my wrist.
In reviewing my error logs (Privacy & Security -> Analytics & Improvements -> Analytics), I see a kernel panic log ("panic-full...") for each time this has happened. It's been two times each day this week and four times already today. I was inclined to see this as a hardware issue and seek a replacement watch during my two-week return period, but my partner's new AW9 has the same issue (though she's only experienced it twice). In every instance, we were working in front of our Macs, so perhaps there's a Continuity or Handoff bug or else in the software?
Has anyone else experienced this kernel panic / respring issue with watchOS 10? You may only notice your watch asking you for a password and assume that it was loose on your wrist and became unlocked. It's easy to miss the respring. Thanks!
Last edited: