Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
hello,Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
hello,Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
Hi, thank you very much for the detailed guidance. Your suggestions helped me isolate a separate blocker before the optical constellation matching stage.
While retesting with Apple’s “Working with generic spatial accessories” sample, I encountered an ASA version-negotiation issue similar to the one reported here:
https://developer.apple.com/forums/thread/838291
Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
hello,Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
hello,Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
Tested the suggested workaround. Our firmware no longer gates on Host Version 0.0. After visionOS writes 00 00 01 79, TimeSync reaches READY, IMU remains stable at ~398.9 Hz with no errors or drops, and mode-2 LED reports continue (count >769, late=0, queue_overflow=0). However, Apple's Generic Spatial Accessories sample still shows authorization=allowed, Provider State unavailable, Is Tracked=false, and no AccessoryAnchor.
Hi, thank you very much for the detailed guidance. Your suggestions helped me isolate a separate blocker before the optical constellation matching stage.
While retesting with Apple’s “Working with generic spatial accessories” sample, I encountered an ASA version-negotiation issue similar to the one reported here:
https://developer.apple.com/forums/thread/838291