Every time I open my AirPods Pro 2 case I receive a message saying "Not Your AirPods Pro" on my iPhone even though the Air Pods connect in the background. I have done "forget device" and factory reset AirPods Pro 2 a couple times and re-paired them and it still happens. Super annoying - anyone else have this issue?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
AirPods Pro 2 issue - "Not your AirPods Pro"
- Thread starter bscheffel
- Start date
- Sort by reaction score
I think what you are seeing is the result of the AirPods being associated with someone else's Apple ID and FindMy. Do you know if they were connected to someone else's phone/account before you got them?
Did you guys find any solution? I have a kind of this problem too. I gave my airpods pro gen.1 to a friend and forgot to delete them from "find my". So I did this a bit later, the AirPods aren't in my "find my" anymore.
My friend still gets a notification like "the owner can see your location", while they are showed in his "find my".
My friend still gets a notification like "the owner can see your location", while they are showed in his "find my".
Same here for my AirPods 3, AirPods Pro 2, and AirPods Max as I removed them from my old Apple ID and added them to my new Apple ID I recently set up.
They all work and show up in my FindMy app of the new Apple ID but if I remove them and try reading them to ANY Apple ID I get the same message.
I was planning on selling my old AirPods 3 and realize the buyer might think they're stolen or still linked to my Apple ID – which it is not.
Anyone else has the same issue or a solution?
They all work and show up in my FindMy app of the new Apple ID but if I remove them and try reading them to ANY Apple ID I get the same message.
I was planning on selling my old AirPods 3 and realize the buyer might think they're stolen or still linked to my Apple ID – which it is not.
Anyone else has the same issue or a solution?
Mine are all from the Apple Store and genuine products no doubt. Apparently it's been happening to many people as I read here and on places like Reddit. Sounds like a software thing.
Either way, after setting them up with a new device they work fine and show up on FindMy – At least for me
Than I’m sorry, it should be a bug in their recognizing module which they launched recently. Who knows what algorithm did they implement there to check for counterfeit, and it is buggy.
I've had this issue a few times over the last month or so on multiple pairs of headphones which all worked without issue previously. I've also had some weird issues with getting them to connect/disconnect to/from devices reliably so not sure if there's been a bug introduced with a recent release.
I found switching my phone off & on usually fixes the issue.
I found switching my phone off & on usually fixes the issue.
I wonder if my issue is related. The first APP2 that I bought has worked according to expectations.
However, starting at some point this week my iP14P suddenly cannot recognize the APP2 (5B58).
When I go through the pairing process it eventually discovers the name I use for the device.
At the moment it seems like an endless cycle so not sure when it will be time to go to Apple as I have AC+
However, starting at some point this week my iP14P suddenly cannot recognize the APP2 (5B58).
When I go through the pairing process it eventually discovers the name I use for the device.
At the moment it seems like an endless cycle so not sure when it will be time to go to Apple as I have AC+
I have started to have the same issue. Feels like it’s since the iOS 16.3 update on my AirPods Pro gen 2. Get the notification that somebody might be tracking me. Also AirPods don’t connect to my phone or show battery status in the battery widget. After a phone restart it seems to be ok for a few hours.
same issue here, it is driving me nuts.
h/w: 14 pro, 2x airpods 2. gen, 1x beats fit pro
i already spent some hours trying to figure it out (well, find steps to reproduce), but its hard to describe.
talked to apple support, they want to swap my 14 pro, because it might fix the problem. i am reluctant to do so because of all the work setting up a new phone...
so today i might have come a bit closer to reproducing it:
cheers
m
h/w: 14 pro, 2x airpods 2. gen, 1x beats fit pro
i already spent some hours trying to figure it out (well, find steps to reproduce), but its hard to describe.
talked to apple support, they want to swap my 14 pro, because it might fix the problem. i am reluctant to do so because of all the work setting up a new phone...
so today i might have come a bit closer to reproducing it:
- after a iphone reboot, everything is working just as it should.
- but more than a day after the reboot, the problem starts: "not your airpods / beats", for all three devices.
- in between, i have moved the iphone out of range from the devices, this might also do the trick, will test later.
cheers
m
Following this thread as I'm having the same issue across 2 different pairs of AirPod Pros (one first generation and one latest generation). I'm updating my phone to the latest public beta 🤷♂️
Update: still having the issue pop up across apple devices. AirPods randomly disappear from iPhone bluetooth menu, MacBook Pro bluetooth menu, iPad, etc.
Anyone else have any luck?
Anyone else have any luck?
Update update: I had my buds replaced at the Apple Store this weekend. They were working fine until today when I pulled them out and got the dreaded "Not your AirPods Pro" message...
I'm guessing the only other thing to do is to re-install iOS but I'm dreading that process.
I'm guessing the only other thing to do is to re-install iOS but I'm dreading that process.
My replacement APP2 had the issue once but not since (*knock on wood*).
My older APP still have the issue, but they're out of warranty so I'm just living with it.
My older APP still have the issue, but they're out of warranty so I'm just living with it.
Just had this happen for the first time on my AirPods Pro 1st gen after owning them for over a year.. Hopefully it's a firmware issue that can be addressed when they re-release 5E133