Facebook Messenger for Apple Watch is a really convenient way for many people to use their real-time chatting app on the go, especially doing it right on their wrists.
Since the initial release back in October, I personally didn’t have any trouble using the Messenger app on my watch at all. Until recently the app started freezing or sometimes just stop working completely.
There are two things I can say right now:
- This is definitely a bug
- I’ve seen many people suffering from it
I hope this post is going to help you temporarily address the issue until there is an official update to the Facebook Messenger application. This quick fix will allow you to resolve the problem without having to restore your iPhone or your Watch to its factory settings.
Fixing the Messenger app on Apple Watch
- From your iPhone, go to the Messenger app
- Access the Settings page and go to Apple Watch
- Change the default replies to anything you want and get out of the settings page.
- Now go back to Settings > Apple Watch and delete the entry that you changed
- Again, return to Settings and close the Messenger app
- Open the Facebook Messenger on your Apple Watch and you should see that all messages are now fully loaded
What a weird trick isn’t it; I’m unable to figure out how this help to fix the problem, but it did. It’s worth noting that most issues on your watch are fixable without having to do any serious work.
If Facebook Messenger is still not loading on your Apple Watch, try the following tips:
Update both iOS and watchOS
If the above solution doesn’t work out for you, that means something is wrong with the software. Therefore, updating both your iPhone and Apple Watch to the latest firmware can potentially resolve the issue.
- iPhone must first be running the latest iOS version (iOS 10 as of writing this)
To update your iPhone, go to Settings > General > Software Update. Perform the same steps with your watch by going to the Watch app on your iPhone.
Once your watch is updated to the latest version, go back to Facebook Messenger to see if it’s working. We do believe that getting the most recent version will possibly fix this problem.