Bug Report - Incorrect trackingAreaIdentifier in visionOS 26 Hover Effect Sample Code

Question

Created 3w

Replies 3

Boosts 0

Participants 4

Description: In the official visionOS 26 Hover Effect sample code project , I encountered an issue where the event.trackingAreaIdentifier returned by onSpatialEvent does not reset as expected.

Steps to Reproduce:

Select an object with trackingAreaID = 6 in the sample app. Look at a blank space (outside any tracking area) and perform a pinch gesture .

Expected Behavior: The event.trackingAreaIdentifier should return 0 when interacting with a non-tracking area.

Actual Behavior: The event.trackingAreaIdentifier still returns 6, even after restarting the app or killing the process. This persists regardless of where the pinch gesture is performed

Answered by DTS Engineer in 847697022

Hello @iricszhou,

As evidenced by these replies we think you've discovered a bug and would appreciate a bug report, and the version of visionOS being used, to continue investigating.

@darkpaw this isn't entirely accurate: "It won't really get progressed if it's only posted in these Developer Forums." as there are issues that can be resolved directly here in the forums without requiring a bug report. It is often preferred to resolve issues here directly for efficiency.

Boost

Answer 1

darkpaw OP

3w

You should probably raise this as a bug in the usual way. It won't really get progressed if it's only posted in these Developer Forums.

You need to raise each issue you find separately at https://feedbackassistant.apple.com/ You can post the FB numbers here if you want, so that others can link to them.

0

Answer 2

Graphics and Games Engineer OP

Apple

2w

Which version of the visionOS beta are you testing with? (You can check the version in the Settings app)

0

Answer 3

DTS Engineer OP

Apple

2w

Recommended

Hello @iricszhou,

As evidenced by these replies we think you've discovered a bug and would appreciate a bug report, and the version of visionOS being used, to continue investigating.

@darkpaw this isn't entirely accurate: "It won't really get progressed if it's only posted in these Developer Forums." as there are issues that can be resolved directly here in the forums without requiring a bug report. It is often preferred to resolve issues here directly for efficiency.

0