Apple Watch crown not picking up heart rate ecg - Issues with ECG and Heart Rate Detection After Updating to WatchOS 10.3.1

This is a useless post! Why did you even respond?? It in NO WAY addresses the issue! No one asked about the features of the watch! STOP making useless posts just to get your post count up so Apple will promote your status.

My model MNU73LL/A, running latest 10.4 update, is suddenly having similar crown-related issues with the ECG app: 9 out of 10 times it either a) won’t start, seems unaware of stem pressure, or b) counts down to 28 or so and restarts. The one time I got a complete count down to 0, I was told I was in afib, which I don’t think was correct.***

Similarly, the Heart Rate app is functioning well, but I have noticed ever since the last update that a stem double press only momentarily displays the proper array of recent apps and instead pops to one arbitrarily, unless I immediately start scrolling.

Since I sleep with my watch on and my HomePod playing a long recording, I’ve also found brushing my arm against the sheets now somehow scrolls the volume down to nothing.

***I tried charging up my old watch, and there the ECG apps seems fine (no afib either), as does being able to scroll with the stem through recent apps.

So what’s going on here—hardware and or software issues? And Community Specialists, please don’t post useless cut and pastes like the one below. And yes, I’ve restarted, etc.

Thanks for asking about these features on Apple Watch.

Make sure you're on the latest version of iOS and watchOS supported by your devices.

Check here to see if a feature is available in your region.

Here are some additional resources you might find helpful:

Heart health notifications on your Apple Watch

Take an ECG with the ECG app on Apple Watch

Track your AFib History with Apple Watch

If you have any other questions, please contact our team here.

If you believe that you're experiencing a medical emergency, please contact your local emergency services.

Same thing with my watch and iphone 12. The only response I can find out of all the different ways to ask this same question, is the same useless response like the one from the "community specialist", even when people state all of the ways they have attempted to resolve the problem are the same as what the "community specialist" posts. APPLE just come out and say that you have a bug, you know about it and are working to resolve it.