Home > Apple > iPhone

Ping My Watch not working from iPhone Control Center [Fixed]

In this guide, we will show you a nifty workaround that will help you fix the issue of the Ping My Watch feature not working from the iPhone’s Control Center. One of the biggest perks of owning a device from the Cupertino giant is its close integration with other Apple devices in a well-enclosed ecosystem. Making full use of the same is a feature known as Ping My Watch.

As is evident from its name, this feature will make your Apple Watch play a sound when it’s nearby so that you can easily find it. The only requirement is that your iPhone and Watch would be on the same WiFi network. As far as accessing it is concerned, you can either do so directly from the Control Center, via the Find My app, or from iCloud. Out of all these three, the Control Panel.

However, as of late, the latter option is giving a tough time to many. Numerous users have voiced their concern that the Ping My Watch feature is not working via the iPhone’s Control Center as the said feature is greyed out and says unavailable. Restarting the device and/or toggling WiFi and Bluetooth didn’t do any good either. If you are also getting bugged by this issue and are unable to find a way out, then this guide is here to help you out. Follow along for the fix.

Fix Ping My Watch not working from the iPhone Control Center

To rectify this issue, you need to toggle the Access Within App feature, delete, and then re-add the Ping My Watch from the Control Center. Here’s how all of this could be carried out:

Ping My Watch not working from iPhone Control Center

  1. Head over to Settings > Control Center > Turn off “Access Within App”.
  2. Then turn it back on. Now go to Control Center and delete Ping My Watch.
  3. Then restart your device and re-add Ping My Watch to the Control Center.

That’s it. These were the steps to fix the issue of the Ping My Watch feature not working from the iPhone’s Control Center. As far as the official stance on this matter is concerned, the developers are aware of this issue, but they haven’t given out any ETA for the rollout of a fix. As and when that happens, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.


Share: