As of the latest AirPod Pro firmware (3A283), I'm happy to report this is now working 🙏

No changes on iOS 14 Beta 3 for me. No update on FB7771582 either, it's still marked as Open.

Just as a heads up, it looks like this API is still not providing data on iOS 14 Beta 2 (18A5319i) and I haven't received any word from Apple (on radar FB7771582) as to whether this is just a stubbed-out API for now. I'm starting to think we might not get access to this until we get an AirPods firmware update closer to launch. Not sure if iOS is stubbing out these methods, or the AirPods just haven't been updated to provide the data. I imagine that when (or if) spatial audio arrives in the betas, this API will start working. Super excited to start playing with this when it lands!

It's under CoreMotion, called CMHeadphoneMotionManager (docs here - https://developer.apple.com/documentation/coremotion/cmheadphonemotionmanager). For what it's worth, it doesn't look like it currently works (see https://developer.apple.com/forums/thread/650051 ) and I'm not seeing any noise from the community about getting it returning data. I've filed radar FB7771582 to track, but let me know if you get it working!

Yep, it's under CoreMotion, called CMHeadphoneMotionManager (docs here - https://developer.apple.com/documentation/coremotion/cmheadphonemotionmanager). For what it's worth, it doesn't look like it currently works (https://developer.apple.com/forums/thread/650051) and I'm not seeing any noise from the community about getting it returning data. I've filed radar FB7771582 to track, but let me know if you get it working!

I've updated my Airpod Pros to the latest firmware (released overnight, 2D27), and am still not seeing any motion events fired.

Thanks for the insight Bobjt, much appreciated!Understand that you probably can't say too much more, but is the intention to deprecate this API in the near future (or at least publicly document the lack of support for new devices)? Can we rely on the 2020 iPad Pros to support future ARKit APIs? It's a shame to hear that this is a hardware limitation, as it puts a bit of a dampener on an otherwise perfect AR development device.

Ah, that's a real shame, but thanks for the heads up! The new iPads are very prominently marketed as having a TrueDepth and A12 processor (alongside dedicated AR hardware in the LiDAR sensor) — I kind of assumed the internal capability check hadn't been upadted to include the A12Z, but that's super strange that it was intentionally excluded.I've also filed this as a bug, as it goes against all previously documented API capabilities. I'll let you know if I'm able to get some more clarification 👍

For what it's worth, I'm seeing this too (iPad Pro 2020, 11", iOS 13.4). I believe this is an unfortunate bug in iOS 13.4 as the previous generations of iPad Pro supported this fine, and these new generation devices have the requisite hardware (A12, TrueDepth camera).Currently upadting to iOS 13.4.5 beta to see if it's fixed, but it'd be a shame to have worse ARKit support on this new device than the old one.EDIT — Yeah, still an issue on iOS 13.4.5 😔