Thanks. Our accessory firmware already does not gate operation on the host-selected version. After visionOS writes 00 00 01 89, the accessory continues reporting TimeSync connection anchors, visionOS enables the HID IMU notifications, and the accessory continues sending IMU reports. However, we follow the guidelines for creating the reference object, we never received the AccessoryAnchor. Please let me know if there is an update on the known issue. Thank you very much.

Filed as FB23870886. I tested the suggested ASA 1.0 version (02 01 00 01 01). visionOS reads the it twice but still writes Host Version 00 00 01 89. I attached a visionOS-originated sysdiagnose captured immediately after reproduction, and the complete accessory serial log.

Filed as FB23870886. I tested the suggested ASA 1.0 version (02 01 00 01 01). visionOS reads the it twice but still writes Host Version 00 00 01 89. I attached a visionOS-originated sysdiagnose captured immediately after reproduction, and the complete accessory serial log.

Filed as FB23870886. I tested the suggested ASA 1.0 version (02 01 00 01 01). visionOS reads the it twice but still writes Host Version 00 00 01 89. I attached a visionOS-originated sysdiagnose captured immediately after reproduction, and the complete accessory serial log.

Filed as FB23870886. I tested the suggested ASA 1.0 version (02 01 00 01 01). visionOS reads the it twice but still writes Host Version 00 00 01 89. I attached a visionOS-originated sysdiagnose captured immediately after reproduction, and the complete accessory serial log.

Filed as FB23870886. I tested the suggested ASA 1.0 payload (02 01 00 01 01). visionOS reads the payload twice but still writes Host Version 00 00 01 89. I attached a visionOS-originated sysdiagnose captured immediately after reproduction, and the complete accessory serial log. Thank you.