I have had the same on both a S4 and now again on a S5. It was OK and now stopped working again! 🥹🤷♂️Mine was working properly and now it isn't (10.1.1). I can only get the current heart rate; I cannot scroll to the resting heart rate and other functions as of a couple of days ago. This on top of not remembering where I last was on the app view. It's to the point that these Black Friday deals on Garmin are looking very, very attractive. I don't really want to deal with a device that's time consuming and tedious to use, and my user experience with my Ultra, which started out quite well, has been in steady decline since Watch OS 10 came out.
This unfortunately seems to have been a design choice to return to the top each time.This on top of not remembering where I last was on the app view.
I’m also quite frustrated with the bugs. This is a much worse experience than when I originally received my series 8.I'm having all these same problems on watchOS 10.2.
I wish I hadn't updated to watchOS 10! I didn't intend to. I updated my iPhone to iOS 17 (which really offered me no benefit, I shouldn't have done that either), but that iOS update forced the Apple Watch update, and the Apple Watch is now uglier and the main thing I use it for (heart rate) is not updating and I really don't trust the readings.
How can this be a bug so many months after you all in this thread originally reported it? I guess I shouldn't ask becuase I know how . . .
Mine broke the same way after a day’s time like previously.Well, the update to OS 10.2 has finally restored my S5 watch Heart Rate bpm screens. They are working again for now anyway! I still regret the update from OS 9 as I much preferred it before the stupid OS10 changes for no reason.
OK 👌 will do! Still working at 00:57 GMT TODAY 13 DEC…Mine broke the same way after a day’s time like previously.
Let us know if the fix seems persistent on your end after 2 days or so.
As promised, heart rate bpm still operating properly and consistently after Watch OS 10.2. 👀👍OK 👌 will do! Still working at 00:57 GMT TODAY 13 DEC…
Wow, you're lucky af. Mine is still broken on my Apple Watch Ultra 2. Reset the Watch on 10.2 to be sure, even after that it stopped working, and still is not working reliably on 10.3 beta 1.As promised, heart rate bpm still operating properly and consistently after Watch OS 10.2. 👀👍
think you missed his last update...Wow, you're lucky af. Mine is still broken on my Apple Watch Ultra 2. Reset the Watch on 10.2 to be sure, even after that it stopped working, and still is not working reliably on 10.3 beta 1.
That is actually because in previous releases the app did not get closed, it continued running in the background, whereas since WatchOS 10, that's not the case. It even gets cleared out of memory on my Apple Watch Ultra 2...My Apple Watch Series 7 as I mentioned above does not update the heart rate complication with watchOS 10.2, but now when I tap the icon to open the app to get the most recent reading it briefly shows a spinning circle, which I believe is the application launch animation. I have never seen that before for any app on Apple Watch since I got the Series 7. I'm assuming it's the normal animation and that I never saw it before because apps always opened fast enough to not show it. If I've just opened the app from the complication and then open it again, I don't see the animation, making me think it's loading faster because it's stored in memory. I remember when Series 9 came out people said it didn't need the faster processor it had because everything was already instant on Apple Watch, but it apparently no longer is.
Oh, interesting. Is that the reason (or a reason) it's not updating the complication in a timely manner?That is actually because in previous releases the app did not get closed, it continued running in the background, whereas since WatchOS 10, that's not the case. It even gets cleared out of memory on my Apple Watch Ultra 2...
That is my suspicion, seems a logical one as well. They tweaked the memory handling with the introduction of WatchOS 10 (I believe they said so in WWDC, also they removed app pinning), this is the most plausible explanation I've heard and found so far. Previously I always had critical apps pinned so they'd never get cleared out of memory, now they constantly do, regardless system or 3rd party.Oh, interesting. Is that the reason (or a reason) it's not updating the complication in a timely manner?