And while the dust around that was about to settle down, a new issue seems to have already made its way. This time around, various users have voiced their concern across Reddit that they are constantly getting bugged with the ‘AirPods Pro Detected’ notification on their iPhone as soon as it detects the said earphones nearby. What is even more intriguing is that you will get bombarded with these prompts irrespective of the fact whether you own these AirPods or not.
So if you are nearby a person who owns an AirPods Pro, and you don’t, then you will still have to greet yourself with those constant prompts on your device. Moreover, the notification also lists out that the Owner can see its location. So if you are not the owner and the actual owner has Airtags enabled as well, then it could prove to be major privacy. This is because you cannot simply disable the AirTags as you don’t have them in the first place.
Then for the set of people who own these AirPods Pro, these notifications wouldn’t be of any good to them as well. This is because they are already in possession of these AirPods and they don’t need a constant reminder of the same. So in every scenario, the best bet seems to be to turn off the ‘AirPods Pro Detected, An AirPod Pro has been moving with you for a while’ notification on your iPhone running iOS 15. And in this guide, we will show you how to do just that. Follow along.
How to Turn off AirPods Pro Detected Notifications in iPhone
The culprit behind this issue is the ‘Notify When Left Behind’ feature of the ‘Find My App’. When this feature is enabled, the iPhone will alert you as and when you leave an Apple device or item at an unknown location. So the best way of rectifying this issue, as you might have guessed, is to simply disable this feature. So without further ado, let’s check out the associated instruction steps. So with this, we conclude the guide on how you could turn off the ‘AirPods Pro Detected, An AirPod Pro has been moving with you for a while’ notification on your iPhone running iOS 15. While this might not qualify as the most viable approach to rectify this issue, but as of now, this does seem to be the only feasible approach. In this regard, if you know of any other workaround that worked out in your favor, then do let us know in the comments section below.