Your Pixel Watch broke two of the most important features Google has openly advertised, including ECG and Find My Phone. Google has been doing this for years already. They release an update that breaks something, and then they break another feature when they release another update to fix the first issue.
A bug has surfaced on Pixel Watch 3 and Pixel Watch 4 that is causing both the Find My Phone and ECG apps to crash completely, leaving both functions totally unusable for a growing number of users. Two distinct features are broken at the same time on a watch that costs hundreds of dollars.
The Find My Phone bug triggers the splash screen, then immediately crashes and throws you back to the watch face. Multiple users confirmed the same experience on a PixelWatch subreddit, which shows it is a widespread issue.
The temporary solution for the Find My Phone bug is simple: if you ask Google on your watch to find your phone, it’ll ring your phone. That’s how easy it really is. Though your watch needs to be paired with your phone for this to work.
On the other hand, the ECG situation bothers the users more, though, and here’s why.
The ECG app lets you check your heart for signs of atrial fibrillation, an irregular heart rhythm. This isn’t a party trick feature. People with heart conditions actually rely on this.
When you open it, the app launches, then immediately crashes with an error that reads “Reopen the app and try again.” Reopening it gives you the same error. You will be stuck in a loop with no exit.
The last major Pixel Watch software update was in March 2026, but these issues only surfaced in the past few days, especially after the shift to Find Hub, pointing to a server-side change or a background app update as the likely culprit rather than the OS itself that broke the feature.
I love what Google is building with the Pixel Watch. The hardware has come a long way, but this is the kind of thing that makes people lose trust in the brand. When your smartwatch’s health features stop working, and there is no official workaround, this shows something has gone seriously wrong with the QA process.
Fix it fast, Google. Your users are waiting.
