Galaxy Watch 4 Manager fix (works on 5, too)

[notforhire]

While we're waiting for the developers and/or Google to provide the software fix that will allow us to use our Galaxy watches in the manner for which they were created, I've found a way to halt the constant notifications about the plug-in having stopped working.

Turn your watch off. Take it off your arm. Set it on your desk (or any other place you find appropriate).

The notifications stop. Problem solved. Start working it "old school", and look at your phone often to see if there are any important notifications you might have missed. 😉

[userXl9JyuKNTb]

Don't restart your phone. The notifications will come back.

[Linusss]

What a useless post lol

[Moosc]

No issues on my 5pro and beta on s22ultra. Updated wearable app no issues. My biggest pet peeve with Samsung is bedtime mode back

[TechyGuy]

This sucks. I cannot use my watch. I have reset my watch 5 times now and it just comes back

[notforhire]

I was out of state when it started for me. Was planning on coming home and uninstalling the Wear app, reset my watch, etc. Then I saw how, ultimately, those steps hadn't worked for others, so I saved myself the aggravation.

[USBetaModerator2]

Hello,

Thank you for your feedback.  This is a known issue and we are working to provide a fix soon.

If you haven’t already, Please update Samsung Members app to latest version from the Galaxy store and send us an error report immediately after experiencing the issue from the Samsung member’s app -> Beta Feedback -> Error Reports to help us debug the issue.
We apologize for the inconvenience and appreciate your contribution to the beta program.

Regards,
One UI Beta Team

[Compusmurf]

Haven't had this issue even once. Maybe something you have installed?

[notforhire]

"this is a known issue and we are working to provide a fix soon"

[user7jvnYvLQLd]

Same, I haven't experienced this luckily. I have Galaxy Watch 4 Classic

[usersibEEM9oVD]

In my testing I found that this is related to the eSim.  Rebooting or disabling and reenabling the eSim causes this issue.  They need to fix this bug as soon as possible.  It's pathetic that they haven't figured this out yet.